Privacy Policy

Last updated: 6 November 2026 · Version 1.2 · What changed

1. In short

Sofra is a calorie and nutrition tracking app for iPhone (iOS 17 or later). It has no account system. The body details, meals, water and weight entries you record stay on your device and, if enabled, in your own iCloud. We, the developer, cannot access them. The app contains no analytics or advertising tools.

Only when you use the optional AI features (adding by chat, online food lookup, suggestions), and only after giving separate explicit consent, is the photo you send or the message you write sent through the developer's server to Anthropic's Claude model. If you do not enable this, the app works fully with search and manual entry. See section 6.

2. Data controller

Tomris Bilge Bilgiç
Güvenlik Caddesi Defne Sokak No: 18 Daire: 3, Çankaya / Ankara, Türkiye
Contact channel: contact form

How data is collected. Personal data is collected only to the extent you enter or send it, through the app interface and the form on this website, electronically and by automated means. Each processing activity below is carried out for the stated purpose and on the stated legal basis.

3. Data you enter in the app

The sex, birth year, height, weight, goal and activity level you enter during setup, and the meals, portions, water and weight measurements you log during the day, are written only to the database on your device. We have no access to this data. It is never transmitted to us, processed by us or shared with third parties. Your daily and weekly calorie budget is calculated from these details on your device.

4. iCloud sync

If iCloud sync is enabled, your data syncs to the private CloudKit database tied to your Apple Account. Apple does not give app developers access to private databases. Sync is governed by Apple's privacy policy: apple.com/legal/privacy. You can turn sync off in the app's Settings or in iOS Settings, in which case data stays on the device only.

5. Health data (HealthKit)

Sofra connects to Apple Health only when you tap "Connect Apple Health"; nothing is requested during setup. You first see Sofra's own explicit consent screen (the box is not pre-ticked); only if you agree does Apple's permission sheet open. If you allow it, Sofra only reads your step count and active energy from Health; on days you move more than usual, the extra is added to your daily budget. The weight measurements you enter are written to Health if you allowed weight writing on Apple's sheet. Sofra does not read weight from Health.

Health data is never sent to any server, never written to iCloud and never included in AI requests. It is not used for advertising, marketing or analytics, and is never sold or shared with third parties. Health data is a special category of personal data; it is processed only on your device, on the basis of your explicit consent (KVKK Art. 6; GDPR Art. 9(2)(a)). You can withdraw consent at any time in the app under Profile › Apple Health › "Withdraw Apple Health consent", after which Sofra neither reads from nor writes to Health. You can also revoke Apple's permission under iOS Settings › Health › Data Access & Devices › Sofra, and delete weight entries written to Health from the Health app.

6. AI features (optional)

What they do. On the add-by-chat screen, from what you write, say or send as a photo (for example "1 portion chicken sauté, 200 g bread"), the app prepares a meal draft and updates it with corrections such as "make the bread 1 slice". It also produces pantry ideas from a fridge photo, and meal suggestions. In search, if a food is not in the built-in list and you tap "Look up online", they also fetch typical nutrition values for the food name you typed. The first time you use these features you see a separate consent screen; if you decline, the feature stays off and search and manual entry work fully. You can withdraw consent at any time in the app's Settings.

What is sent. The photo you send, the message you write or say (in the chat, together with the food names and portions in the current meal draft and at most the last 6 short messages), or the food name you look up online (when a food is not in the built-in list and you tap "Look up online") is relayed through the developer's serverless function on Vercel Inc. (Frankfurt, Germany region) to Anthropic PBC's Claude model in the United States. Location and camera metadata are stripped from photos on your device before sending. Your weight, goal, age, sex and Health data are never sent. For meal suggestions, only "remaining calories and macros" rounded to the nearest 50 are included; no personal profile can be derived from them.

What is stored. The developer's server does not store photos, messages or chats; it forwards the request to the model provider and returns the answer to your device. The chat history exists only in your device's memory while the chat screen is open. The server keeps only usage counters: an HMAC digest of the device identifier, the number of requests and the date; on the free tier, a digest of the chat identifier for at most 2 hours to count follow-up messages for the same meal. These counters are stored in Supabase's European Union (Frankfurt, Germany) region, do not identify a person and are deleted automatically within 2 days at most. A food name looked up online and the nutrition values found for it (for example "pomegranate molasses: 268 kcal per 100 g") are cached for up to 180 days, without any link to an identity, so that the same lookup is answered quickly for everyone; who searched is not recorded. For packaged products the server first sends only the product name to the open database Open Food Facts (Open Food Facts association, France; data licensed under ODbL); nothing about you is included in that request.

Keeping the food list up to date. To keep the built-in food list current, the app downloads the public list file from the developer's website at most once a day. No data about you is sent with this request.

On Anthropic's side. Under Anthropic's commercial API terms, Anthropic does not use inputs and outputs sent through the API to train its models. Anthropic's retention periods and terms of use are governed by Anthropic's commercial terms and privacy policy: anthropic.com/legal/privacy.

Legal basis. Your explicit consent for processing the photo and text (KVKK Art. 5(1); GDPR Art. 6(1)(a)) and for the international transfer to Anthropic in the USA (KVKK Art. 9; GDPR Art. 49(1)(a)). Both points are stated separately on the consent screen.

7. Device verification (App Attest)

To verify that AI requests come from the genuine Sofra app on a real iPhone, the app uses Apple's App Attest service. The server stores only a digest of the attestation key identifier, its public key and a counter; these do not identify a person and are processed to prevent abuse of the quota. The record is deleted automatically if unused for 400 days. Legal basis: our legitimate interest in protecting the service (KVKK Art. 5(2)(f); GDPR Art. 6(1)(f)).

8. Speech recognition

If you choose to say your meal aloud, the app uses Apple's Speech framework. If your device supports on-device recognition, the audio stays on your device; otherwise the audio is sent to Apple's servers for transcription. The app tells you about this once. Processing on Apple's side is governed by Apple's privacy policy: apple.com/legal/privacy. The transcribed text is processed as described in section 6 only when you tap send and only if you have given AI consent. You can turn off microphone and speech recognition permissions in iOS Settings at any time.

9. Notifications

Logging reminders are scheduled locally on your device; no push server is involved. Permission is optional and can be revoked in iOS Settings at any time.

10. Sofra Pro and purchases

Sofra Pro is sold through the App Store by Apple. Your payment and card details never reach the app or us. The app reads the transaction receipt Apple provides on the device to unlock Pro features. Meal entry is unlimited on Pro; to recognise Pro and apply a high daily safety limit against abuse, the server verifies Apple's signed transaction receipt and keeps only a digest of the original transaction identifier as the counter key; this value does not contain your name, Apple Account or payment details. Legal basis: performance of the subscription contract (KVKK Art. 5(2)(c); GDPR Art. 6(1)(b)).

11. Contact form

When you use the contact form in the app or on this site, your message, chosen topic, optional email address and technical details (app version, OS version, language) are emailed to us. Legal basis: our legitimate interest in answering you (GDPR Art. 6(1)(f) / KVKK Art. 5(2)(f)) and, for the international transfer, the explicit consent you give with the checkbox (KVKK Art. 9). Transmission goes through Vercel Inc. (serverless function) and Resend Inc. (email delivery) as processors; both operate servers in the USA and only relay the message. Your message is used solely to respond, is not shared with third parties and is deleted no later than one year after the matter is closed. Using the form is optional; you may instead write to the postal address above.

12. Summary

DataWhereWho can accessPurposeLegal basis
Body details, meals, water and weight entriesDevice + your own iCloudOnly youBudget calculation and trackingNot transferred to the developer; processed on your device by you
Health data (reading steps and active energy; writing the weight you log)Device (Health app)Only youCounting extra movement toward your budget; saving weight to HealthIn-app explicit consent (KVKK Art. 6) and Apple permission; on device only
Photo, chat message, meal draft or looked-up food name (AI)Via Vercel (Frankfurt) to Anthropic (USA); photos and chats not stored, lookup results cached without identity for 180 daysAnthropic as processor; the developer does not see the contentFood recognition, calorie calculation and suggestionsExplicit consent (KVKK Art. 5(1) and Art. 9)
Usage counters (device ID digest, count, date; chat ID digest for 2 hours; App Attest key record for 400 days)Supabase (EU, Frankfurt)Developer; does not identify a personQuota and abuse preventionLegitimate interest (KVKK Art. 5(2)(f))
Purchase status (transaction ID digest)Apple / device; digest in Supabase (EU)Apple and you; developer for the digestUnlocking Pro and its quotaContract (KVKK Art. 5(2)(c))
Contact form messageVia Vercel and Resend to our mailboxDeveloperAnswering youLegitimate interest (Art. 5(2)(f)); explicit consent for transfer (Art. 9)

13. Cookies and tracking

The app uses no cookies, advertising identifiers, fingerprinting or analytics SDKs. This website is static and sets no cookies.

14. Children

The app is rated 12+ on the App Store, is not directed at children and does not knowingly collect data from children. No calorie-deficit goal is set for users under 18.

15. Your rights

Under Turkish KVKK, GDPR and similar laws you may request access, rectification, erasure, restriction and portability, and object to processing. Use the contact form or write to the postal address above; we respond within 30 days.

Because only you hold the in-app data, deletion is in your hands: delete the app, and remove the iCloud copy under iOS Settings › Apple Account › iCloud › Manage Account Storage › Sofra. Weight entries written to Health are deleted from the Health app. Server-side counters do not identify a person and are deleted automatically within 2 days at most, and the App Attest key record after 400 days without use; once you withdraw AI consent, no further requests are sent. EU residents may also complain to their local supervisory authority.

16. Changes

Updates are published on this page with a new date and version number. Material changes are also announced inside the app; if AI processing changes, your consent is requested again.

Version 1.2 (6 November 2026): added meal entry by chat (the draft and recent messages are sent), so AI consent is requested again; added an in-app explicit consent screen for Apple Health and clarified that Sofra does not read weight from Health; corrected the counter storage region (Frankfurt), the App Attest retention period (400 days) and the age rating (12+); added how data is collected.