Mezura AI — Privacy Policy
Mezura AI is a personal logbook for meals, training and health. This policy (which is also the information notice KVKK article 10 requires) explains what the app stores, why, where it goes, how long it is kept and how to have it removed. The short version: your log belongs to you, it is used only to run the features you use, it is never sold, and the app contains no advertising SDKs. A Turkish version is at /privacy-tr.
Who is responsible for your data
The data controller for Mezura AI (under KVKK, the veri sorumlusu) is [FULL LEGAL NAME], [POSTAL ADDRESS], an individual developer based in Turkey. Write to onratlgn@gmail.com about anything in this policy.
Mezura AI, Ayna AI and Maske AI come from the same developer and share one account: signing in to one with the same Google, Apple or email sign-in opens the same account in the others, and the three keep their data in the same Google Firebase project. Each app reads only its own data. The other apps' policies are at /privacy, /ayna/privacy and /maske/privacy.
Our representative in the European Union under article 27 of the GDPR: [EU REPRESENTATIVE: NAME AND ADDRESS].
What the app stores
- Your account. When you sign in with Google, Apple or an email address and password, Firebase Authentication keeps your account identifier, your email address and, if the provider shares it, your name. Apple's "Hide My Email" address works.
- Your log. Meals and their photos, nutrition targets, saved recipes, training places, routines, workouts, assistant conversations, the memories the assistants keep about your preferences (which you can see and delete in Settings) and your cross-device settings. They are stored in Google Firebase (Cloud Firestore and Cloud Storage) under your account, so they sync between your devices. Meal photos keep the location metadata your camera wrote into them.
- Recipes you share. Sharing a recipe by link stores a copy of it, without your private note or cover photo, that anyone holding the link can read. It is deleted with your account.
- Package labels you confirm. When you scan a barcode and the app reads a food's nutrition label or a supplement's or medicine's box, the product's printed details are saved to a catalogue shared by all users, so the next person who scans it gets the right figures. An entry holds only the product's details and an internal account identifier that lets you correct your own reading: never your name, email, meals or health records.
Health data
Some of what Mezura can keep is health data, a special category of personal data under KVKK article 6 and GDPR article 9. The app asks for your explicit consent before any of it is used, the first time you turn on one of these, and you can withdraw it in Settings → Privacy at any time:
- Health (off until you turn it on): lab results and the photos or PDFs they were read from, vitals, your supplement and medicine stack and dose log, and health goals. Stored in your account like the rest of the log. A medicine search sends only the name you typed to the U.S. National Library of Medicine's public RxTerms service.
- Body data from Apple Health or Health Connect: your age, sex, height, weight, body composition, activity and sleep are read on the phone when an assistant needs them and sent only as context for that conversation; a new weigh-in is stored in your account with the feedback on it.
- Imported workouts from Apple Health or Health Connect keep their time, energy, distance and a summary of their heart rate in your account.
Health data is never used for advertising, never shared with anyone outside the providers below, and never sent to Google Analytics or Crashlytics. The assistants outside Health read your Health records only for the sources you switch on in Health → Privacy, which can also lock Health behind Face ID and delete everything it holds. Withdrawing consent turns Health and body data off and, if you choose, deletes the Health records and weigh-ins; imported workouts keep their heart rate until you delete them. Nothing the assistants say about health is a diagnosis.
What stays on your device
- Writing nutrition and workouts to Apple Health or Health Connect, if you turn it on.
- Calendar entries for planned sessions, scheduled notifications and check-ins, your appearance choice, whether crash reports and usage counts are sent, and sign-ins to Instagram or TikTok made inside the app for recipe import (those sessions live only in the app's web storage on your phone).
- Your current location, if you choose to use it when placing a training place on the map. Only the place you save is stored, not your movements.
AI features
The assistants run on Google's Gemini models through Firebase AI Logic (Vertex AI). On the Max plan you can also choose Anthropic's Claude models, which run on Google Cloud's Vertex AI too, as a model Google serves; Anthropic acts as Google's subprocessor for them. When you use an assistant, what that conversation needs (the meal photo or lab report, your messages, relevant parts of your log, targets, memories and, with your consent, health figures) is sent to produce the reply. These models are reached through Google's global endpoint, so a request may be processed in any of Google's regions, including outside the EU. Under Google Cloud's terms this data is not used to train the models.
The assistants may look up foods and recipes in public databases (USDA FoodData Central, Open Food Facts, TheMealDB, API Ninjas); those lookups carry only the search term or barcode, never anything that identifies you. When you import a recipe from a link, the app fetches that page.
Connecting Mezura to another AI app
You can choose to connect your Mezura account to an AI assistant of your own, such as Claude or ChatGPT, so it can read your log. Nothing is shared until you sign in on our consent page and allow it, and you choose what it may read: your meals, nutrition totals, targets, weigh-ins and food memories, and, if you use the sport coach, your workouts, routines and training memories. The connection is read-only. Your Health records (lab results, vitals, supplements and medical documents) are never shared through it.
Once you allow it, that app's provider receives what its assistant reads, and handles it under its own terms and privacy policy, not ours. You can end a connection at any time from that app; deleting your Mezura account ends every connection at once. We keep a record of each connection (which app, what you allowed, when it was last used) for as long as it exists.
Crash reports and usage counts
Unless you turn them off in Settings → Privacy, the app sends crash reports (Firebase Crashlytics) and counts of how it is used (Google Analytics for Firebase) to Google: which screens are opened, that a meal was logged or an assistant replied, how long a reply took, and your plan, language and app settings. They carry a random identifier for this installation, the app version and device model. They never include anything you logged (meals, photos, messages, health data), nor your name, email, account identifier or advertising identifier, and they are not used for advertising or to track you across apps. Turning them off, or deleting your account, resets this phone's analytics identifier.
Purchases
Subscriptions and credit packs are sold by Apple or Google and managed through RevenueCat, which receives your app account identifier and your purchase history to confirm what you have unlocked. The app never sees your payment details. Your credit balance, shared with Ayna AI, is kept in your account.
Why we process your data, and on what legal basis
| What we do | Why | Legal basis |
|---|---|---|
| Your account, and keeping your log in sync | To provide the app you signed up for | Performance of a contract (KVKK art. 5(2)(c); GDPR art. 6(1)(b)) |
| Health records, body data, weigh-ins, sleep and workout heart rate, stored and sent to the assistants | To run Health and the body-aware features you turned on | Your explicit consent (KVKK art. 6; GDPR art. 9(2)(a)) |
| Sending a conversation's content to the AI model | To produce the reply you asked for | Performance of a contract; explicit consent for any health data in it |
| Package labels in the shared food and supplement catalogues | So everyone's scans read correctly | Legitimate interest (KVKK art. 5(2)(f); GDPR art. 6(1)(f)) |
| Purchases and credits | To unlock what you paid for and keep billing records | Performance of a contract; legal obligation |
| Crash reports and usage counts | To find what breaks and what is used | Legitimate interest; you can turn them off in Settings → Privacy |
| App Check and request limits | To keep abuse and fraud out | Legitimate interest |
| Answering your requests and keeping a record of deletions | To meet our legal duties | Legal obligation (KVKK art. 5(2)(ç); GDPR art. 6(1)(c)) |
Who receives it
- Google (Firebase Authentication, Firestore, Storage, Functions, App Check, Remote Config, AI Logic and Vertex AI, Crashlytics, Analytics): hosting, sync, abuse protection, the AI models, crash reports and usage counts. Google acts as our processor.
- Anthropic, through Google Cloud: the Claude models, for Max users who choose them.
- RevenueCat: subscription status.
- An AI app you connect yourself (see above): what you allowed it to read, under its own terms.
- Apple and Google: sign-in and payment, under their own privacy policies.
- Public authorities, only where the law requires it.
We do not sell personal data, share it for advertising, or use advertising SDKs.
Where your data is processed, and transfers abroad
Your account's database, files and our server functions are in Google Cloud's European Union regions (the eur3 multi-region and europe-west1). For anyone in Turkey that is a transfer of personal data abroad. The AI models, Firebase Authentication, Crashlytics and Analytics may process data outside the EU, including in the United States. Google, RevenueCat and Google's other processors may also reach data from other countries, including the United States, to run and support their services.
These transfers rely on appropriate safeguards: for transfers from Turkey, the standard contracts under article 9 of KVKK concluded with these providers and notified to the Personal Data Protection Authority; for transfers from the EU, the European Commission's standard contractual clauses in the providers' data processing terms and, where a provider is certified, the EU–US Data Privacy Framework. For health data the explicit consent you give in the app covers these transfers as well.
How long it is kept
| Data | How long |
|---|---|
| Your account and everything stored under it | As long as you have the account. Deleting it removes everything 30 days later (see below). |
| An entry, photo, recipe or memory you delete | Removed from the cloud when you delete it |
| Crash reports (Crashlytics) | 90 days |
| Usage counts (Google Analytics) | At most 14 months |
| Purchase history at RevenueCat, Apple and Google | As long as their legal and accounting duties require |
| Your emails to us | As long as needed to answer them, and as the law requires after |
| Product readings in the shared catalogues | They stay, as a product's printed facts, no longer linked to a living account |
To delete your whole account, go to Settings → Account → Delete account in the app (or write to us). You are signed out and the copy on your phone is cleared at once; the account is then kept for 30 days in case you change your mind (signing back in within that time restores it), after which your sign-in and everything stored under it, in all three apps, are deleted for good.
Children
Mezura AI is not directed at children under 16 and does not knowingly collect their data. If you believe a child has given us data, write to us and we will delete it.
Your rights
Under article 11 of KVKK you may ask us whether we process your personal data and, if so, for information about it; the purpose of processing and whether it is used for that purpose; the third parties in Turkey or abroad it is transferred to; to have incomplete or wrong data corrected; to have it deleted or destroyed under article 7, and to have third parties it was transferred to told of a correction or deletion; to object to a result against you that arises from analysis by automated systems alone; and to claim compensation for damage caused by unlawful processing.
Under the GDPR you also have the right of access, rectification, erasure, restriction of processing, data portability, to object to processing based on legitimate interests (articles 15–21), and to withdraw a consent at any time without affecting what was done before.
Much of this you can do yourself in the app: see and delete each entry, photo and memory, withdraw a consent in Settings, and delete the whole account. For anything else, write to onratlgn@gmail.com from the address of your account (so we can tell the request is yours), or by post to the address above. Requests are answered free of charge within 30 days. If you are not satisfied with the answer, or get none, you can complain to the Personal Data Protection Board (kvkk.gov.tr) within the periods article 14 of KVKK sets, or, in the EU, to the data protection authority where you live or work.
No decision with legal or similarly significant effects is made about you by automated means alone.
Security
Data travels encrypted, and the database's rules let each account read and write only its own documents. Requests are checked with Firebase App Check so only the genuine app reaches the servers. If a breach ever puts your data at risk, we will tell you and the authorities as the law requires.
Changes
If this policy changes, the date above changes with it, and significant changes are announced in the app's release notes. A change to what a consent covers asks for it again.
Contact
Questions or requests: onratlgn@gmail.com, or by post to [POSTAL ADDRESS].