Sayved privacy policy
Your log lives on your phone. This page explains, in plain English and in full detail, the few things that leave it, who receives them and how long anything is kept.
Last updated 8 October 2026
Summary in six lines
- Everything you log is stored in a database on your phone. We do not hold a copy.
- There is no account. We never ask for your name, email or phone number.
- Speech is turned into text on your phone. Audio is never uploaded.
- To structure an entry, the text or a reduced-size photo is sent through our server to an AI provider (OpenAI), which returns the result. We do not save the content on our server.
- Our server does keep a random device code with usage counters, and, for subscribers, a Google Play purchase token. Neither contains your name.
- No ads, no analytics, no selling of data, no training AI models on your entries.
The privacy policy linked from Google Play lives at kamildzikowski.com/sayved-privacy. This page and that one describe the same practices.
Who we are
Sayved is published by Kamil Dzikowski, who is the controller of any personal data described here. For anything about privacy, write to [email protected].
The short version, in a table
| Information | Where it is | Does it leave your phone? |
|---|---|---|
| Your entries, corrections, charts, conditions, routines, reminders | Database on your phone | No, unless you export or share them yourself |
| Original photos | Your phone | No |
| Voice audio | Never stored by Sayved | No |
| Text of an entry | Your phone | A copy is sent for AI processing when you capture it |
| Reduced-size copy of a photo or document | Created on your phone | Sent for AI processing, not kept by us |
| Entries picked for an Ask question, plus the question | Your phone | Sent for AI processing, not kept by us |
| Device code (random) | Your phone and our server | Yes, with each AI request |
| Google Play purchase token | Your phone and our server | Yes, with AI requests, if you subscribe |
| Name, email, location, contacts, advertising ID | Not collected | Not applicable |
No account
Sayved has no sign-up and no login. There is no profile on our side to look you up by. The app never asks for your name, email address, phone number or date of birth, and it does not read your contacts, your location or your advertising ID. Some features let you type body measurements or names of family members; those stay on your phone (see family members).
Because there is no account, we cannot see your log, restore it for you, or tell which person a request came from. That is deliberate, and it also means some things (backups, new phones) are in your hands. See backup and a new phone.
What stays on your phone
Everything you record is written to a database on your device before anything else happens: what you said (as text), what you typed, your photos at their original resolution, the values derived from them, and every correction you make. Corrections are stored beside the original reading rather than over it. Charts, reports, the doctor report, the energy baseline, conditions, routines and reminder schedules are all built and kept on the phone.
Because the capture is saved first, a failed connection never loses an entry. Uninstalling the app removes this database. Clearing the app's storage does the same.
Your voice
When you speak, Sayved asks your phone's speech recogniser to work on the device itself. The app only keeps the resulting text. It does not record audio to a file and does not upload audio anywhere. The recogniser is part of your phone's operating system, supplied by your phone's maker or Google, and its own behaviour is governed by their terms. If your phone lacks an on-device recogniser for your language, you can type instead.
Your photos and documents
Original photos never leave your phone through Sayved. When you capture a meal, label, or medical document, the app makes a smaller copy and re-encodes it as a JPEG. Food and scene photos are reduced to about 640 pixels on the long edge. Document pages, which need to stay legible, are reduced to about 1,536 pixels. Only that smaller copy is sent, up to six images per entry, and it is used to read the photo and then discarded by us. The app does not add location information to it.
What leaves your phone, step by step
- You capture. Speech is transcribed on the phone; the entry is saved locally straight away.
- The app prepares a request. It contains the text and/or the reduced photos, your phone's local time (so "yesterday at 10pm" resolves correctly), your language setting (used to write the summary of a photo in your language), your device code, and your purchase token if you subscribe.
- Our server checks and forwards. It validates the device code and subscription state, counts the request against the daily fair-use limit, and passes the content to OpenAI.
- OpenAI returns structured data. The server relays it back without storing the content.
- Your phone saves the result beside the original capture, where you can edit it.
When you use Ask, your phone first searches its own database and picks the matching entries (at most 80). It sends your question and those entries (time, category, summary, extracted values and your corrections) along the same route. Your whole history is never sent. Selected entries can belong to any category, including sensitive ones, if your question concerns them.
Not sent at any step: your name, email, location, contacts, advertising ID, audio, original photos, family member names, body measurements entered for the energy baseline, or the list of conditions you track.
The AI processor
The AI processor is OpenAI, used through its API. At the time of writing, both structuring a capture and answering an Ask question use OpenAI's gpt-4o-mini model. OpenAI's API terms state that data submitted through the API is not used to train its models, and that it may be kept for a limited period for abuse monitoring. See openai.com/policies. The key to that API is held on our server and is never inside the app. If we change provider or add one, we will update this page, and the Google Play policy, before the change reaches the app.
What our server keeps
Our server does not store the content of your entries: not the text, not the photos, not your questions or the answers. It does keep a few small operational records:
- Daily counters. For each device code, how many photo, text and Ask requests it made today, so the fair-use limits can be applied. The counters reset every day (UTC).
- Trial start. The time our server first saw each device code, to count the 14-day free trial. This record is kept for as long as the service runs.
- Subscription checks. For each purchase token we have seen: Google's answer about whether it is active, the subscription state and expiry, when we last checked, and up to ten device codes that presented it (to notice one subscription being shared widely). Records for tokens that are not active are removed after 30 days; active ones are kept while the subscription lasts.
- Operational logs. Lines recording which route ran, which model answered, how many tokens were used, and any error message. They hold no entry content. Like any internet service, our server and its hosting see the network address your phone connects from, which is used for abuse limiting.
The device code
The first time you open Sayved it creates a random code on your phone. It is not your Android ID, your advertising ID or anything derived from your hardware or Google account. It is sent with each AI request so the daily limits and the trial can be counted per install. Clearing app storage or uninstalling erases it, and reinstalling creates a new one. The code is not used for advertising, analytics or profiling. If you email support from the Report a problem screen, the code is included in the message you send so we can look into the problem.
Subscriptions and Google Play
Sayved Pro (2.99 USD a month after 14 days free) is sold and billed by Google Play. We never see your card or payment details; Google handles them under its own privacy policy. After you subscribe, Google gives the app a purchase token, which the app keeps on your phone and sends with AI requests. Our server asks Google, using a read-only connection to the Play Developer API, whether that token is currently active. That is the only use of the token. What you have already logged stays on your phone and stays readable if you stop subscribing.
Family members and children
You can add people you log for, such as a child or a parent. Each person gets a separate database on your phone. Any name or label you give them stays on the phone and is never sent to us. The processing request for a family member looks the same as your own: our server cannot tell which person, if any, an entry belongs to. Reminders for every person are scheduled on the same phone.
Sayved is not designed for children to use themselves and is not intended for anyone under 16. If you log for a child, you are the person using the app, and you should be their parent or guardian or have the consent of the adult concerned. We hold no account for a child and nothing that identifies one.
Sensitive categories
A life log can hold health information: symptoms, medication, mood, weight, intimate activity. Sayved treats these categories like any other for processing, but marks health, medication, mood and energy, and intimacy as sensitive. Sensitive entries are left out of CSV exports and doctor reports unless you opt in, and they are never shown in the home-screen widget or in notifications. Conditions you track are used only on your phone. Remember that if you capture a sensitive entry, or ask a question about one, that text is sent for AI processing like any other (see above).
Notifications and the widget
Reminders are scheduled by your phone itself, with no push service and nothing sent to us. A reminder shows your own label or the neutral words "Anything to log?" with no body text. If you track a condition, a rare nudge reads "Still tracking what you added?" and never names the condition. Android needs permission to show notifications and to restore your schedule after a restart. The home-screen widget shows today's date and calorie, protein, carbohydrate and fat totals, calculated on the phone.
Exports and sharing
You can export your log as a CSV file and create a doctor report (a web page file). Sayved writes the file temporarily on your phone and opens Android's share sheet; you decide where it goes. We do not receive it. Once you send it to an email app, cloud drive or another person, it is handled by that service or person, not by Sayved. Sensitive categories are excluded unless you choose to include them.
What we never do
- No advertising, ad networks or advertising IDs.
- No analytics, telemetry or crash-reporting service in the app.
- No selling, renting or sharing of your data for anyone's own purposes.
- No profile of you, and no tracking across apps or websites.
- No use of your entries to train AI models.
- No recording or uploading of your voice.
Permissions
| Permission | Why | Required? |
|---|---|---|
| Microphone | Transcribe speech on the phone | No, you can type |
| Camera | Photograph a meal, label or document | No, you can pick a file or use voice or text |
| Internet | Send captures and questions for AI processing; check subscription | Needed for processing; entries still save without it |
| Notifications | Show reminders you set up | No |
| Run at start-up | Restore reminder schedules after the phone restarts | No |
Choosing a photo from your gallery or files uses Android's own picker and needs no storage permission.
Retention
| Data | How long |
|---|---|
| Your log and photos | On your phone until you delete them or uninstall |
| Voice audio | Not kept |
| Content sent for processing | Not kept by us; kept by OpenAI only as its API terms allow |
| Daily counters | Reset every day |
| Trial start time per device code | For as long as the service runs; deletion on request, see Your rights |
| Purchase verdicts | 30 days for inactive tokens; while subscribed for active ones |
| Operational logs | Short-lived, no entry content |
Security
Traffic between the app and our server is encrypted in transit (HTTPS). The AI key and Google verification credentials stay on the server. Your database is protected by Android's app sandbox and, if you have set one, your phone's lock and device encryption. No system is perfectly secure, but because our server holds no copy of your entries, a breach of it would not expose your log. Your phone's own system backup, if you have it switched on, is handled by Android and Google under your settings, not by Sayved.
International transfers
Our server and OpenAI may process data outside your country, including in the United States. What is sent is the content of a capture or question and the random codes described above, without your name or contact details.
Your rights
Depending on where you live (for example under the GDPR, the UK GDPR or the UAE data protection law), you may have rights to access, correct, delete, restrict or object to the processing of your personal data, to move it, and to complain to your data protection authority. In practice:
- Access and correction: all your data is in the app, and every derived value can be edited.
- Deletion: delete an entry in the app, or uninstall to remove everything. To remove the records our server holds about your device code or purchase token, email us with the code (shown in Settings) and we will delete them.
- Portability: export your log as CSV.
We use the content you submit only to carry out the structuring or answer you asked for, which is the legal basis (performance of the service you requested). We respond to requests within 30 days.
Changes
If our practices change, we will update this page and the Google Play policy and change the date above before the change reaches the app.
Contact
Kamil Dzikowski, [email protected]. See also the terms of use and the medical disclaimer.