Whisper Magic
Android privacy

Where your words go.

Version 8, last updated 16 November 2026. This policy covers the Whisper Magic app for Android. The Mac app has its own policy. Every sentence here describes what the app's code does, not what we would like it to do.

The short version

Cloud dictation is on by default, and each recording goes to Whisper Magic's cloud to become words. One switch in Settings keeps dictation on the phone instead. Rewrite is off until you turn it on, and then it runs on the phone too. Opening Settings checks the cloud allowance even with cloud dictation off, and that request carries an install id or your account's session. Signing in and downloading a model also use the network. A report you send is the only other thing that leaves the phone, and it leaves when you press Send.

What leaves your phone

Cloud and account requests use fixed HTTPS addresses and do not follow redirects, and neither does a report apart from one retry at the same worker's workers.dev address. The app has no advertising, third-party analytics SDK, automatic crash-report uploader or update-check request; a crash writes its stack into the app's own log, which leaves the phone only inside a report you send. The usage and anti-abuse records below are still collected by our services.

Cloud processing and retention

Our proxy sends audio to Microsoft's transcription service. If that attempt fails and a fallback is configured, it sends the audio to xAI. Rewrite runs on your phone in this version and sends no transcript text. The proxy still has a cloud route for it, pointing at Baseten or Fireworks, and that route is switched off in the app code.

The proxy does not write successful audio or transcript bodies to its database. It keeps usage and provider counters instead. Service logs can contain provider error messages, including up to 200 characters of a failed transcription response. Not having an audio database is not a promise about what an outside provider keeps. The app does not set those providers' retention periods, and this policy does not promise a deletion deadline for their copies.

Cloud dictation is optional: the bundled speech engine works with no network at all. The cloud switches do not send the text already in the destination field as dictation or rewrite input.

Identifiers and server records

Signed out, each cloud request carries an install id: a random UUID made on the phone the first time it is needed. It is not a hardware id and not an advertising id. It lasts until the app's storage is cleared or the app is uninstalled, and clearing storage lets the app make a new one. It is not a permanent reinstall identity. Signed in, cloud requests carry the account's session instead, never both.

The proxy stores seconds billed, request counts and the last update time against an install id for its lifetime allowance, or against an account or linked license for each monthly period. A Rewrite request would also store per-provider request and failure counts, costs and an update time; the cloud route is switched off in this version, so those rows are not written. For signed-out requests it records the network address, day, install id and first-seen time, to limit new installs from one address. A day is the counting window, not a one-day retention limit: the code has no scheduled purge for those rows or the usage rows.

The sign-in service also stores per-email hourly code-request counters and per-address mail and account-creation rate counters. Those windows roll over when another request updates them, and the code has no scheduled deletion of the saved addresses. Signing out or clearing phone storage does not remove any of these server records.

What stays on the phone

What is not collected

Deleting your data

Changes

A change to how the app handles your data is a change to this page in the same commit, and the version above goes up. If this page and the app disagree, the app is right and the page is a bug: write to privacy@inmost.app.

Future Shock LLC · privacy@inmost.app · contact form