Last updated: July 22, 2026
Big Mouth Marketing Pte Ltd ("we", "our", "us") operates Leadber.com. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our Service.
Lead data (names, phone numbers, emails) scraped through Leadber is sourced from publicly available web pages. You, as the customer, are the data controller of this lead data. We process it on your behalf as a data processor. We do not sell lead data to third parties.
When a customer sends a photo, voice note, video or document to a WhatsApp number connected to Leadber, we record that a message was received, its type (image, audio, video, document), an optional caption or filename, and a reference id supplied by WhatsApp. The file itself is not stored on Leadber's servers — not on disk, not in object storage, not in cache. When you open the conversation, we stream the file from WhatsApp on demand using that reference id.
Because WhatsApp removes stored media after a limited period, older files may no longer be viewable in Leadber. The text record of the message remains. You can turn media display off entirely for your workspace in Settings → Messaging; when it is off, nothing is fetched and the chat shows a placeholder instead. Twilio-hosted media is handled the same way.
When a message contains media, the automatic AI reply is disabled for that conversation and a human is asked to respond — media content is never read by the AI (see section 3b).
Leadber uses third-party AI providers to generate replies, suggest messages and analyse leads. When the AI acts on a conversation, the text of the inbound and outbound messages is sent to one or more of these providers so that a response can be produced. Media (photos, voice notes, videos, documents) is not sent to any AI provider — media messages trigger a hand-off to a human reply instead.
The third parties that receive data on your behalf, and what each receives, are:
| Provider | What it receives | Why |
|---|---|---|
| OpenAI (GPT-4o-mini) | Text of the inbound message, your Knowledge Lab (My Brain) context, and the text of the recent conversation; or, for LeadDive, the business profile and website text already gathered for that lead. No media. | Draft or send automatic replies; generate suggested opening lines; produce a LeadDive fit verdict. |
| Groq (openai/gpt-oss-20b) | Scout search queries and interpreted intent; business data gathered from Google Maps and from the lead's website (text only); LeadBrain signals derived from your pipeline. No customer media. | Interpret search prompts, extract facts about a lead, score and summarise leads, and draft message suggestions. |
| Firecrawl | URLs to scrape (a lead's own website). Returns rendered text. No message content, no media. | Fallback website enrichment when Google Maps alone is insufficient. |
| Google Maps Places API | Search query strings (business name, city, phone number). No customer messages. | Primary lead discovery engine for Scout and LeadDive. |
| Twilio | Recipient phone number and the text of the message you send; and, where used by your workspace, Twilio-hosted media URLs. Status callbacks. | WhatsApp delivery when you use a Twilio-provisioned number. |
| Meta (WhatsApp Cloud API) | Recipient phone number or business identifier and the text of the message you send; Meta also delivers inbound messages (text and media references) to Leadber via webhook. | WhatsApp delivery when you connect your own WhatsApp Business number (Meta Embedded Signup). |
| Resend | Recipient email address, subject, and the body of the email you send (not inbound customer messages). | Outbound email delivery when your workspace has connected a Resend API key, and for Leadber's own transactional email (sign-up, password reset, invoice). |
| Pusher | Lead identifier, phone number, lead name and a short preview of the inbound message (up to 80 characters). No media. | Push a new-message notification to the open chat screen in real time. |
| Stripe | Your billing details (handled by Stripe directly; Leadber does not store card numbers). | Subscription and credit top-up billing. |
No AI provider used by Leadber receives images, audio, video or document bytes. We do not call any vision or multimodal model. If you turn automatic replies off in Settings, no message content is sent to OpenAI or Groq for that workspace.
All data is stored and processed on our cloud infrastructure provider located in Singapore. We do not transfer personal data outside Singapore except where required to provide the Service (e.g., Groq API calls for AI features, Twilio for WhatsApp delivery). Such transfers are governed by appropriate data processing agreements.
Leadber's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Leadber uses Google user data solely to provide and improve core application features, including Google Calendar integration for scheduling meetings. We do not use Google user data for advertising, selling to third parties, AI/ML model training, or any purpose unrelated to the application's core functionality requested by the user.
We retain your account data for as long as your account is active. Lead data is retained for 24 months from the date of collection or until you delete it, whichever is sooner. Outreach logs are retained for 12 months. You may request deletion at any time.
You can request deletion of your account and all associated data at any time.
Depending on your jurisdiction, you may have rights to:
To exercise these rights, contact us in writing at the address below. We will respond within 30 days.
If you are a lead who has received a WhatsApp message through Leadber and wish to opt out, reply STOP to the message. Your number will be immediately added to our suppression list. For further requests, contact us in writing at the address below.
We use essential cookies for authentication and session management. We use analytics cookies (anonymised) to understand how the Service is used. You can disable cookies in your browser settings, though this may affect functionality.
We implement industry-standard security measures including encryption at rest and in transit, access controls, and regular security audits. However, no method of transmission over the internet is 100% secure.
We may update this Privacy Policy from time to time. We will notify you of significant changes by email or in-app notice. Continued use of the Service after changes constitutes acceptance.
For privacy-related enquiries, please contact us in writing:
Big Mouth Marketing Pte Ltd, Singapore