Privacy Policy
This Privacy Policy explains how Doppler HQ, Inc. ("Pebble", "we", "us") collects, uses, and shares information when you use Pebble via WhatsApp or our websites at pebble.exchange, including learn.pebble.exchange. If you have questions, email us at hi@pebble.exchange.
1. What we collect
We collect the information described below to operate, secure, and improve Pebble.
- Information you give us in chat. When you talk to Pebble on WhatsApp, we store the messages you send, and things you share in them — your name, city, email address, what you're looking for, what you can help others with, people you invite or recommend, and any links (LinkedIn, personal site) you share.
- Your WhatsApp phone number. We receive it from WhatsApp each time you message Pebble, and we use it as your account identifier.
- Your email address. If you choose to verify an email, we store the address while verification is pending and send a short-lived verification link to it. We mark it verified only after you complete the link. Verifying an email is optional until you want to complete an intro; both people need a verified email before Pebble can send the introduction.
- Your messaging preferences and consent. We record whether you have opted in to receive intro requests, intro updates, and meeting updates on WhatsApp, along with when and how that choice was made. We also record if you pause or resume those updates.
- Calendar availability, only if you grant it. If you grant Pebble access to your Google Calendar to schedule an intro meeting, we read your free/busy times and create the meeting event you approve. We do not read the content of your other events.
- Public profile pages you share. If you paste a LinkedIn URL or personal website, we may fetch the public page to enrich your profile.
- Delivery signals. When we send email intros, we receive delivery, bounce, and complaint signals from our email provider so we can stop sending to bad addresses.
- Website and advertising attribution. On our public marketing pages, we collect page and interaction data, browser and device information, cookies, and campaign, ad, placement, and referral identifiers. If you join a waitlist, we associate that attribution data with the signup so we can measure which campaigns lead to signups.
We do not ask for or handle payment information at this time.
2. How we use it
We use what you share to:
- Understand what you're looking for and match you with someone in the Pebble network who might fit.
- Ask the potential match on your behalf, and — only if they say yes — offer the intro back to you.
- Send the introduction by email to both people's verified email addresses once both sides agree and, if you separately grant calendar access, help compare availability and schedule an intro meeting.
- Reply to your WhatsApp messages and, where you have opted in, send intro requests, intro updates, and meeting updates. You can stop proactive updates at any time by replying PAUSE PEBBLE UPDATES.
- Improve Pebble's replies and matching quality.
- Understand website performance and measure the effectiveness of our advertising campaigns.
- Keep the service safe and running, and comply with law.
We do not sell your personal information. We do not use your messages or profile to train third-party foundation models. If we ever want to train our own model on user content, we will ask for your consent first.
3. Who we share it with
Pebble relies on a small set of service providers to operate. The messages and profile data you share with Pebble may be processed by:
- Meta — to receive your messages and send our replies through the WhatsApp Business Cloud API, and to measure ads through the Meta Pixel and Conversions API. For ad measurement, we may send a one-way-hashed version of a waitlist email address together with campaign, browser, and conversion information.
- Google Cloud (asia-southeast1) — to host our servers and database.
- Google Vertex AI (Gemini) — to run the conversational model that reads your messages and drafts replies. Vertex AI is configured as a data processor; per Google Cloud's terms, your prompts and responses are not used to train Google's foundation models.
- Bird (SparkPost) — to send and receive email on Pebble's behalf.
- Google Calendar API — only if you grant calendar access, and only to read free/busy and create the intro meeting you approve.
- Third-party LinkedIn enrichment providers accessed via the RapidAPI marketplace — used narrowly to enrich profile information you share with us. The specific provider may change; we choose providers that offer commercially reasonable data-handling terms.
We share the minimum information each provider needs to do its job. We do not sell your personal information.
4. How intros work — what we share with other users
Pebble uses staged disclosure so members can consider possible matches without exposing direct contact details.
- When Pebble shows possible matches, before the member is contacted or consents to an intro, a preview may include their name, public profile links, location, background, and why they may be a fit. It does not include phone numbers or email addresses.
- When someone asks Pebble to contact a potential match, Pebble may start with a generic request and then share the requester's name and relevant context while asking whether the potential match is open to the intro.
- When both sides say yes, Pebble sends an email introduction using each person's verified email address. Pebble does not disclose WhatsApp phone numbers as a fallback.
An introduction is never completed unless both people agree. Direct email addresses are shared only through that mutually approved email introduction.
5. How long we keep it
We keep your profile and intro history for as long as your Pebble account is active, so we can stay useful to you and continue to make matches. WhatsApp message contents in our systems are kept while the account is active and, for accounts that have gone inactive without asking us to delete them, for up to 12 months afterwards.
If you ask us to delete your account, we remove your identifying profile information within 30 days. Backups may take up to a further 30 days to fully rotate. We may retain a limited set of records for longer where the law requires it, or where we need them to defend a legal claim.
6. Security
We use technical and organisational measures we consider appropriate to protect your data — encryption in transit (HTTPS), encryption at rest for sensitive fields (calendar tokens are encrypted with keys held separately from our database), logged staff access, and short-lived credentials for our staff.
We do not currently hold SOC 2, ISO 27001, or similar third-party security certifications, and we do not claim any. No online service is perfectly secure. If we ever discover a data breach that affects you, we will notify you without undue delay and as required by law.
7. Your rights
Depending on where you live, you may have rights under laws such as the EU / UK General Data Protection Regulation, the California Consumer Privacy Act, the Hong Kong Personal Data (Privacy) Ordinance, and similar consumer-privacy laws in your jurisdiction. These include the right to:
- Ask what personal data we hold about you and receive a copy.
- Ask us to correct information that is inaccurate.
- Ask us to delete your data.
- Withdraw consent for optional integrations (for example, revoke calendar access) at any time.
- Pause proactive WhatsApp intro requests, intro updates, and meeting updates at any time by replying PAUSE PEBBLE UPDATES. You can resume them by telling Pebble you want updates again.
- Object to or restrict certain processing.
To exercise any of these rights, email us at hi@pebble.exchange. We respond as soon as we can — typically within 30 days where practicable, and in any case no later than the period required by applicable law.
You can also revoke Pebble's access to your Google Calendar at any time from your Google Account settings.
If you live in the EU, UK, or Switzerland you can complain to your local data protection authority. If you live in Hong Kong you can complain to the Office of the Privacy Commissioner for Personal Data (PCPD). If you live in the United States you can raise a complaint with the Federal Trade Commission or your state Attorney General.
8. Age
Pebble is intended for people aged 18 and over. If you are younger than 18, please do not use Pebble. If we learn that we have collected information from someone under 18, we will delete it.
9. International transfers
Pebble is operated by Doppler HQ, Inc., a United States corporation. Our
primary hosting and database sit in Google Cloud's
asia-southeast1 region (Singapore). Some of our service
providers process data in other countries (for example, Meta's WhatsApp
Cloud API and Bird operate globally). Where required, we rely on standard
contractual clauses and other lawful transfer mechanisms provided by our
processors.
10. Google API Services Limited Use
Pebble's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In practice: we use Google Calendar access only to check your free/busy times and create the intro meeting you approve. We do not use calendar data for advertising, we do not sell it, we do not let humans read it except when you ask for support or where required by law, and we do not use it to train AI models.
11. Automated processing
Pebble uses automated processing to rank and suggest possible matches from the network. A suggested match may be shown before that person is contacted, but being shown does not create an introduction. Pebble contacts a selected potential match, and an email introduction is completed only after both people agree. No automated decision by Pebble has a legal or similarly significant effect on you.
12. Cookies and analytics
On public website pages, pebble.exchange uses Amplitude Analytics and Session Replay to understand visits and interactions and improve the site. This may collect page views, clicks, browser and device information, and a replay of how a visitor interacts with those public pages. We do not load Amplitude on token-bearing email verification or calendar connection pages. Amplitude processes this information on our behalf.
On advertising landing pages, including learn.pebble.exchange, we also use the Meta Pixel and Meta Conversions API to attribute waitlist signups and beta opt-ins to campaigns and ads. Meta may set or read advertising cookies. We retain first-touch and most-recent campaign attribution in browser local storage for up to 90 days. You can limit cookies through your browser and Meta account settings, although doing so may reduce attribution accuracy.
13. Changes to this policy
If we make material changes to this policy, we will update the "Last updated" date and, where appropriate, notify you via WhatsApp or email. Continued use of Pebble after a change means you accept the updated policy.
14. Contact
For privacy questions or to exercise your rights, email hi@pebble.exchange. We have not appointed a formal Data Protection Officer; privacy queries are handled by the small team behind Pebble at the same address.
Data controller: Doppler HQ, Inc., 3830 94th Ave NE, Yarrow Point, WA 98004, United States.