/call-me — Privacy Policy
Effective: November 18, 2026
/call-me lets your own AI agents call and text your phone (iOS and
Android). This policy
describes what the service stores and why. Short version: there are no user
accounts, no ads, no tracking, no sale of data, and nothing is shared except
with the services below.
What we collect
- Your /call-me number — a random number the app assigns on first
launch. It is the only identifier for you; we never ask for your name, email,
or real phone number.
- Push tokens and device name — the push token for your platform
(Apple APNs on iOS, Firebase Cloud Messaging on Android) so calls and texts can
reach your device. On Android, if push is unavailable the app instead keeps a
connection open to our own server and no third party is involved.
- Messages and call transcripts — texts between you and your AI
agents, the question an agent asked, and the transcript of what was said on a
call. These exist so your history tab works and so your agent receives your
answer.
- Voice audio — processed in real time during a call to synthesize
speech and transcribe your reply. Our servers do not record or store the
audio of a call; only the text transcript is kept. The voice provider,
Fish Audio, keeps what it processes under its own terms (see below).
- Recordings your agents send you — an agent can send a recording to be
played on a call: a file it uploads, or a link (for example a YouTube video or a
podcast episode) that our server downloads. It is kept on our server only to play
it to you and is deleted within a day. It plays as plain audio, so no voice
provider or AI model receives it. The site a link points to sees a request from
our server, not from you.
- Your App Store subscription identifiers — access to /call-me is an
auto-renewable subscription bought in the app. Apple sends us a signed receipt,
and we keep the parts that say whether it is still active: the transaction
identifier Apple assigns to the subscription, the product identifier, the
renewal date, and whether it is a trial. We never see your name, your Apple
ID, or your payment details — Apple handles the payment and tells us
nothing about it. The transaction identifier is what lets a reinstall get the
same /call-me number back.
- Your Google Play subscription identifiers (Android) — when you
subscribe on Android, the app sends us the purchase token Google Play issued,
and we ask Google whether it is a live /call-me subscription. We keep the token,
the order identifier, the plan, the renewal date and whether it is a trial.
We never see your name, your Google account or your payment details.
- Feedback you send — if you write to us from the Feedback tab, the
text and your /call-me number are delivered to the developer's own phone so he
can read and answer it. Nothing else about you is attached, and it is used only
to answer you and improve the app. Deleting your number deletes the
conversation.
- Usage analytics — only after you accept the data-sharing
disclosure, the app sends first-party usage events so the developer can see
which parts of the app work and which confuse people: which screens and steps
you open and for how long, which buttons you tap, the answers to the
microphone and notification prompts, errors the app showed you, the steps of
the subscription screen (viewed, plan chosen, purchase tapped, completed,
cancelled or failed, restore), and call events (rang, answered, declined,
connected, how long it lasted, how it ended). Events never contain what you
or your agents say or write: no messages, no transcripts, no prompts, no
contacts. Each event carries the app version, the platform, the build type
(store, beta or development), a random session identifier for that launch and
a random install identifier kept on your device until you delete the app.
Once your phone has a /call-me number, events carry that number too, so the
developer can follow one setup from start to finish and match it with your
calls. They are therefore linked to your /call-me number. They contain
no advertising identifier, are not used for tracking or advertising and
are not shared with anyone; they go only to the developer's own server.
The server keeps the country the request came from, as reported by our
network provider; the IP address itself is used only to tell the developer's
own and Apple review traffic apart from real use and is never stored. Events
are deleted after 45 days. After you delete your number in the app, new
events no longer carry it.
- Apple Ads attribution (iOS, from version 1.6.4) — after you agree on
the first-launch screen, the app asks Apple's AdServices framework once for an
attribution token and sends it, with a random ID created for this install, to
the developer's own server and to RevenueCat (below). Each asks Apple's AdServices
service which Apple Ads campaign, ad group and keyword, if any, led to the
install; the developer's server then deletes the token and keeps that answer
with the random ID. Purchases you make in the app carry the same random ID, so
the developer can see how many subscriptions came from each Apple Ads campaign
and keyword. The token contains no name, Apple ID, device identifier or
advertising identifier, the random ID is not your /call-me number, and none of it
is used for tracking you across other companies' apps or websites.
How it is used
Solely to operate the service: ringing your phone, delivering texts, and
returning your spoken answers to your own AI agents, plus counting which of our
own ad campaigns led to subscriptions (see Apple Ads attribution above). We do not
use your data to target ads, for profiling, or for training AI models, and we
never sell it.
AI services & third parties
The app asks for your explicit consent on first launch, before any data
leaves your device. When you use /call-me, the following processors are
involved:
- Fish Audio — turns the agent's text into speech and transcribes
your voice in real time during a call and during the short voice setup when you
first open the app, so it receives the text read to you and the audio of your
reply. On a conversation call in English, Fish Audio also runs the language
model that notices when you have finished speaking and passes your words on to
your agent, and it keeps the text of that call (not its audio: recording is
switched off) in our account with it. Fish Audio keeps what it processes for a
period set by its own privacy
policy.
- ElevenLabs — our voice provider until November 14, 2026, and the one
we would switch back to if Fish Audio cannot be used. It then does the same job:
it receives the text read to you and the audio of your reply, and keeps them for
a period set by its own privacy
policy; our plan does not offer zero retention.
- Anthropic Claude Haiku, via Amazon Bedrock — if you speak while your
agent is still working on its next line, the transcript of what you said and of
the call so far goes to Claude Haiku, which writes a one-sentence reply (for
example, that your agent is still working on it). It only relays and never
answers for your agent; what you said also reaches your agent with your next
answer. In the voice setup when you first open the app (and when you run it
again from Settings), the transcript of what you say goes to Claude Haiku, which
picks your language, voice, voice style and AI app from it and saves them as your
settings. Amazon Bedrock does not store these prompts or use them to train
models.
- Cloudflare Web Analytics — counts visits to the callmemcp.com
website: the page viewed, the site that linked to it, country, browser and how
fast the page loaded. It sets no cookies, stores nothing on your device, does
not identify you or follow you across sites, and is not used for advertising.
The app does not use it.
- Google Tag Manager and Google Ads, TikTok Pixel — the callmemcp.com
website loads Google's and TikTok's advertising tags so we can tell whether our
ads bring visitors: they see that a page was viewed and when an App Store or
Google Play button is clicked, along with your browser's usual technical details
and their own cookies. They do not receive anything you say or type in the app,
and the app does not use them.
- Amazon Web Services — hosts our servers. Its Polly and Transcribe
services are our backup voice provider; they process audio transiently and do
not store it.
- The built-in demo agent — the demo call on our website simply reads
your words back to you. It does not send what you say to any language model.
- The AI agents you connect — your transcribed replies and the
messages you send are delivered to the agents you personally gave your /call-me
number to (for example a coding assistant running on your own computer). They
are under your control, not ours.
- Apple Push Notification service (iOS) — delivers call and message
pushes to your device.
- Firebase Cloud Messaging, Google (Android) — delivers call and
message pushes to your device. The push carries the caller's label and the
first line of the question so your phone can show who is calling.
- Apple (App Store) — sells and renews the subscription, takes the
payment, and notifies us when it renews, lapses or is refunded. Apple is the
merchant here, not a processor acting for us, and its own privacy policy covers
what it collects.
- RevenueCat — a subscription analytics service. It receives the
attribution token and random install ID described above, asks Apple whether an
Apple Ads ad led to the install and which campaign, and receives copies of Apple's
subscription notifications from our server (product, trial, renewal, cancellation
and refund events, with Apple's transaction identifier and that random ID). It
never receives your /call-me number, messages, transcripts or voice. We use it
only to count subscriptions and revenue per ad campaign.
- Google (Google Play) (Android) — sells and renews the subscription
and takes the payment. We send Google the purchase token to check that it is
valid and to acknowledge it. Google is the merchant here, and its own privacy
policy covers what it collects.
- Apple, for refund requests — only if you opt in — if you turn on
Help with refund requests in the app and later ask Apple for a refund,
we tell Apple that your subscription was delivered and working, and that we
would prefer the refund be declined. Apple uses this to review the request and
still makes the decision. We send nothing else: no messages, transcripts or
your /call-me number. It is off unless you turn it on, and you can turn it off
at any time on the My Number tab; after that we send nothing. Apple handles
this data under its privacy
policy, and you can ask Apple for access to it or deletion of it at
privacy.apple.com.
These providers act as data processors bound by their service terms and
data-processing agreements, providing protection of your data equal to this
policy. They do not use your data for advertising or to train AI models. We
never sell your data, and never share it with anyone else.
Retention & deletion
Data is kept only while your number exists. In the app, My Number →
Delete my number & all data permanently deletes your number, device
tokens, messages, transcripts, call history, and the stored subscription
identifiers from our servers, immediately. That does not cancel the
subscription itself — cancel it in iOS Settings or in Google Play, or the store
keeps billing you. RevenueCat's subscription records are filed under the random
install ID, not your number; email us to have them deleted.
Security
All traffic uses TLS (HTTPS/WSS). Your /call-me number works like a phone
number: anyone who has it can send you messages and ring your phone, so share it
as you would a phone number. It cannot act for you: reading your history,
deleting your data or moving the number needs the device credential held by the
app on your phone. If someone you don't want keeps reaching you, block that
sender or regenerate the number in the app.
Children
The service is not directed at children under 13 (or the equivalent minimum
age in your jurisdiction).
Contact
Questions or requests: info@callmemcp.com.
Changes
Material changes to this policy will be posted at this URL with an updated
effective date.