Privacy Policy

1. At a glance

• Your logs are saved on your phone first. MitFit works without an account and without a connection.
• Raw Apple Health and Health Connect samples never leave your phone. After you sign in, only daily totals are synced.
• Body photos stay on your phone. They are sent once to Google Vertex AI for analysis and are never stored by MitFit's servers or backups.
• Meal photos are sent to Google Vertex AI to estimate nutrition and are not stored there. They are uploaded only if you share a meal with your squad, and are deleted when you delete that meal or post, or your account.
• Your account backup is on by default, encrypted, and can only be restored by your account. You can turn it off.
• We do not sell your data, show ads, or track you across other apps. Analytics stay off unless you agree.
• You can delete your account in the app at any time. Deletion is immediate.

2. Who we are

MitFit is an app by Rexahub, the personal brand under which Sertaç Akdoğan publishes apps. Rexahub is not a company. The data controller for MitFit is Sertaç Akdoğan (Rexahub), Türkiye ("MitFit", "we", "us"). We contact you and you contact us by email; there is no separate postal address for privacy requests.

For anything about privacy, including requests to use your rights, email contact@rexahub.com.

3. What stays on your phone

MitFit is local-first. Everything you log is written to a database on your phone before anything else happens, and the app never waits for the network. This includes:

• meals, food items and nutrients, favourites, water, exercise and weight logs, and body measurements;
• health samples imported from Apple Health or Health Connect (heart rate, heart rate variability, glucose, sleep, steps, blood pressure, VO2 max and similar);
• body analysis results and the body photos used to create them;
• your meal photos (kept for 30 days, 1 year or forever, as you choose in Settings; your logs stay after a photo is removed).

If you use voice input, speech recognition runs on your device. No audio leaves your phone.

If you never sign in, your data stays on your phone. Deleting the app deletes it.

4. What goes to the cloud, and why

When you create an account and sign in, some data is sent to our servers so that MitFit can sync, back up your logs and power squads.

Squad data is created only once you join or create a squad. Many values shown to squads (badges, wins, scores and your public summary) are calculated on our servers from the daily summaries above.

5. Apple Health and Health Connect

If you connect Apple Health (iOS) or Health Connect (Android), MitFit reads the data types you approve and can write back weight, body fat and nutrition entries you create.

• Raw health samples never leave your phone. They are also left out of your account backup and are re-imported from your phone's health app when you restore.
• The only health-derived values in the cloud are daily totals (steps, active energy, workout minutes and counts, weight and trend, sleep and recovery scores) and, only if you turn on body-metric sharing, summary body measurements on your squad profile.
• Health data is never used for advertising, never sold, and never shared with data brokers.
• MitFit's use of information received from Health Connect follows the Health Connect Permissions policy, including its Limited Use requirements.

Health data is special-category data under data protection law. We ask for your explicit consent before processing it, and you can withdraw that consent in Settings at any time.

6. Meal photos and body photos

Meal photos

• Meal photos are stored on your phone.
• When you scan a meal, the photo is sent to Google Vertex AI (Gemini) to estimate what is on the plate. It is processed in memory and not stored by MitFit or kept by Google for training.
• A meal photo is uploaded to our storage (Cloudflare R2) only if you share that meal with your squads. Shared photos are kept until you delete your account or until 1 year after your MitFit Pro subscription lapses. They are deleted straight away if you hide or delete the meal or the post.
• Meal photos are included in your account backup only if you turn on that option.

Body photos

• Body photos are stored only on your phone, in a folder that is excluded from your phone's own backup unless you choose to include it (for example in iCloud Backup).
• When you run a body analysis, the photos are sent once to Google Vertex AI through our server. They are processed in memory and never stored by MitFit's servers or included in MitFit backups.
• The app technically blocks body photos from being uploaded anywhere else.
• The results (numbers and text, not photos) are saved on your phone and in your encrypted backup. Squads never see your body photos.
• You can delete all saved body photos in Settings.

We ask for your consent before your first body analysis.

7. AI features

MitFit uses AI to estimate meals from photos or text, read nutrition labels, evaluate packaged products, parse a day of logs from one sentence, and analyse body photos.

• All AI requests go through our server to Google Vertex AI (Gemini). Google does not use this data to train its models.
• To make estimates relevant, a request can include a minimal summary of your goals and targets. Images are processed in memory only.
• We log technical details of each AI request (task type, model, timing, token counts, errors) under a pseudonymous identifier. These logs never contain your photos, your text or your profile context, and are deleted after 90 days.
• We do not currently use any other AI provider. If that changes, we will update this policy first and use only providers that do not retain your data.

AI estimates can be wrong. See the Health Disclaimer.

8. Account backup

Account backup is on by default so you don't lose your logs if you change or lose your phone.

• What it includes: your meals, items and nutrients, favourites, water, exercise and weight logs, measurements, body analysis results (no photos), insights and settings. Meal photos only if you turn that on.
• What it never includes: raw health samples and body photos.
• Where it is stored: in Cloudflare R2 object storage (US / default jurisdiction, location hint Eastern North America). R2 only ever receives the encrypted file (ciphertext), never readable data.
• How it is protected: your phone encrypts each backup with AES-256 before upload. The encryption key is itself protected by Google Cloud Key Management Service (envelope encryption), and it can be unlocked only when you are signed in to your account. Our storage only ever holds encrypted data.
• This means your backup is encrypted and only restorable by your account. It is not end-to-end encrypted: because the key is managed in our cloud key service, it is not mathematically impossible for MitFit to access it, but our systems are built so that only your signed-in account can restore it.
• We keep your latest 7 backups. Older ones are deleted automatically.
• You can turn backup off in Settings › Privacy & Data › Account backup. Existing backups are then deleted, and your logs live only on your phone.

9. Squads and what others see

• Members of your squads can see your name, username, avatar, bio and goal, and the things you choose to share in Squad privacy: your streak, your meal posts and, if you turn it on, summary body metrics. Body metric sharing is off by default. Body photos are never shared.
• People outside your squads see only a minimal profile card.
• You choose who can find you by search: everyone, friends only, or nobody.
• MitFit is positive-only: we never show other members' calorie overages, missed days or weight loss rankings.
• If you block someone, you stop seeing each other's content and they can't invite, nudge or find you.
• Content you report is reviewed by our team. See the Terms of Use.

10. Sign-in, analytics, crash reports and notifications

We use these Google Firebase services:

• Firebase Authentication for sign-in with Apple, Google or email and password.
• Firebase App Check to check that requests come from the genuine MitFit app (uses Apple App Attest / DeviceCheck and Google Play Integrity).
• Firebase Cloud Messaging to deliver push notifications.
• Firebase Crashlytics to collect crash reports (device model, OS version, app version and the crash trace). It is on by default to help us fix bugs, and you can turn it off in Settings.
• Firebase Remote Config to change app settings and feature flags without an update.
• Google Analytics for Firebase to understand which features are used. It is off until you agree during onboarding, and you can change your mind in Settings. Analytics events never contain health values.

MitFit does not use the advertising identifier (IDFA) and does not track you across other companies' apps or websites.

11. Purchases

MitFit Pro subscriptions are sold by Apple (App Store) and Google (Google Play). We never see your card details. We use RevenueCat to manage subscriptions; it receives your MitFit account identifier and your purchase history, nothing else.

12. Food database lookups

When you scan a barcode or search for a branded food, the app looks it up directly in Open Food Facts, a public food database. Only the barcode or search term is sent, with no account or personal data. Like any website, Open Food Facts can see your device's IP address.

13. Service providers

We use the following providers to run MitFit. They process data only on our instructions, under data processing agreements.

14. Where your data is processed

Our cloud data is stored and processed in the United States (Google Cloud region us-central1, plus Cloudflare and RevenueCat). AI requests use Google's global Vertex AI endpoint, so AI processing may take place in other regions. This means your data is transferred outside Türkiye and the European Economic Area.

• Türkiye (KVKK): we transfer personal data abroad on the basis of your explicit consent, which we ask for at onboarding, and of standard contracts signed with each provider and notified to the Personal Data Protection Authority (KVKK) as required by Article 9 of Law No. 6698.
• EU / EEA and UK (GDPR): we rely on our providers' certification under the EU–US Data Privacy Framework (and its UK extension) and, where a provider is not certified, on the European Commission's Standard Contractual Clauses.

You can ask us for more information about these safeguards at contact@rexahub.com.

15. Legal bases

Withdrawing consent does not affect processing that happened before you withdrew it.

16. How long we keep data

17. Your rights and choices

Depending on where you live, you have the right to:

• access your personal data and get a copy of it;
• correct inaccurate data (most of it you can edit in the app);
• delete your data: delete your account in the app under Profile › Delete Account, or request deletion by email;
• withdraw consent at any time with the toggles in Settings (health import, body analysis, analytics, crash reports, account backup);
• data portability: in-app export isn't available yet, so email contact@rexahub.com from your account email and we will send you an export;
• object to or restrict certain processing;
• under KVKK Article 11, also to learn whether your data is processed, its purpose, the third parties it is transferred to, to ask that corrections or deletions are passed on to them, to object to a result produced solely by automated analysis that is against you, and to claim compensation for damage caused by unlawful processing.

We reply within 30 days. We may ask you to confirm the request from your account email. You can also complain to your data protection authority: in Türkiye, the Personal Data Protection Authority (Kişisel Verileri Koruma Kurumu); in the EU, the authority of your country.

18. Security

Data is encrypted in transit (TLS) and at rest. Every request to our servers is checked against your sign-in token and App Check. Backups are encrypted on your phone before upload. Access to production systems is restricted. No system is perfectly secure, and we will notify you and the authorities of a personal data breach where the law requires it.

19. Age requirement

MitFit is for people aged 16 and over. We do not knowingly collect data from anyone younger. If you believe a child under 16 is using MitFit, contact us and we will delete the account.

20. Changes to this policy

We will update this page when the way we handle data changes, and change the "Last updated" date above. For significant changes we will tell you in the app before they take effect.

21. Contact us