Effective 28 September 2026 · Version 2026-09-28
Ölçü is an app that records your weight, what you eat and how you feel. That is health data, and we treat it as such. This page explains, in plain language, everything we keep and where it goes. It is the English version of the Turkish privacy policy; the legal detail under Turkish law is in the KVKK disclosure notice (in Turkish).
Only what you enter, under these headings:
We do not collect your location, your contacts, the rest of your photo library, your browsing history, or what you do in other apps.
A phone camera writes more than the picture into a photo: GPS coordinates, the device make and model, the time it was taken, sometimes the owner's name. None of it is visible, but it all travels if the file is sent as it is.
So every photo you upload is rebuilt from its pixels alone before it is stored or analysed. All of the metadata is dropped, not part of it. A photo that cannot be decoded is rejected — sending on a file that could not be cleaned is exactly the outcome this exists to prevent.
To do what the app promises you: calculate your target, show you what you have recorded, run the features you use and manage your subscription. And, to improve the app, we count which screens are used (see "Usage statistics"). There is no other purpose — we do not profile you, target ads at you or sell anything to anyone.
The app relies on five service providers. Each receives only what it needs to do its own job.
| Provider | What it receives | When |
|---|---|---|
| Supabase database, sign-in, file storage — data centre in Frankfurt, Germany |
Your account and everything you record; your photos; usage statistics | Always — this is where your data lives |
| OpenAI AI features — USA |
The photo (metadata removed), a voice recording, your message to the assistant, the day's calorie and macro summary, your eating preferences and allergies. Nothing that identifies you. | Only when you use that feature |
| RevenueCat subscriptions — USA |
Your account number, subscription status and — on iPhone — which App Store ad you came from | When a subscription is checked; to measure our ads |
| Google AdMob advertising — Ireland / USA |
Device and advertising identifiers. No health data and none of your records. Only non-personalised ads are requested. | Only in the free version |
| Expo notifications — USA |
Your device's notification token and the notification text | Only if you allowed notifications |
From version 1.0.3, we count which steps of the app are used: opening the app, finishing set-up, adding a meal, seeing the subscription screen, starting a subscription and the like. The point is to see where people get stuck, so we can fix it.
These records have hard limits:
If the app crashes or hits an unexpected error, that is recorded the same way, in our own database: the error's message, where in the code it happened, the app version and the platform. What you typed, your records and your health data do not enter the report; the message and detail are truncated before they are kept. Reports are deleted automatically after 90 days, deleted with your account, and switched off by the same setting.
We advertise on the App Store and want to know which ads work. If you installed the app on iPhone by tapping an Apple ad, our subscription provider RevenueCat learns from Apple which campaign and keyword it was and adds it to your subscription record. This uses a token Apple generates that contains no device identifier; it is not used to recognise you in other apps or to show you ads, so no tracking permission is asked for. Your health data is never added to it. The same setting switches it off: if statistics are off, this is not collected either.
Ölçü is available in EU App Stores, and the General Data Protection Regulation applies to users there. The following adds to the rest of this page; it does not replace it.
Ölçü is not intended for anyone under 18 and does not knowingly collect data from that age group. If we learn that we are processing a child's data, the account and its data are deleted. Calorie restriction carries health risks during growth, so this limit should be taken seriously.
No system is unbreakable. If a security incident affects your data, it will be reported to the authority and to you as the law requires.
From Profile → Data and privacy, without asking anyone, you can:
When this policy changes, the version and date above change. If a change affects the scope of a consent you gave, the app shows you the consent screen again.
28 September 2026: the "Which ad you came from" section was added, and it was listed among the data that goes to RevenueCat. Because the data sent abroad now covers more, the consent screen is shown again.
25 September 2026: the usage statistics, crash reports and European Union sections were added. The scope of your health-data and international-transfer consents did not change — the statistics contain no health data and are kept in the database you already consented to — so the consent screen is not shown again.