EatWell

EatWell Privacy Policy

Version: privacy-2026-07-26-draft.4 · Effective: 21 July 2026 Status: In force — approved by legal counsel Last updated: 5 November 2026 — Android app added (Health Connect, Google Play purchases, push notifications, on-device recognition); Firebase Crashlytics crash and sign-in error reports

If you create an account, we may process your name, e-mail and account identifier. When you use the app, we may process nutrition, water, weight, body composition, goal and preference records. App Store or Google Play product and transaction-verification data is processed when you purchase. Apple Health (HealthKit) and Health Connect categories are accessed only with permission. Camera, audio, lab and AI data is not collected while those features are disabled.

We use data to operate your account and diary, provide insights, deliver purchase entitlements, synchronise records, maintain security and answer support requests. We do not sell health data or use it for advertising.

Anonymous usage analytics are on by default. To improve the app, usage events such as which screens were opened, at which step you left, whether an action succeeded and session length are sent to our own servers and to our analytics provider TelemetryDeck GmbH (Germany, EU). This data contains no name, e-mail, account identifier, text you write, photos or health value. A random identifier generated for the device is one-way hashed on your device before it is sent and is not linked to your account; technical details such as device model, OS and app version, language and region are added. You can turn this off any time with the “Anonymous analytics” switch in Profile › Privacy; sending stops and pending events on the device are deleted.

While the same switch is on, two more pieces of anonymous diagnostic information are sent. Food searches that return nothing (only to our own servers): to see what the catalogue is missing, a search term or scanned barcode number that produced no result is counted. The term is filtered on the device and on the server; text containing a digit or @, very short text, or text longer than 40 characters is never sent or stored. Terms are kept only as a “how many times searched” counter, not linked to your account, device or time. Crash and error reports: if the app crashes, or a step such as sign-up or sign-in fails, a technical report (app/OS version, device model, where in the code it crashed or the error's technical code) is sent to our own servers (Apple MetricKit on iOS, the app's own crash report on Android) and to Google's Firebase Crashlytics. It carries no name, email, content you entered or health data and is not linked to your account; Crashlytics uses a randomly generated installation identifier for the device.

iOS permissions for camera, Photos, microphone, speech recognition, notifications, Face ID and HealthKit are requested only for relevant features and can be revoked in Settings. Apple and Google/Firebase may be used for identity, Apple or Google Play processes in-app purchases, and Google's Gemini API powers the AI features (explained below). The final processor list and data regions must be published before launch.

On Android, the same features use the platform equivalents. Permissions for the camera, microphone, notifications, exact alarms (fasting and cooking timers) and Health Connect are requested only when you use the related feature and can be revoked in Android Settings or in the Health Connect app. With your permission the app reads steps, active calories burned, exercise sessions, weight, body fat and lean body mass from Health Connect, and writes the workouts and active calories you log in the app. Health Connect data is used only to show your activity and body measurements, calculate your daily balance and, if you choose, share it with your dietitian; it is never used for advertising and never sold. Purchases are processed by Google Play; we receive the purchase token and subscription status to verify your entitlement. Push notifications are delivered through Firebase Cloud Messaging using a device token. Voice logging uses the device's speech recognition service, on the device where available. Barcode, nutrition-label, lab-document and scale-printout reading run on your device with Google's ML Kit; the photo is not sent to our server for these. App integrity is checked with Google Play Integrity (Firebase App Check), which does not give us personal data.

Your health data is shared with no one unless you connect to a dietitian. When you connect you pick the categories individually, and the dietitian sees only the last 28 days. Connecting also makes your previous 28 days visible — we state this on the connect screen before you connect. Stopping sharing closes access immediately, including the past. A dietitian cannot edit or delete your records. The one exception is body composition: while that category and weight sharing are on, your dietitian can add a body composition measurement they took in a session to your records (a weight entry is created with it). It is marked “Entered by a dietitian”, you get a notification, and you can edit or delete it. The categories that can be shared are nutrition logs, weight, water, exercise logs, health profile, lab results, weekly check-ins and body composition. The weekly check-in and body composition categories are off by default for everyone; your existing sharing does not widen on its own (details below). Because a body composition record also carries your weight, that category is visible to a dietitian only while weight is shared too.

When you ask the AI assistant a question, log a meal or water by typing, or send a meal photo for recognition, the content goes through our server to Google's Gemini API: your question; your sentence with your device's date, time and time zone; or the photo (metadata including location is removed on your device). If “Allow AI Assistant to use this profile” is on in your health profile, your age, height, weight, diet preference, condition and allergy categories are added to questions. If the separate “Let the assistant see my dietitian's program” option is on, the eat and avoid lists and the calorie, protein and water targets of your dietitian's program running that week are added too. Both options are off by default. If the third, separate “Let the assistant see today's log” option is on, today's calorie, protein, carb, fat and water totals, your daily targets and the names of the foods you logged today are added as well; amounts, times and notes are not. This option is on by default and can be turned off in your health profile. Your name, e-mail, medications, supplements, your dietitian's name and program note, and earlier messages are not sent. Google does not use this content to improve its products or train models; it may log it for a limited period only to prevent abuse. The Gemini API runs outside Türkiye. Your question, sentence and photo are not stored on our server. The generated answer (assistant reply, meal draft, recognition result) is kept against your account for 30 days so a repeated request is not processed twice, and is deleted when that period ends or when you delete your account. The AI never logs a meal on its own; you confirm each draft.

Your AI chat history — conversation, typed-logging drafts and photo result cards — is stored on your device only, in a protected area reserved for your account, excluded from device backups and not sent to our server. The newest 300 items are kept, and the small photo previews in cards are deleted after 14 days. You can delete the history any time in Profile › “Clear AI chat history” or from the chat menu; it is also deleted when you delete your account. Meals already in your diary stay.

If you log a meal with a photo, the image stays on your device for 14 days and is deleted the next time you open the app after that; the meal record stays. You can delete any photo at any time. While dietitian sharing is off, photos do not leave your device; once you enable nutrition sharing the image is also stored on our server for 14 days and your dietitian views it through a short-lived link. Stopping sharing and deleting your account both delete the server-side images. Audio and lab document images are never retained after processing.

Body composition (body fat, fat-free mass, muscle, water, visceral fat, basal metabolism, waist) is added in three ways: you enter it by hand; it is read from the Apple Health or Health Connect data you allow (body fat percentage, lean body mass; waist circumference from Apple Health only); or you scan a photo of a scale printout. Scanning runs on your device with on-device text recognition (Apple's on iOS, Google ML Kit on Android): the photo is not stored and is not sent to our server or to any AI service; you confirm the values read before saving. Measurements sync with your account like your other records and are included in data export. You can choose in your target settings to use the basal metabolism your scale measured for your calorie target; your dietitian can also ask for it in a program, and it is switched on when you apply the targets.

If you prepare a weekly check-in for a dietitian, the progress photos (up to three angles), your weight and waist measurement, your mood, the private note for your dietitian and the log-adherence preview calculated on the device are first stored as a draft on your device only, in a protected area excluded from device backups. Photo metadata (including location) is removed on save.

Sending it to your dietitian is a separate choice and is off by default. The first time you tap “Send to my dietitian”, a confirmation page lists what will be sent; if you agree, the “Weekly check-ins” category is added to your sharing. From then on a check-in is sent only when you send it — nothing is sent in the background. When you send, the photos (with metadata stripped again on the server), weight, waist, mood and note reach our server and only that dietitian sees them, through short-lived links. The adherence preview on your device is not sent; the score your dietitian sees is calculated by the server from the program they published. Sending again in the same week replaces the earlier check-in.

The server keeps the latest 12 weeks per dietitian; older weeks are deleted when you send a new one. Turning the category off, pausing or stopping sharing, either of you ending the relationship (including by blocking) and deleting your account delete the check-ins and their photos from the server. In the draft on your device, the previous week's photos are deleted when a new week starts; remaining drafts are deleted when you delete your local drafts or your account. The 14-day rule for meal photos does not apply here.

We use data minimisation, transport encryption, protected local storage, account isolation and access controls. You may delete your account in the app, revoke optional sharing and health consent, and manage system permissions. The app is not directed to anyone under 18 and blocks under-18 registration.

Privacy: privacy@geteatwell.app · Support: support@geteatwell.app · Controller: Harun Yardımcı, Esentepe Mah. Anadolu Cad. And Pastel Sitesi B3/84, Kartal/İstanbul, Türkiye