Privacy Policy

1. Who we are

Medbay Fit ("Medbay Fit", "we", "us") is a fitness and nutrition coaching app for iOS and Android. This policy explains what personal data the app and its backend service collect, why, who else processes it, how long we keep it and what you can ask us to do about it.

We are the data controller for the data described here. For any privacy question or request, write to [email protected].

2. The short version

• You can use Medbay Fit without an email address. By default your account is a random identifier generated on your device.
• We collect what the app needs to coach you: your onboarding answers, your body measurements, your workouts, your meals and water, your supplements, and anything you type to the AI coach.
• Health and fitness data is never used for advertising or marketing, is never sold, and is never shared with data brokers.
• There is no advertising SDK and no third-party analytics or tracking SDK in the app, and no fonts, scripts or pixels loaded from third parties on this website.
• Photos you send to an AI feature and text you send to the AI coach are processed by OpenAI on our behalf.
• Your community profile is off by default. Nothing you log is visible to anyone until you switch it on and post.
• You can ask us to delete everything: see §17 and the account deletion page.

3. What we collect and why

We collect data in three ways: you enter it, the app generates it as you use it, or you authorise an import from Apple Health, Health Connect or a sign-in provider. We do not buy data about you from anyone.

3.1 Account and identity

• Device-generated account identifier. On first launch the app creates a random UUID and stores it in the device's secure store (iOS Keychain, Android EncryptedSharedPreferences). That identifier is your account. It is not your advertising identifier, not your IDFA/GAID, and it is not shared with third parties for tracking.
• Optional sign-in. Signing in is optional and is offered after onboarding, so you can move your account to a new device. If you use Sign in with Apple or Google, we receive and store the provider's stable user identifier and, if you choose to share it, your name and email address. We verify the identity token's signature with the provider and then attach it to your existing account. We never receive your Apple or Google password.
• Session token. We issue a signed session token (JWT) so the app can talk to our API.
• Preferences. App language, time zone, accent colour theme, notification and reminder settings.
• Entitlement state. Whether you have an active Medbay Fit Pro subscription, and your remaining free AI credits.

3.2 Onboarding answers and profile

The eight onboarding questions and the profile screen produce: goal (lose fat, build muscle, strength, endurance, maintain), gender, birth year, height, starting weight, current weight, target weight, activity level, training experience, training days per week, session length, where you train (gym, home equipment, bodyweight), injuries you report, dietary preference, allergies, focus areas, plus the daily calorie, protein, carbohydrate, fat and water targets we calculate or you override. We also store progress-game values: streak, best streak, XP, weekly workout goal, and your workout reminder time.

Some of this — body measurements, injuries, dietary restrictions — is health data and in the EEA/UK counts as a special category of personal data. We process it on the basis of your explicit consent, which you give by entering it, and you can withdraw it by deleting the entries or your account.

3.3 Body metrics, measurements and records

Date-stamped weight, body-fat percentage, muscle mass, and circumference measurements for neck, shoulders, chest, waist, hips, left and right arm, left and right thigh and calf, plus any note you attach. We also store AI body-analysis results (estimated body fat, muscle mass, symmetry, posture and overall scores, per-muscle-group scores and recommendations).

3.4 Training logs

Workout sessions (program and day, title, status, start and finish time, duration, total volume, total sets and reps, estimated calories, your note and mood), every exercise in the session and every set inside it (weight, repetitions, RPE, warm-up flag, personal-record flag, completion timestamp), your personal records (best weight, reps, estimated 1RM, volume), your favourite exercises, and the training programs generated for or created by you.

3.5 Nutrition and hydration

Food entries (date, meal type, the food chosen or the custom name from an AI photo estimate, servings, and the resulting calories, protein, carbohydrate and fat), water entries, and your diet plans with their meals and recipes. Barcode scanning, where available, uses the camera only to read the code and look up the product — camera frames are not uploaded or stored.

3.6 Supplements and personal protocol logs

Supplements and medications you choose to track: name, type, dose, unit, times of day, weekdays, start and end dates, notes, and whether you took each scheduled dose. The app also lets you keep a private log of longer protocols, with the name you give them, dates, the compound names, doses, frequency and your notes.

This is a diary, not advice. Medbay Fit does not recommend, endorse, prescribe or dose any substance, and no part of the app interprets these entries. We store only what you type, we do not use it to profile you, and it is never shown to other users.

3.7 AI coach conversations

Your chat threads and messages with the AI coach, the assistant's replies, the change proposals it generates for your program or diet, and the status of asynchronous generation jobs. We also store token counts per message for cost accounting. See §6 for how this data reaches OpenAI.

3.8 Technical data

Like any internet service, our servers necessarily process the network information that accompanies a request — IP address, timestamp, the endpoint called, the app platform and version, and error information — in order to run the service, diagnose faults and prevent abuse. We do not use this to build advertising or behavioural profiles, and we do not combine it with third-party data sets.

4. Health and fitness data (important section)

4.1 What the app can read from the platform

If, and only if, you grant permission, Medbay Fit reads these record types from Apple Health (HealthKit) on iOS and Health Connect on Android:

• body weight, body-fat percentage, lean body mass, height
• workouts / exercise sessions (type, start and end time, duration, energy burned)
• nutrition (energy and macronutrients)
• hydration
• steps
• active energy burned

These are imported so your progress lives in one place — for example your weight history fills in automatically instead of you re-typing it, and a run you recorded elsewhere counts toward your week.

4.2 What the app writes back to the platform

With your permission, Medbay Fit writes back only what you created in the app: workouts, body weight, nutrition and hydration. We filter out anything that originally came from the platform, so a record is never duplicated or written back on top of itself.

4.3 Permissions are yours, and revocable

• iOS: Settings → Privacy & Security → Health → Medbay Fit, or the Health app → Sharing → Apps. You can allow or revoke each data type individually.
• Android: Health Connect (in Settings, or as a separate app on Android 9–13) → App permissions → Medbay Fit.
• In the app: profile picture (top right) → Settings → Apple Health / Health Connect → Disconnect. Disconnecting stops syncing and deletes the records that were imported from the platform from our servers (on iPhone you are asked, and can choose to keep them). Records you entered yourself are kept, because they are yours.
• The Health permission step during onboarding is skippable. If you decline, the app works exactly as before — you just type your measurements yourself.

Health data read from the platform is stored on our servers so the same history is available on your other devices and so the AI can use it to build your plans. It is transmitted over an encrypted connection and it is not sent to any third party other than the processors listed in §10.

5. Photos and the camera

Photos appear in Medbay Fit in three places, all optional:

• Progress photos attached to a body measurement.
• Body-analysis photos you send to the AI to get muscle-group, symmetry and posture feedback.
• Food photos you send to the AI to estimate a portion and its macros.
• Community photos, if you choose to post one.

Photos you submit are uploaded to and stored on our servers under randomly generated file names (the storage layout is never exposed) and are served only to your authenticated account — except for a photo you deliberately attach to a community post, which becomes visible to the community. Photos sent to an AI feature are transmitted to OpenAI for analysis as described in §6. Camera and photo-library access are requested only at the moment you use one of these features, and you can deny or revoke them in your device settings.

You can delete a progress photo by deleting the measurement it belongs to, a post photo by deleting the post, and all of it by deleting your account.

6. AI features and OpenAI

The AI features are: training program generation, diet plan generation, the coach chat, food-photo macro estimation, body-photo analysis, and the weekly report. They work by sending a context package to OpenAI, which acts as our processor and returns the result. Depending on the feature, that package can include:

• your profile and goal data (age band, gender, height, weight, target weight, experience, equipment, schedule, injuries, dietary preference, allergies, calorie and macro targets);
• a summary of your recent training (last sessions, volume, personal records) and today's nutrition totals;
• the message you typed into the coach;
• the photo you submitted, for the two vision features;
• a filtered list of permitted exercise identifiers from our catalogue, so the model can only pick real exercises.

We do not send your name, email address, account identifier or any payment information to OpenAI. We use OpenAI's API under terms that do not permit your inputs or outputs to be used to train their models. If we ever have no OpenAI key configured, the AI endpoints simply return "unavailable" and the rest of the app keeps working.

7. Community content

The community surface is opt-in and off by default. Your profile flag starts as private, and while it is private nothing you log is visible to anyone else.

If you turn it on, the following becomes visible to other users:

• your display name (if you leave it blank we generate an abbreviated one, e.g. "Cem B." — we never publish a full surname), your avatar and your bio;
• posts you create: text, an optional photo, and — for a shared workout — only a summary: title, program name, duration, total volume, total sets, and up to three highlighted exercises;
• your likes, comments, follows and challenge participation and progress.

What the community can never see: your set-by-set breakdown, your weight history, your body measurements, your body-fat or photos you did not post, your nutrition and water logs, your supplement or protocol entries, your AI conversations, and your calorie and macro targets. These are not returned by the community endpoints at all.

We also process moderation data: blocks (which cut visibility in both directions) and reports (the reason you pick and the detail you write). A post that is reported by enough distinct users is hidden from the feed automatically. We keep moderation records after the underlying content is gone, because otherwise blocks and repeat-offender handling would not work.

8. Subscriptions and purchases

Medbay Fit Pro is sold as an auto-renewing subscription through the App Store and Google Play and is managed with RevenueCat. Your device-generated account identifier is used as the RevenueCat app user ID so that a purchase can be matched to your account.

From the store, via RevenueCat, we receive and store: transaction and event identifiers, the product purchased, purchase date, renewal count, the price and currency, the store country, and whether the subscription is active. We never receive or store your card number, bank details or billing address — the payment is handled entirely by Apple or Google.

9. Push notifications

If you allow notifications, the app registers with Firebase Cloud Messaging (Google) and we store the resulting device push token, plus the reminder times you configured. We use notifications for workout and supplement reminders, weekly reports and — if you enable the community — community activity. We do not send marketing push notifications. Revoking notification permission in your device settings stops all of them.

10. Service providers

We share data only with the processors below, only to the extent needed for the stated purpose, and under contracts that require them to protect it. We do not sell personal data and we do not share it for cross-context behavioural advertising.

Provider	What it receives	Why
OpenAI	The AI context package described in §6, including submitted photos. No name, email, account ID or payment data.	Generating programs, diet plans, coach replies, photo estimates, weekly reports
RevenueCat	Account identifier, store transaction and subscription events	Validating and managing subscriptions
Apple · Google (stores)	Purchase and subscription data; the identity token if you use Sign in with Apple or Google	Payments, sign-in, app distribution
Google (Firebase Cloud Messaging)	Device push token and the notification payload	Delivering notifications
Our hosting provider	Everything stored by the service (database, uploaded files, server logs), as the infrastructure it runs on	Running the API, database and file storage

We may also disclose data if we are legally required to (a valid court order or lawful request), to establish or defend legal claims, or to protect the safety of our users. If the service is ever transferred to another owner, your data may transfer with it and you will be told before anything about this policy changes for you.

11. What we never do

• We do not sell your personal data, and we do not "share" it in the sense used by US state privacy laws (cross-context behavioural advertising).
• We do not use health or fitness data for advertising or marketing, ever.
• We do not share health data with data brokers.
• We do not embed advertising SDKs, third-party analytics SDKs or session-replay tools in the app.
• We do not collect your precise or coarse location, your contacts, your calendar, your microphone input, your call or SMS data, your browsing history, or the list of other apps on your device.
• We do not use cookies, fonts, scripts, pixels or any third-party request on this website. Nothing here tracks you.

12. Legal bases

If you are in the EEA or the UK, the GDPR applies; if you are in Türkiye, the KVKK applies. Our bases are:

• Performance of a contract (Art. 6(1)(b)) — creating your account, storing your plans and logs, delivering the features you asked for, managing your subscription.
• Explicit consent (Art. 6(1)(a) and Art. 9(2)(a)) — health data, including your measurements, injuries, dietary restrictions, supplement entries, photos, and anything imported from Apple Health or Health Connect; sending content to the AI features; push notifications; publishing a community profile. You can withdraw any of these at any time, without affecting what was lawful before.
• Legitimate interests (Art. 6(1)(f)) — keeping the service secure, preventing abuse and fraud, moderating community content, and debugging.
• Legal obligation (Art. 6(1)(c)) — keeping the transaction records that tax and accounting law require.

13. How long we keep data

Data	Kept
Account, profile, plans, training, nutrition, measurements, supplements, AI conversations	For as long as your account exists. You can delete individual entries at any time.
Records imported from Apple Health / Health Connect	Until you disconnect the platform (which deletes them) or delete your account.
Photos (progress, body analysis, food, community)	Until you delete the entry or post they belong to, or your account.
Everything above, after a deletion request	Erased from live systems within 30 days; purged from encrypted backups within 90 days.
Transaction and subscription records	As long as tax, accounting and audit law requires (typically up to 10 years), reduced to the minimum needed for that purpose.
Moderation records (blocks, reports)	Retained after account deletion in a form that no longer identifies you, so that safety decisions stay enforceable.
Server and security logs	Short rolling window, typically no longer than 90 days.

14. International transfers

Our servers and some of our processors — OpenAI, RevenueCat, Google (Firebase), Apple — operate outside your country and, for users in the EEA/UK/Türkiye, may process data in the United States or other jurisdictions. Where that happens we rely on the European Commission's Standard Contractual Clauses or an equivalent safeguard, together with the technical measures in §15.

15. Security

• All traffic between the app and our API is encrypted in transit (HTTPS/TLS).
• Your account identifier and session token are stored in the platform's secure store — iOS Keychain, Android EncryptedSharedPreferences — not in plain preferences.
• Uploaded files are stored under random identifiers and are served only through an authenticated endpoint; directory listing is not possible.
• Every API request is checked against the authenticated account, so one user cannot read another user's records.
• Access to production systems is limited to the people who need it.

No system is perfectly secure. If a breach ever affects your personal data, we will notify you and the relevant supervisory authority as required by law.

16. Your rights

Depending on where you live, you can ask us to:

• Access the personal data we hold about you, and get a copy of it.
• Correct anything inaccurate.
• Delete your data ("right to be forgotten").
• Restrict or object to processing based on legitimate interests.
• Port your data to another service in a machine-readable format.
• Withdraw consent — for health sync, AI features, notifications or the community profile — at any time.

Most of these you can do yourself in the app by editing or deleting entries, disconnecting Health, or turning the community profile off. For anything else, email [email protected] from the address linked to your account, or include your in-app account identifier if you never signed in. We answer within 30 days. We do not charge for this, and we will not treat you differently for asking.

We do not use your data for automated decision-making that has a legal or similarly significant effect on you. If you are unhappy with our answer you can complain to your local data protection authority — in Türkiye the KVKK authority, in the EEA your national DPA, in the UK the ICO.

17. Deleting your data

You can have your account and the data attached to it erased. The full instructions, what is deleted, what we must keep and for how long, are on a page you can reach without logging in: medbay.fit/delete-account. The short version: email [email protected] with the subject Delete my account.

18. Children

Medbay Fit is not directed at children and we do not knowingly collect data from them. The app carries a 4+ / "Everyone" store rating because it contains no objectionable content — that rating describes the content, not the intended audience. Strength training, calorie targets and body-composition tracking are not appropriate features for children.

You must be at least 16 years old to use Medbay Fit (or older, if your country sets a higher age for consenting to this kind of processing; where the applicable minimum is lower, that age applies). If you are under 18 you should use the app only with the involvement of a parent or guardian and after speaking to a physician. If you believe a child has given us personal data, email [email protected] and we will delete the account.

19. Changes to this policy

If we change this policy we will update the "Last updated" date at the top and, for changes that materially affect you, tell you in the app before they take effect. If a change requires new consent — a new data category or a new purpose — we will ask for it rather than assume it. Previous versions are available on request.

20. Contact

Privacy questions, data requests and complaints: [email protected]. We aim to reply within 2 business days and to resolve formal data requests within 30 days.