Privacy Policy — Wavekeeper

Operated by: Shamir Shakir, an individual developer, operating as Wavekeeper (no separate registered legal entity as of this date).
Contact: privacy@wavekeeper.app

1. What Wavekeeper is

Wavekeeper is an AI phone-call assistant. You give it a plain-language instruction (for example, “Call Nisa and ask if she’s free for dinner tonight”), and it places a real phone call on your behalf using an AI voice. Every call is initiated by you, for a specific task you described, at the moment you asked for it. Wavekeeper does not run mass or automated cold-calling campaigns, does not call numbers you did not name, and does not call on any schedule you did not set.

2. Data we collect, and where it comes from

Data	Source	Why
Account information — email address, and a securely hashed password (if you register with email/password), or your name/email from Google or Apple if you sign in that way	Provided by you at sign-up, or by Google/Apple’s sign-in flow	Identifies your account, lets you sign in on multiple devices, and lets us recover your account (password reset)
Phone numbers you call	Typed by you, or selected from your device’s Contacts	Required to place the call
Your device Contacts (names and numbers)	Read directly from your phone’s Contacts app, on-device only	Used only to match a name you typed against your own address book — your contact list is never uploaded to or stored on our servers, only the one number you choose to call ever leaves the device
Call transcripts — the full text of what was said by both the AI and the person who answered	Generated server-side while the call is in progress	Lets you review what was discussed, and lets the AI summarize the call
Call metadata — who you were calling, the stated purpose, duration, status, language, estimated cost	Generated when you request the call and when it ends	Powers your call history and push notification summary
Your own name (“calling on behalf of ___”)	Typed by you during onboarding	Spoken by the AI so the person you’re calling knows who it’s calling for
Push-notification token	Issued by Google Firebase Cloud Messaging on your device	Lets us deliver a “your call ended” notification
Telemetry / diagnostic events	Generated by the app and server as you use them	Debugging, reliability, and product usage — never your contact names, phone numbers, transcripts, or instructions, only counts and outcome codes

We do not collect: your device’s microphone or camera (call audio is carried between the telephony network and the person you called, not recorded from your phone), your location, or any payment/financial information (no billing system exists yet — see §7).

3. The AI voice, and how it identifies itself

Every call Wavekeeper places uses a synthesized, non-human voice. On every call, in the opening line, before asking anything of the person who answered, the assistant:

States its own name and that it is an AI assistant.
States that the call may be recorded and transcribed.
States who it is calling on behalf of.

If the person who answered asks whether they’re talking to a human, a bot, a recording, or an AI, the assistant is instructed to say plainly that it is an AI and never claim or imply otherwise. The assistant is also instructed never to agree to payments, contracts, or commitments, and to end the call politely if asked to stop calling or if the person sounds distressed.

This reflects the FCC’s ruling that AI-generated voices are “artificial voices” under the Telephone Consumer Protection Act, and state-level automated-caller/bot-disclosure laws in jurisdictions such as California, Utah, and Colorado. This section describes our product’s actual behavior; it is not a certification of compliance in every jurisdiction Wavekeeper may be used in.

4. How the call itself works (and what that means for recording)

Wavekeeper does not use your phone’s own microphone or dialer. When you request a call, our backend places the call through a telephony carrier (see §5), which connects to the phone number you specified. What gets transcribed and stored is the conversation between our AI and the person who answered, not anything captured from your device.

Call-recording consent laws vary by state and country (some require only one party’s consent, others require every party’s consent). To address this consistently everywhere, every call opens by stating plainly that it may be recorded and transcribed, before any other exchange happens.

5. Third parties we share data with, and why

Vendor	What they receive	Why
Infobip	The phone number being called, the text to be spoken	Places outbound calls (default one-way “scripted” path)
Twilio	The phone number being called, the AI’s spoken/heard turns	Places outbound calls for two-way “conversation” mode
ElevenLabs	Text to speak, and on one calling path the raw call audio (processed on their platform, never stored by us)	Text-to-speech, and speech-to-text on that path
Groq	The parsed call instruction, the live conversation transcript	Runs the AI model that decides what the assistant says next
Google Firebase Cloud Messaging	Your device’s push token and a short notification title/body	Delivers the “call ended” notification
Google Sign-In / Sign in with Apple	Your name and email, as shared by the provider	Lets you create/access your account without a separate password
Resend	Your email address	Sends account-related email (e.g. password reset)

We also run our own servers and our own database, where account records, call records, transcripts, and telemetry are actually stored (see §6) — this is our own infrastructure, not a third party. We do not sell your data, and we do not share it with data brokers or advertisers. No advertising or analytics SDK is integrated into the app.

6. How long we keep data, and how

Call transcripts and the phone numbers you called are stored indefinitely, in plain text (not encrypted at rest) — a deliberate product decision as of this update.
Your device Contacts are never sent to or stored on our servers.
Passwords are never stored in plain text — only a securely hashed form.
Push tokens are stored server-side; a token is replaced whenever your device issues a new one.
Telemetry events are retained separately for diagnostics and product improvement — never message content, transcripts, or phone numbers.
You can request deletion of your account and associated data at any time by emailing privacy@wavekeeper.app.

7. Payments / subscriptions

Wavekeeper does not currently collect any payment or billing information. No in-app-purchase, subscription, or payment SDK is integrated as of this update.

8. Your choices and rights

You can deny the Contacts permission at any time; Wavekeeper falls back to letting you type a phone number manually.
You can deny the notifications permission and still see call results in your in-app history.
You can reset your password, sign out of all sessions, or delete your account by contacting us.
Contact privacy@wavekeeper.app for any privacy question, data-access request, or deletion request.

9. Children’s privacy

Wavekeeper is not directed at, and is not knowingly used by, children under 13 (or the minimum age of digital consent in your region, if higher). If you believe a child has used Wavekeeper and provided data to us, contact us and we will delete it.

10. Changes to this policy

We may update this policy as Wavekeeper changes. If we make a material change to what we collect, how we use it, or who we share it with, we will update the date above and, where required by law, provide additional notice.