Privacy
Not as a promise we could quietly change — there is no account, no sign-in and no server of ours for them to be sent to. Everything below describes what the app actually does, and each claim is something you can check.
Last updated 22 August 2026
The short version
| What | Only if | Where it goes |
|---|---|---|
| Crash reports and errors | You turn on Share anonymous diagnostics | Firebase Crashlytics |
| Which screens and buttons were used | You turn on Share anonymous diagnostics | Google Analytics for Firebase |
| A notification address for this install | You allow notifications | Firebase Cloud Messaging |
| Nothing else | — | — |
Refuse all three and the app still works completely: the prompter, recording, saving to your gallery and every setting are unaffected. None of them is a condition of using Orate.
What stays
Everything you write or paste stays in Orate's own storage on the device. It is never uploaded, never included in a crash report, and never attached to an analytics event.
That last one is enforced rather than intended: the internal type an event can carry is a closed set of strings, numbers and true/false flags chosen from a fixed list, so there is no code path by which a script, a filename or anything you typed could become part of one.
Video and audio stay in Orate's own storage until you save or share them yourself. Saving copies a file to your photo library or gallery; sharing hands it to whichever app you pick. Neither passes through us.
Text size, reading window, pace, mirroring, appearance, language and recording quality are stored on the device only. There is nothing to sync because there is no account to sync to.
Writing, prompting, recording, saving and sharing all work in airplane mode. If Orate ever appears to need a connection for one of those, that is a bug.
The two switches
In Settings. It covers two things together, because both are measurement and neither is something you asked for: crash reports, and a record of which screens and controls were used.
The events are things like “a recording started”, “a take was saved”, “the upgrade screen was opened”. They carry the app version, the platform, the interface language, the device model and whether the install has Pro — and nothing else.
Turning it off stops collection at the source, not just in our own code: the underlying analytics and crash libraries are switched off in the app's own configuration files, before any of our code runs, and only this switch turns them on.
Orate asks after your first recording, never at launch. Most of what it sends is local and never leaves the device: a reminder you set yourself, an export finishing, a warning that storage is nearly full.
Allowing notifications also registers this install with Google's notification service, which issues an address for it. That address is what makes an occasional announcement possible. It identifies the installation, not you, and there is nothing on our side to join it to.
Revoke permission and the address is deleted rather than left behind. On Android you can also mute announcements on their own and keep your reminders, because they are separate notification channels.
Two things, both of which your device declares for itself: your app language, and whether this install has Pro. Nothing is uploaded to make that work, and there is no list of devices anywhere — a message is addressed to a group, not to anyone in particular.
Never
There is no sign-up, no login and no profile. We never set a user identifier with any third party. Each service holds its own per-installation id — and because there is no account and no server of ours, there is nowhere those ids could be joined together or to a person.
No advertising identifier is read, no data is shared with advertisers or data brokers, and nothing is used to follow you across other apps or websites. There are no ads in Orate. This is why iOS never shows you an app-tracking prompt for it: there is nothing to ask about.
We do not sell or rent anything about you to anyone. There is no data to sell.
Purchases are handled entirely by the App Store or Google Play. We never see your card, your address or your store account, and there is no receipt server here — Orate asks the store whether this install has Pro and gets back yes or no.
Details
Google, through Firebase, provides crash reporting, analytics and notification delivery. They process that data on our behalf and receive nothing else.
Apple and Google also process purchases as the stores you bought through, under their own privacy policies rather than this one.
Vercel hosts this website and counts its page views, and Google Analytics records where visits to it came from. Both are the site rather than the app, and they are the next answer below.
Everything above describes the app. This site counts page views, through Vercel Web Analytics: the page you opened, the link you arrived from, a rough country and city, and your device type, browser and operating system. It sets no cookies and stores nothing on your device, and it cannot see anything you type.
Visitors are counted by a hash of the request that Vercel discards after 24 hours, so there is no identifier to follow you with and nothing that outlives a day. None of it reaches the app, and none of the app's switches apply to it.
The site also uses Google Analytics, which tells us where visits came from — a search, a link, a post somewhere — and which of the two store buttons gets clicked. It runs without cookies: the consent settings are initialised to refuse every kind of storage and are never granted, so nothing is written to your device and no identifier is kept for you.
That is why you were not asked about cookies on either count — there are none to ask about. It costs us accuracy, because a second visit cannot be recognised as the same person, and that is the trade we would rather make than put a consent dialog in front of a page selling an app with no account.
If your browser sends Do Not Track or Global Privacy Control, the analytics script is not loaded at all. Neither signal is legally binding in most places, which is rather the point of honouring it.
Crash reports and analytics events expire on Firebase's own retention schedule. Turning the diagnostics switch off stops any further collection immediately. The notification address is deleted when you revoke permission, and expires by itself if the app is removed.
Turn off Share anonymous diagnostics in Settings to stop analytics and crash reporting. Revoke notification permission in your phone's settings to delete the notification address. Delete the app to remove everything held on the device, including every script and recording — those are on the device, so uninstalling is what deletes them, and it cannot be undone.
If you want to ask us anything about the above, or make a request about data held about an install, write to contact@planifyapps.com. Please say which platform you are on. Bear in mind that with no account we have no way to identify which records are yours, which is a limit of having collected so little rather than a refusal.
Orate is a general-purpose tool and is not directed at children. It collects nothing that could identify anyone of any age.
If what the app sends ever changes, this page changes in the same release rather than afterwards, and the date at the top moves. The store listings carry their own summaries of the same facts, and all three are kept in step deliberately.