Privacy Policy
Last updated 25 August 2026
Saymory holds the things you say when you are thinking out loud, which is about as personal as app data gets. This policy says what stays on your phone, what leaves it, who else touches it, and how to get rid of it. Where the iPhone and Android apps differ, it says so. They do not work the same way, and a policy that described only one of them would be wrong for whoever read it on the other.
Saymory is published by the developer of Saymory ("we", "us"). It is available worldwide as an iPhone app on the Apple App Store and as an Android app on Google Play.
The short version
- On iPhone, speech is turned into text on the device the moment you stop, by Apple's on-device recognition. If you have welcome credits left or a Pro subscription, the recording is then also sent to our transcription provider for a more accurate transcript, and for speaker labels in Conversation mode. It is deleted there as soon as the text comes back. Without credits or Pro, the on-device transcript is all there is and the audio never leaves the phone.
- On Android, every recording is transcribed in the cloud, so the audio is uploaded. Android has no on-device recogniser we can rely on, and rather than ship a worse transcript we send the audio to our transcription provider and delete it there as soon as the text comes back. The recorder screen says "Transcribed after you stop, in the cloud" before you record anything.
- Note text is sent to AI providers to write your summaries, extract your action items, and answer your questions. Nothing else.
- Nothing you write is used to train AI models, and nothing is ever sold or shared with advertisers.
- You can keep your notes off our servers. Cloud backup is off by default; with it off, your notes and audio live only on your phone. Transcription and AI features do send a recording or note text to our providers while they work, and nothing is kept there afterwards.
- You can delete everything, including your whole account, from inside the app.
What Saymory stores on your device
Whether or not you have an account, the following live in the app's private storage on your phone:
- Audio recordings you make, until you delete them or your audio-retention setting removes them.
- Transcripts, note text, photos you add to notes, and the text read out of those photos.
- Your settings, and a local index that lets the app search your notes on-device.
This data is protected by the operating system's app sandboxing, on iOS or Android, and your device passcode or biometric lock. If you never sign in and never turn on cloud features, this is the only place your notes exist. We cannot see them, and we could not hand them over if asked.
What we collect when you have an account
| Data | Why |
|---|---|
| Email address | To create and sign you into your account. If you use Sign in with Apple and choose to hide your address, we only ever see Apple's relay address. |
| Note text and transcripts | Sent to produce summaries, action items, and answers. Stored in your account only when cloud backup is on. |
| Audio | To produce the transcript and, in Conversation mode, the speaker labels. On iPhone while you have welcome credits or Pro, on Android for every recording. Audio is not stored on our servers. |
| Usage counters | Counts of questions asked, summaries generated, and minutes of conversation processed. used to apply plan limits and to keep track of costs. These are numbers, not content. |
| Subscription status | Whether you are on the free or Pro plan, so the app knows what to unlock. Handled through Apple and RevenueCat; we never see your payment details. |
| Crash reports (optional) | Only if you leave "Share crash reports" on. These contain call stacks and device model, never your notes, transcripts, or audio. |
We do not use advertising identifiers, we do not track you across other apps or websites, and we do not build advertising profiles.
Who processes your data
To provide the features described above, Saymory shares the minimum necessary with these processors. They act on our instructions and may not use your content for their own purposes.
| Processor | What it receives | What for |
|---|---|---|
| OpenAI | Note text and transcript text; your question when you ask one | Writing summaries and action items, creating the search index, answering questions |
| AssemblyAI | Audio. On iPhone while you have welcome credits or a Pro subscription; on Android for every recording. | Turning speech into text, and separating and labelling speakers. On iPhone this covers conversations and languages the device cannot handle on its own; on Android it covers everything, because there is no on-device recogniser. The audio and its transcript are deleted from AssemblyAI as soon as we receive the result. |
| Supabase | Account record, and your notes when cloud backup is on | Database and authentication |
| Apple | Purchase and subscription events | Processing payments and managing subscriptions |
| RevenueCat | An anonymous user identifier and your subscription status | Telling the app which plan you are on |
These providers process data in the United States and other countries. Where required, transfers rely on the providers' standard contractual clauses and equivalent safeguards.
On-device processing is not sharing. On iPhone, speech recognition and reading text out of your photos are performed by Apple frameworks running on the device, and that content is not sent to us or to anyone else. On Android, photos you add to a note stay on the device and are never uploaded; speech, as above, is transcribed in the cloud.
Optional connections you control
- Calendar (iPhone only). If you turn on Calendar context, Saymory reads the events around a recording so it can name a meeting note and suggest who was in the room. It is read-only, it stays on the device except for attendee names passed to speaker detection, and it never writes to your calendar. The Android app does not read your calendar at all.
- Reminders and notifications. Task reminders and the daily recap are scheduled locally on your phone, on both platforms. Nothing is sent to a server to deliver them, and there is no push service involved.
How your data is protected
- Everything travels over encrypted connections (TLS).
- Note content, transcripts, titles, and task text stored in your account are additionally encrypted by the app before they reach the database, using AES-256-GCM. The key is held in a separate secrets vault, so anyone reading the database directly sees ciphertext.
- Every row is scoped to your account with database-level access rules. Audio is never stored on our servers. When Conversation mode sends it, it is processed to produce your transcript and discarded.
No system is perfectly secure. What the design does is keep the most sensitive material, the audio itself, off our own servers: it reaches the transcription provider only for as long as it takes to produce the text, and is stored in your account only if you turn cloud backup on.
How long it is kept
Your notes are yours for as long as you want them: nothing you wrote or recorded is deleted on a timer you did not set. Everything else, the operational records our servers produce while serving you, expires on the schedule below. A job runs every day and enforces it.
| Data | Kept for |
|---|---|
| Notes, transcripts and search index in your account | Until you delete the note, turn cloud backup off, or delete your account. Deleting a note removes its transcript, its search index entries and its audio. |
| Recordings on your device | Until you delete the note, or the audio-retention window you chose in Settings, from one day up to forever. Transcripts stay when the recording is reclaimed. |
| Audio uploaded for transcription | Deleted from our storage as soon as the transcript comes back, and deleted from the transcription provider in the same step. It is never kept as a file on our servers. |
| The transcript on a finished transcription job | Cleared once your device collects it, and within 24 hours in every case, even if your device never comes back. |
| Transcription job records (status and timings, no content) | 30 days after the job finishes or fails. |
| AI processing log (which model ran, how long, success or failure, not your text) | 90 days. |
| Error logs, crash reports and product milestones | 180 days. |
| Usage counters and subscription records | For the life of the account, and after deletion where tax and accounting law requires us to keep a record of a payment. These are numbers, not content. |
| Data sent to AI providers | Kept by them only as long as their own operational policies require, and not used to train their models. |
Two things we want to be explicit about, because plenty of apps do the opposite. Ending a subscription does not delete anything. If your Pro plan lapses or moves to another account, you keep every note; only the paid features stop. Nothing of yours is held hostage to a payment. Deleting your account is immediate and real. Your notes, transcripts, audio and search index are erased at once, not queued for a grace period. Your crash reports go with them. The error and AI processing logs are unlinked from you: the user id is stripped out, so what remains cannot be traced back. They then expire on their own schedule. Residual copies can survive in encrypted database backups for up to 30 days before those backups roll off.
If an account goes unused for 24 months we may close it and delete its data, after emailing the address on the account first and giving you a chance to keep it.
Your choices and rights
- Choose what a recording becomes. The sheet shown before each recording lets you turn off the automatic summary and tasks for that note.
- Keep notes off our servers. Leave cloud backup off and your notes stay on the device.
- Export everything. Settings → Export all my data gives you your notes as Markdown; any note can be exported as PDF.
- Delete an individual note, with its audio, transcript and index entries.
- Delete your account from Settings. This erases your account record, notes, transcripts, audio, and search index. It cannot be undone.
- Opt out of crash reports with the toggle in Settings → Privacy.
Depending on where you live, you may also have the right to access, correct, port, or object to our processing of your data, and to complain to your local data protection authority. The controls above cover most of this directly; for anything else, email us and we will action it.
Children
Saymory is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has provided us with personal data, contact us and we will delete it.
Changes to this policy
If this policy changes in a way that materially affects you, we will update the date at the top and, for significant changes, tell you in the app before the change takes effect.
Contact
Questions, requests, or complaints: droidappbdinfo@gmail.com. We aim to reply within a few business days.