MyFitBook Privacy Policy

Last updated: 19 October 2026

1. Who we are

MyFitBook is operated by Everydayapps OÜ, a company registered in Estonia. We are the data controller for the personal data described in this notice.

• Data Protection contact: hello@everydayappsoy.tech
• Company address: Nooda tee 8, 13516 Tallinn, Haabersti linnaosa, Harju maakond, Estonia

If you have any question about how we handle your data, or want to exercise any of your rights under GDPR, email the Data Protection contact above. We aim to respond within 30 days.

2. What we collect

We collect only what MyFitBook needs to function. Below is every category we touch:

Account

• Email address (for sign-in and account recovery)
• Username (your unique handle)
• Display name (the name shown on your profile and to friends)
• Password hash (legacy email accounts only; managed by Supabase, we never see the plaintext)

Sign in with Apple

New accounts are created with Sign in with Apple. From Apple we receive:

• Your stable Apple user identifier for MyFitBook (a token unique to our app; it does not identify you to other apps)
• Your email address — or, if you choose "Hide My Email", an Apple private relay address that forwards to you. We treat the relay address as your account email.
• Your name, only if you choose to share it, used to pre-fill your display name (you can change it)

We never receive your Apple ID password. You can stop sharing your email with us at any time in your Apple ID settings; account recovery then depends on the relay address staying active.

Body data

• Weight history (each entry you log)
• Body fat percentage and lean body mass — optional, entered by you or imported from Apple Health together with weight when you allow it; stored in your account and never shown to other users.
• Height, sex, age band (optional, used for energy/macros calculations)
• Dietary preferences (diet category, allergies, dislikes)
• Weekly step goals and activity preferences

Fitness data

• Workout sessions (date, type, exercises performed)
• Sets, reps, weight, duration, distance
• Custom exercises you create
• Cardio sessions (segments, intensity, distance)
• Personal records and effort scores derived from your sessions
• Bodyweight leverage settings for bodyweight exercises
• Heart-rate zone profile (your declared max_hr_bpm, used to personalise effort targets in cardio programs)
• Workouts imported from Apple Health (optional, from version 1.1): if you turn on "Import from Apple Health", workouts recorded by Apple Watch or by other apps that write to Apple Health (for example Garmin or Strava) are stored in your account as workout sessions — activity type, start and end time, duration, distance, calories, average and maximum heart rate, the GPS route where one exists, and the name of the app that recorded it. Imported workouts are treated exactly like workouts you log in MyFitBook: they count toward your stats and competitions and are visible to your friends in the feed. You can turn the import off at any time under Settings → Cardio; workouts already imported stay until you delete them.

Nutrition data

• Food logs (each item, portion, macros)
• Custom foods you create
• Barcodes you scan (sent to OpenFoodFacts for lookup; we don't share your identity with them, only the barcode)
• AI meal scans: the photo is sent to Anthropic (Claude) for analysis when you choose to scan. We keep the AI's estimate (the foods and amounts it suggested, as text), on iPhones with a depth sensor the size measurements taken with the photo (numbers only, no depth image), and any description or correction you typed, with your food log, including scans you don't log, so we can measure and improve the scanner's accuracy. Scans you never log, and any description or correction you typed, are deleted after 180 days; a logged meal keeps its scan for as long as the meal exists. We keep the scan photo only when you log the meal (see Meal photos below). Anthropic's own retention policy applies during inference.
• Recipes and dishes you save
• Meal photos (when you capture or pick a photo for a macro log, we upload it to the meal_photos storage bucket so you and your friends can see it in the feed)

Sleep data

• Bedtime, wake time, quality rating for each entry

Social data

• Friends list
• Posts in friends feed and lobby
• Reactions to others' posts
• Lobby memberships and competition participation
• Optional caption text you attach to shared logs
• Direct messages you exchange with friends and coaches (visible only to the two participants; a reported message is hidden pending review)
• Whether you share your route shapes with friends, and since when

Contacts matching (optional)

If you choose "Find friends from contacts", MyFitBook reads the email addresses in your address book on your device, normalises each one and computes a one-way SHA-256 hash of it. Only those hashes are sent to our server, where they are compared with hashes of existing members' emails to show you who is already on MyFitBook. Your address book, contact names, phone numbers and the plaintext email addresses are never uploaded, and the hashes are not stored after the match. You can decline the iOS contacts permission and still add friends by username or invite link.

Coaching, voice notes and drills

• Coaching links between a coach and a client (who is coaching whom, since when)
• Lesson cards a coach writes for a client, including cues and drills
• Coach voice clips: when a coach records a voice note for a lesson card, the audio is transcribed on the device using Apple's speech recognition (no audio is sent to us for transcription). The audio clip itself is uploaded to a private storage bucket (lesson-media) readable only by the coach who recorded it and the client the card is sent to. Voice clips are deleted together with the lesson card or with the account.
• Practice reflections and golf practice/round data you log
• Community drills you publish (name, description, sport). Drills are screened by an automated pre-check before they become visible to other users and can be reported like any other content.

Stories

• Photos you upload as 24-hour stories are stored in the stories storage bucket and are visible to your friends. They are auto-deleted after 24 hours by a scheduled job.

Share cards

• When you render a Strava-style share card for a cardio session and tap "Share", the rendered JPEG is shared via the iOS share sheet (only to apps you choose).
• When you additionally toggle "Also post to feed", the JPEG is uploaded to the share_cards public storage bucket and a feed_posts.kind = 'share_card' row is created. The bucket is public — anyone with the URL can view the image. Within the MyFitBook app, only your friends see the card in their feed.

Location data

• Precise location (GPS): When you start a cardio workout, we record latitude/longitude points to compute distance, pace, splits, elevation gain and a route map. Recording starts on tap-Start and stops on tap-Finish. The points are stored as gps_tracks in your account, and only you see your route on a map. If you turn on Settings → Cardio → Share my routes with friends (off by default), friends who can see one of your workouts, and a coach you have an active coaching link with, can also see the shape of that workout's route, with the start and finish hidden and turned to a random direction, plus its per-kilometre splits and elevation gain. Our server sends them only the outline, scaled to fit a box and turned (and sometimes mirrored) by a random angle that differs for every workout: no coordinates, place names or map. Before that, it removes the start and finish areas of the route, including any part that passes back through them, so those points never leave our database. Someone who knows your area might recognise the streets you ran and work out roughly where you start. The setting covers only workouts you start after turning it on. Turning it off hides your route shapes from everyone else immediately. People you have blocked, or who have blocked you, never see them. A share card you choose to post shows the full outline of the route on the image, including the start and finish.
• Coarse location (city / country): Optional city and country you enter manually for global and local leaderboards. We do not auto-derive these from GPS.

Device data

• Push notification token (only when you opt in to notifications)
• Device timezone (used to schedule motivational pushes at sensible local hours)
• iOS version (used for diagnostics and bug triage)
• Apple Health (HealthKit) reads — only if you grant permission via the iOS prompt: sleep analysis, step count, walking and running distance (used only on your device to estimate calories from your steps), active energy, heart rate, heart-rate variability (HRV), resting heart rate, and — if you turn on "Import from Apple Health" — workouts, workout routes, body mass, body fat percentage and lean body mass (weight and body composition are stored in your account as weight-log entries). Steps, active energy, and heart-rate samples stay on your device. Sleep sessions you log or import are stored in your account, and a derived daily readiness snapshot (readiness tier plus sleep, HRV, and resting-heart-rate deltas versus your own baseline — never raw samples) is stored in your account to power the readiness card. If you use the Apple Watch app, workouts you record there are written to Apple Health on your device.

Health data is used only for the features described above. It is never used for advertising, never sold, and never shared with third parties.

Feedback you send us

• When you use Settings → Send feedback, we store your message, whether it is a bug report or an idea, an optional screenshot you attach (in a private storage area only we can read), and basic diagnostics to help us reproduce problems: the app version and build, your iOS version and your device model (for example "iPhone15,3"). This is linked to your account so we can reply.

Subscription and purchase data

MyFitBook membership is bought through Apple's App Store. To know whether your account is entitled to the app, we store a mirror of your subscription state received from Apple:

• The product you bought (fitbook.sub.monthly or fitbook.sub.yearly)
• Subscription status and expiry date, and the environment (production or sandbox)
• Apple's original transaction identifier for the subscription, which we receive through the App Store Server API and App Store Server Notifications and use to match renewals, cancellations and refunds to your account
• Whether your account is a founding member (created before launch) or has a manual founding exemption

We never receive or store your card number, billing address or Apple ID password — payment is handled entirely by Apple under Apple's own privacy policy.

Free-trial check

So the free trial can't be started again and again with a new account, we keep:

• A pseudonymous code made from your email address, and from your Sign in with Apple ID if you use it, together with the date your free trial started. The code is a salted one-way hash: it doesn't contain your email, but because we hold the salt we can recompute it to recognise the same email or Apple ID if it signs up again. We keep it for a limited period (currently 3 months) after your trial starts, also after you delete your account, and then delete it.
• A flag for your iPhone through Apple's DeviceCheck: when a new account starts its trial, the app creates a one-time device token, our server passes it to Apple, and Apple stores a per-device flag (and the month it was set) for us. The token doesn't identify the device to us, and we don't keep it. Apple keeps this flag; we only act on it when it was set within the same limited period, and because it belongs to the phone, it can also apply to the next person who signs up on that phone.

3. Lawful basis for processing (GDPR Article 6)

• Contract performance (Art. 6(1)(b)): the core logging and tracking that makes MyFitBook function — workouts, food, sleep, weight, custom exercises — and the subscription entitlement records needed to bill and serve your membership.
• Consent (Art. 6(1)(a)): push notifications, leaderboard participation, HealthKit reads, contacts matching, microphone/speech recognition for voice notes, social posting, sharing the shape of your workout routes with friends. You can revoke any of these in app or iOS Settings at any time.
• Legitimate interest (Art. 6(1)(f)): product diagnostics (iOS version logging) and measuring the accuracy of AI meal scans (we compare the AI's estimate with what you logged). These interests are narrow and your rights are not overridden.
• Legitimate interest (Art. 6(1)(f)): preventing the free trial from being used again and again with new accounts — the free-trial check in section 2, kept for a limited period (currently 3 months).

4. Who we share data with

We don't sell your data. We don't share it with any advertising network. We use a small number of processors purely to deliver the service:

• Supabase (Frankfurt, EU region) — database, authentication, edge function hosting. A Data Processing Agreement is in place.
• Apple Push Notification service (APNs) — push token delivery only. Notification payloads contain motivational copy, not nutrition or body data.
• OpenFoodFacts — barcode lookup. We send the barcode only; no personal data.
• Anthropic (Claude) — AI meal-scan analysis when you choose to scan. The photo (and, on iPhones with a depth sensor, the size measurements taken with it) is sent on your action and the analysis is returned; we keep that analysis as text with your food log. Anthropic's own terms apply during inference.
• Apple — Sign in with Apple (identity), the App Store and App Store Server API / Server Notifications (subscription status), DeviceCheck (a per-device flag Apple stores for the free-trial check; no device identifier is shared with us), and Apple's on-device speech recognition framework for voice-note transcription. Apple acts under its own privacy policy for the purchase itself; we receive only the subscription state described above.

5. How long we keep your data

We keep your data for as long as your account is active. AI meal scans you never log, and any description or correction you typed for a scan, are deleted after 180 days; a logged meal keeps its scan as long as the meal exists.

When you delete your account in-app, it is deleted immediately: your profile, workouts, nutrition (including AI meal-scan estimates), body, sleep and social data, your Sign in with Apple link and the subscription mirror record are erased at once, and your uploaded media (avatar, meal photos, stories, share cards, practice clips, coach voice clips and feedback screenshots) is removed from storage shortly after, normally within minutes. There is no recovery window, so make sure you want to delete before you confirm. Your Apple subscription itself is managed by Apple — cancel it in your App Store account settings, as deleting the account does not cancel billing.

Feedback you send from the app is kept for as long as we need it to handle your report, and is always deleted with your account. Backups of our database roll over and are overwritten within 30 days.

The free-trial check (section 2) keeps its pseudonymous code for a limited period (currently 3 months) after your trial starts, even if you delete your account, and then deletes it. Apple keeps the DeviceCheck flag for your phone; we only act on it within that same period.

6. Your rights under GDPR

You have the following rights regarding your personal data:

• Right of access: export everything via Profile → Settings → Export my data. The export is a JSON+ZIP archive. Until the export includes your AI meal-scan estimates and the descriptions you typed, email hello@everydayappsoy.tech and we'll send them to you.
• Right of rectification: edit fields directly in the app.
• Right to erasure: Profile → Settings → Delete account. See Section 5 for timeline.
• Right to data portability: the export above is machine-readable JSON.
• Right to object / restrict processing: email hello@everydayappsoy.tech.
• Right to lodge a complaint: with the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, aki.ee).

7. Security

• All data is transmitted over TLS.
• Data at rest is encrypted by Supabase.
• Passwords are hashed by Supabase auth (industry-standard).
• We periodically review access controls.

No system is perfectly secure. If you believe an issue exists, email hello@everydayappsoy.tech.

8. Children

MyFitBook is not directed at users under 16. If you believe a child has created an account, email hello@everydayappsoy.tech and we'll delete it.

9. Changes to this policy

Small clarifications are shipped quietly. For material changes (new categories of data, new processors, changes that affect your rights), we will re-prompt acceptance in-app on next launch.

10. Contact

• Privacy / data requests: hello@everydayappsoy.tech
• Everydayapps OÜ, Nooda tee 8, 13516 Tallinn, Haabersti linnaosa, Harju maakond, Estonia