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 dictation. When it is on, each recording goes to
cloud.inmost.appover HTTPS and the transcript comes back. The request carries the audio, transcription settings, your saved spellings and fixes, and a credential, not the destination app's name or the text already in its field. The app refuses a recording over 300 seconds or 20 MB before uploading anything. - Rewrite. Rewrite runs on your phone: when you turn it on and its model is downloaded, each finished transcript is tidied locally and nothing is sent for it. The cloud route for Rewrite is switched off in this version.
- A report. Settings → Send feedback posts to
feedback.inmost.apponly when you press Send. The request carries your message, the kind of report, a random install id, and your email address if you type one. Two switches are on by default and add the app's own log, up to its last 64 KB, and the app version, Android version and phone model; a third switch is off by default and adds the text of your most recent dictation. The attached log holds no word you said or typed. The screen renders the exact request body from the same value that is posted. A send that fails is kept on the phone and retried on the next launch and after the next successful send. The app keeps at most 20 saved reports. A saved copy is deleted when its send works, when the service refuses the report, after five tries, or when the app's storage is cleared. The oldest is deleted when a full queue takes a new one. - The allowance check. Opening Settings asks
cloud.inmost.appfor the cloud meter, whether or not cloud dictation is on. Signed out, the request carries this phone's install id. Signed in, it carries the account's session. It carries no recording and no transcript. - Signing in. The app sends an email address, then the six-digit code you enter, to
license.inmost.app. Our service passes the address and the code to Cloudflare Email Sending to deliver the message. The code is valid for ten minutes. Our database keeps a hash of the code with its address, expiry, attempt count and send time. A successful use deletes that row, and an expired or exhausted row is deleted the next time a sign-in attempt checks it. Expiry alone does not run a timed deletion, and asking for another code replaces the previous row. - The account. The account keeps its id, email identities, creation and last-seen times, any linked license, and hashed session tokens with issue and expiry times. The app uses the session to load the account, add or remove an email identity and sign out. Signing out clears the session and the loaded account on this phone. It does not delete the account or its server records. A sign-out request deletes that server session only if it reaches the service.
- Model downloads. If you tap Download, the app fetches model files from HTTPS URLs at
huggingface.co, which can redirect the download. Each file is checked against its listed size and SHA-256 hash. No audio, transcript, account session or install id is attached. Like any download, it shows your network address to the server that serves it.
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
- Recordings. Dictation writes audio to the app's own recordings directory. Canceling deletes that dictation. A recording that was transcribed is not deleted by the app, so it stays until Android's Clear storage or an uninstall removes it.
- Kept dictations. When a cloud dictation fails, the app can keep a second copy in
files/kept-takes. Keeping dictations is on by default and holds the ten most recent copies. Settings can stop future copies, and turning it off does not delete copies already kept. A kept dictation is not an automatic retry. - App log and unsent reports. The app writes its own log to
files/inmost.log, one file capped at 256,000 bytes (Diagnostics.MAX_BYTES), and writes the type and frames of a crash into it, never the exception's message. Settings → Send feedback attaches the last 64 KB unless you turn that off, and shows it to you first. A report that fails to send waits infiles/feedback-outboxand is retried on the next launch and after the next successful send. The app keeps at most 20 saved reports. A saved copy is deleted when its send works, when the service refuses the report, after five tries, or when the app's storage is cleared. The oldest is deleted when a full queue takes a new one. - Recent dictations. The home screen keeps up to 20 inserted dictations, cut to 280 characters each, in private preferences. You can copy an entry, delete it or clear the list there. These entries are not uploaded by a history feature; cloud processing is described above.
- Your words and fixes. The keyboard learns an unfamiliar word after two uses, keeping up to 500 learned words. It also keeps correction pairs and rules used to repair later transcripts before insertion. Settings lets you inspect and remove learned words and active fixes, or clear the personal dictionary. These stores are not uploaded as a word list. Their words can still appear in text you choose to dictate or rewrite.
- Practice. Practice writes prompted words, decoded words, stroke points and the key positions they were made on to
files/warmup-capture.jsonl. Capture is on by default, stops at its 256 KB budget, and has a switch and a separate delete button in Settings. Passage progress is saved separately. - Swipe log. Outside practice or the bench recorder, each completed swipe is written to
files/swipe-log.jsonl. It includes the stroke, key positions, candidates, the committed word and the last 32 characters before the cursor. That context can include text you typed or dictated. Rotation targets two files of 10 MiB each, and a failed rotation can take the files past that target. There is no off switch or in-app exporter for this log. The app does not upload it. - Swipe learning.
files/swipe-store.binholds corrected key positions, up to 400 word templates and up to 512 labeled gestures, trimmed to a 256 KB budget. It is on by default and not uploaded. Settings → Swipe correction → Forget deletes this learning and any debug export, not the swipe log or diary. - Swipe diary. The diary is off by default. Turning it on keeps strokes, ranked and committed words, surrounding text and the keep, change or delete outcome in
files/swipe-diary.jsonl. It rotates at 20,000 lines into one older file. Turning it off stops new entries but does not delete old ones. The app does not upload it. Clear storage or an uninstall removes it. - Password fields. The keyboard hides its microphone in a field Android marks as a password, and the bubble copies dictated text instead of inserting it there. The accessibility service still reads the focused node's attributes and text before deciding how to insert. A password swipe record blanks the committed text, candidates, crossed-letter path and preceding context, but keeps stroke coordinates and key geometry. This is not a promise that the stroke cannot reveal letters.
- Local logs and clipboard. The keyboard and bubble write inserted transcript text to Android's logcat, and the accessibility service logs insertion plans that can contain field text. Logcat is not the app's log: nothing copies it into
files/inmost.log, so a report never carries those lines. A copy you ask for, or a copy fallback when insertion fails, puts the transcript on Android's clipboard, where Android and the app you paste into handle it. - Local measurements. The keyboard keeps counts of characters typed and keyboard switches in the minute after dictation, in preferences and
post-insertion.txt. These counters contain no text and have no uploader. - Your session. The session token is encrypted with a key in Android Keystore. Cloud client diagnostics redact the credential. Local encryption does not remove the server session records.
What is not collected
- No name and no phone number. Signing in puts an email address on our side, and so does a report you send with your email address typed in.
- No contacts, no calendar, no photos, no files, no location and no camera. The app does not separately read a mailbox, text messages or browser history.
- No advertising id, no analytics SDK, no automatic crash reporting and no update check.
- No swipe or typing record is uploaded. The only requests the app makes are the ones named above.
Deleting your data
- On this phone. Clear recent dictations on the home screen. Remove learned words and fixes in Settings → Your words. Delete the practice capture with Forget what practice kept. Settings → Swipe correction → Forget deletes the learned swipe store and any debug export, and leaves the swipe log and diary. To remove all app-managed files and preferences, including recordings, the diary and the saved session, use Android's Settings → Apps → Whisper Magic → Storage → Clear storage, or uninstall the app. Copies you exported or pasted into another app are not removed by clearing Whisper Magic.
- Your account. Settings → Account → Delete account, then confirm. The app and our account service delete your sign-in: every way you signed in, an Apple ID, a Google account or an email address, the address the account was made with, every session it holds, and any sign-in code still pending for it, through
POST /v1/accounts/delete. It allows five deletes an hour from one address. If you cannot sign in, write to [email protected] from the address on the account and a person deletes it for you. Neither path deletes the license you bought: it is the person's and not the account's, and the Macs it is set up on keep working. A cloud plan billed against that license is canceled by the delete; a plan on a license the account never attached is not found by it, so end that one in the Mac app. - What no control here deletes. Clearing phone storage or signing out deletes no server record. Deleting the account leaves the usage and provider counters its requests wrote (not the audio or the text), the copies a provider holds, and the anti-abuse counters this service keeps per calling address. The code does not define a timed retention or an automatic account-deletion schedule.
- Outside providers and logs. The app has no control that deletes a provider's copies or Android's logcat. This policy promises no immediate deletion from those systems.
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 [email protected].
Future Shock LLC · [email protected] · contact form