Privacy Policy

Last updated: July 5, 2026

This Privacy Policy describes how Forgd Fitness ("Forgd", "we", "us", or "the app") collects, uses, stores, and shares your personal information when you use our mobile application available through the Apple App Store.

We built Forgd around a privacy-first principle: what you log in the app (workouts, nutrition entries, body measurements, progress photos) lives on your device and syncs to your own private account on a backend we operate, so it's available whenever you sign in on another device. That data is encrypted in transit and at rest, restricted by access controls, and we never sell it, show ads against it, or use it to train models.

The key things to know:

Your account & synced data. When you create or sign into a Forgd account, your account record and the fitness, nutrition, body, and photo data you log are stored on a backend we operate (the forgd-backend, hosted on Cloudflare Workers with managed Postgres and object storage on Supabase, in the United States) so you can sign back in and access your data across devices.
Trainer sharing (opt-in). A trainer can only see your data if you connect with a Forgd-listed trainer (by entering their invite code, or by requesting a trainer from the in-app directory who then accepts your request) and explicitly grant per-scope access (workouts, nutrition, photos, body data, goals). If you never connect a trainer, your data is never shared with any trainer.
Community & friends (opt-in). Forgd includes optional social features. If you send or accept a friend request, an in-app activity feed shares your fitness milestones (completed workouts, personal records, streaks) and your display name with the friends you connect with. You can also create or join challenges and appear on their leaderboards, and invite friends with a referral code. None of this sharing happens unless you choose to add a friend or join a challenge. See Section 1.12.

Sections 1.7-1.8 and Section 3 describe where your data lives and how it's protected.

The short version: Forgd does not sell or rent your data. We do not show advertising. We do not use your data to train machine-learning models. We share your information only with the service providers listed in Section 4 (as needed to operate the app), with a trainer you choose to connect (Section 1.8), and, if you opt into our community features, with other Forgd users you add as friends or share a challenge with (Section 1.12).

1. Information We Collect

1.1 Information you provide directly

When you sign in with Apple, we receive your Apple-issued user identifier and, at your option, your name and email address. If you choose to use Apple's Hide My Email feature, we receive a private relay email instead of your real address.

When you use Forgd, you may enter or log:

Your name and display preferences
Date of birth, sex, height, weight, and fitness goals
Body measurements (e.g., waist, hips, arms)
Workout entries, exercise logs, and training programs
Nutrition entries, meal plans, and dietary preferences
Hydration and step goals
Gym locations you've saved
Progress photos you've taken or uploaded
Notes and custom content you've written

1.2 Health data from Apple HealthKit

If you grant permission, Forgd reads a broad set of fitness, health, and recovery data through Apple's HealthKit framework, including: activity and energy data (steps, active and basal energy, exercise time, stand time, walking and running distance, flights climbed); workouts; cardio biomechanics (VO₂ max, walking and running speed, running stride length and power); heart-rate and cardiovascular data (heart rate, resting heart rate, heart rate variability, respiratory rate, oxygen saturation, body temperature, blood pressure); body composition (weight, body-fat percentage, body mass index, height, lean body mass, waist circumference); and sleep and mindfulness sessions. With your permission Forgd also writes back to HealthKit the workouts you log in the app, water intake, and updates to body composition. HealthKit data is stored by Apple, never by us, and is controlled through your device's Settings → Health → Data Access & Devices → Forgd at any time.

Per Apple's HealthKit policies, we do not sell, disclose, or use HealthKit data for advertising, data brokering, or any purpose unrelated to providing fitness and health features inside the app.

1.3 Photos and camera

If you grant permission, Forgd uses the device camera for two purposes: progress photos (captured and stored on your device and synced to your private Forgd account in a private Supabase Storage bucket on the backend we operate, fetched via short-lived signed URLs) and barcode scanning in the Nutrition tab to look up packaged foods (the scan happens on-device; only the resulting product code is queried against the public Open Food Facts database). We do not scan your photos for faces or sell them. Progress photos are shared only with our backend storage provider (Supabase, acting as our processor) and, only if you opt in, a trainer you connect. Separately, if you actively use an AI feature, tapping "Get AI feedback" on a progress photo, or the AI meal-photo / workout-photo scanning, that specific image is sent to our AI provider (Anthropic) to generate the feedback and is not used to train any model (see Section 1.11). A connected trainer can view your progress photos only if you turn on the Photo sharing scope (see Section 1.8). Form-check videos are a separate, opt-in upload covered in Section 1.8.

1.4 Location data

Forgd uses location in two distinct ways:

Nearby search (not stored or transmitted to us). If you use the Gyms feature (Workouts → Saved Gyms) or the Restaurants feature (Nutrition → Restaurants tile) and grant location permission, Forgd uses your current location to query Apple's MapKit local-search service for nearby gyms or restaurants. For this feature the location is used only for the lookup itself: we do not store it, do not transmit it to any server we control, and do not track your location in the background.

Outdoor cardio GPS route (recorded and uploaded). If you start an outdoor cardio workout (such as a run or ride) and grant location permission, Forgd records your precise GPS route (a series of latitude/longitude points) for the duration of that workout so it can show your distance, pace, and map. When you save the workout, that route is uploaded with the cardio log to the backend we operate and stored linked to your account, so it syncs across your devices and, if you opt in, can be shown to a trainer you connect. This matches the "Precise Location" data type declared as collected and linked in our App Store privacy label and app privacy manifest. Location is captured only while a cardio workout is active (never in the background), and you can decline or revoke location access at any time in Settings.

1.5 Device and usage information

Forgd does not embed third-party analytics or advertising SDKs. The app keeps a local crash log on device and offers it to you for optional sharing. It does not leave your device unless you explicitly share it.

Motion sensors: if you grant motion permission, Forgd reads cadence, pace, and active-calorie data during cardio workouts directly from CoreMotion. This data is processed on-device only. It is not sent to any server we operate.

The "How To" tutorial sheet on each exercise loads YouTube content inside an in-app private web view (using YouTube's youtube-nocookie.com embed where applicable). When that sheet is open, your device communicates directly with YouTube to render the search results or video, and YouTube receives the standard request information any browser would send (IP address, user agent, the search query). Forgd itself does not collect or store any data about which tutorials you watched.

1.6 Subscription information

When you purchase a subscription, Apple processes the transaction and provides the app with a cryptographically-signed receipt indicating your entitlement status. We never see your payment details, card numbers, or billing address. Subscription status is verified on your device.

1.7 Data held on the backend

So you can sign in across devices and pick up your data anywhere, the data you log in the app (workouts, nutrition entries, body measurements, and progress photos) is stored in your private account on our backend (see Section 3 for the infrastructure and Section 8 for safeguards). In addition to that logged data, the backend keeps an account record:

Your account email address.
If you sign up with email and password: a salted PBKDF2 password hash. Your raw password is never transmitted to or stored by us in plaintext.
If you sign in with Apple or Google: the provider's user identifier, plus the email those providers attest you control (which may be Apple's private relay address if you use Hide My Email).
Refresh tokens for active sessions, scoped to a single device, hashed at rest. We rotate them on each use and revoke them when you sign out, reset your password, or delete your account. Once a refresh token is revoked, that session can't get a new short-lived access token.
Short-lived email-verification and password-reset tokens, hashed at rest, that expire automatically (password-reset links after about one hour; email-verification links after 24 hours).
Your account role (regular user, or trainer if approved) and a token version counter. The counter increments after security-relevant changes (for example, when an account is approved as a trainer); your next session refresh re-reads the counter and stamps the current value into a new access token. Existing access tokens, which are short-lived (15 minutes), age out naturally on top of this.

Your account record and all of your synced data are wiped when you delete your account (see Section 5).

1.8 Sharing your data with a trainer (only if you connect one)

Forgd offers a Trainer Hub: certified coaches we've approved can be connected to your account, either by entering an invite code they share with you or by requesting a coach from the in-app trainer directory who then accepts your request. Connecting a trainer is entirely optional, never automatic, and gated behind a deliberate confirmation flow.

Your data is already stored in your private Forgd account (Section 1.7). When you connect a trainer, you choose per-scope what they can see, independently for workouts, nutrition, body measurements, goals, and progress photos. Each scope you toggle on grants that connected trainer read access to the corresponding data from their web dashboard; turning a scope off removes their access to it. Access updates in near-real-time as you log new entries.

What a connected trainer can see is bounded by your toggles:

Workouts: exercise names, sets, reps, weights, durations, and timestamps for sessions you've completed.
Nutrition: daily food entries, calories, macros, and meal labels.
Body data: weight, body measurements, and body-fat estimates you've entered.
Goals: if you turn on the goals scope (off by default), the fitness goals you set (each goal's title, target, current progress, and whether it's complete) are shared so your trainer can track them alongside your training.
Progress photos: only if you flip on the photo scope, which is off by default. Photo files are stored in a private Supabase Storage bucket; the connected trainer's authenticated session fetches them through our backend via short-lived (15-minute) signed URLs.
Direct messages: if you flip the messaging scope on (off by default), text messages between you and your trainer are stored on our backend so the conversation can be read from either side. Message bodies are capped at 4,000 characters each. They remain on our backend keyed to your account after disconnect (so each side keeps their own history); they are removed when you delete your account.
Weekly check-ins: if you submit the optional weekly check-in survey from the Trainer screen, your four 1-5 ratings (energy, sleep, soreness, motivation) and a free-text note are stored on our backend so your trainer can see trends week-over-week.
Live workout heart rate: if you start a workout while connected to a trainer, the app may stream your current heart rate (sampled approximately every 15 seconds), the exercise you're on, and the elapsed time to our backend so your trainer can watch a live card on their dashboard. The most recent ~60 samples are kept while the session is active; per-session aggregate min / max / average are retained as part of the workout summary. Live HR streaming only happens during an active session that you started; nothing streams when the app is in the background or when no workout is running.
Form-check videos: the Trainer screen lets you record or pick a short video and upload it to your trainer for technique review. If you do, the video file is stored in a private Supabase Storage bucket (separate from progress photos) and your trainer fetches it through our backend via short-lived (15-minute) signed URLs. Trainers can add timestamped drawings or comments which are stored alongside the video. Form-check videos and their annotations are hard-deleted from our backend on disconnect (and on account deletion). Unlike workouts/nutrition/body/photos which remain keyed to your account after disconnect, video files are wiped because the storage cost and sensitivity profile are higher.

You can disconnect a trainer at any time from the Connect a Trainer screen. Disconnect requires you to type the trainer's name to confirm. Disconnection ends the relationship immediately, stops further mirror updates, and removes that trainer's access. Your workout, nutrition, body, and photo data stays in your own account (it always lives there); any trainer-specific data you created (messages, check-ins, live-session aggregates) also remains keyed to your account but is no longer visible to that ex-trainer or to any other trainer unless you connect a new one and grant the matching scope. Form-check videos are an exception: they are hard-deleted on disconnect. All mirror data is fully removed when you delete your account (Section 5).

If you never connect a trainer, none of your data is ever shared with a trainer. It stays private to your account. (Your workouts, nutrition, body data, and photos still sync to your own Forgd account for backup and cross-device access, per Sections 1.7 and 3. Messages, weekly check-ins, live heart-rate streaming, and form-check videos are trainer-only features that don't exist unless you connect a trainer and enable the relevant scope.)

Forgd's admin team manually reviews trainer applications. Approval and rejection decisions are recorded in an internal audit log (admin email, decision, timestamp) so we can answer compliance and account-recovery questions later.

1.9 Heart rate from Apple Health

Forgd reads heart-rate samples through Apple HealthKit on your iPhone. If you wear an Apple Watch (or any other device that writes heart rate to Apple Health), those samples become available to Forgd during a workout the same way the rest of your HealthKit data is (see Section 1.2), and they drive the optional live-heart-rate card described in Section 1.8. HealthKit data is stored by Apple, never by us, and is governed by Apple's privacy controls; you can revoke Forgd's access at any time in Settings → Health → Data Access & Devices → Forgd. Heart rate is read only with your permission and used only for the in-app features described here.

1.10 Push notifications

If you grant notification permission, our backend sends push notifications to your device through Apple's Push Notification service (APNs) for events such as: a connected trainer assigning a workout or program, an incoming chat message, a meal-plan reschedule, a form-check annotation, the weekly check-in reminder, rest-timer / workout-reminder alerts, and, if you use the community features, social events such as a friend request, a friend accepting your request, a reaction to your activity, or a challenge invitation. To deliver these we store an APNs device token for each device you sign in on, scoped to your account, in our backend. Tokens are revoked when you sign out, are re-bound to a different account if a new user signs in on the same device, and are deleted when you delete your account. We do not use push tokens for analytics or any purpose other than delivering the notifications described above. You can revoke notification permission at any time in iOS Settings → Notifications → Forgd; the device token row stays until your next sign-in/out cycle but no further pushes are sent.

1.11 AI features

Forgd offers optional AI features: the AI coach chat, AI meal-photo and workout-photo scanning, and AI feedback on a progress photo. When you use one of these, the relevant input, the text you send the coach, or the specific photo you choose to scan or get feedback on, is sent to our AI provider, Anthropic (a U.S.-based processor), which processes it to generate the response and returns it to us. Anthropic processes your input only to fulfill that request; per its commercial API terms it does not use your inputs to train its models, and Forgd never sells this data. These features are opt-in per use: nothing is sent to the AI unless you actively start a scan, request feedback, or message the coach. AI responses are general guidance only, not medical, dietary, or professional advice, and you can report any AI response you find inappropriate directly from within the app.

1.12 Community and social features (opt-in)

Forgd includes optional social features. They are off until you act: nothing about you is shown to another user unless you send or accept a friend request, join or create a challenge, or share a referral code. When you use them, the following data is stored on our backend and shared with the specific other users described below.

Friends. You can search for and send friend requests to other Forgd users, and accept or decline requests sent to you. We store the friend relationship (the two accounts and its status: pending, accepted, or blocked) on our backend. Accepting a request makes the two accounts mutual friends; either of you can remove or block the other at any time.
Activity feed. Once you have accepted friends, the app posts your fitness milestones (for example a completed workout, a personal record, or a streak) as activity events, and shares them, along with your display name, on the feeds of your accepted friends. Your friends can react to your events, and you see theirs the same way. If you have no friends, these events are not visible to anyone else.
Challenges and leaderboards. You can create a challenge (with a name and optional description you write) or join an existing one, and invite friends to it. Participants and their progress on a challenge metric are visible to the other participants on the challenge leaderboard, along with your display name. Public challenges may be discoverable by other users.
Profile. Other users you connect or share a challenge with can see your public profile: your display name, when you joined, and summary stats such as your number of challenges and mutual friends.
Referral codes. You can share a personal referral code with other people; when someone uses it, we record the referral on both accounts.

Moderation. Text you author that other users can see (your display name, challenge names and descriptions, and activity titles) is screened by a server-side filter that rejects objectionable content. You can report content or another user, and block a user, from within the app; reports are stored for our review, and blocking hides that user from you and prevents further interaction. These controls exist to keep the community safe under the App Store's user-generated-content requirements.

All of this community data (your friend relationships, activity events and reactions, challenge participation and invitations, and referral records) is removed when you delete your account, as described in Section 5. Challenges you created remain for the other participants, but your creator link is anonymized.

2. How We Use Information

We use the information above solely to operate the app's features for you:

Personalize workout and nutrition recommendations
Save and sync your training programs, logs, photos, and goals across your Apple devices
Show your progress trends, streaks, badges, and achievements
Integrate with Apple Health to reflect your real activity
Enable in-app purchases and subscription features
Respond to your support requests

We do not use your data for advertising, profiling across services, training machine-learning models, data brokering, or any purpose unrelated to the fitness features you've enabled.

3. Where Your Data Is Stored

On your device: app data is written to your device's local application sandbox. Identity tokens are stored in the iOS Keychain. This data is protected by iOS's standard file-system encryption when your device is locked.

In your Forgd account (our backend): the data you log (workouts, nutrition, body measurements, and progress photos) syncs to a backend we operate so it's available across your devices. It is sent over an encrypted connection (TLS) and stored encrypted at rest. Because we host this backend, this sync is not end-to-end encrypted; access is restricted by the safeguards in Section 8, and we never sell your data or use it for advertising. The technical specifics follow.

On our backend (forgd-backend): your account and the data you log live on infrastructure we operate: Cloudflare Workers handle requests, and a managed Postgres database on Supabase (in the United States) stores the rows, with progress-photo image files in a private Supabase Storage bucket accessed only via short-lived (15-minute) signed URLs. Database access is restricted by row-level security defaults that deny non-service requests; passwords are stored only as PBKDF2 hashes; refresh tokens are rotated and revocable. If you've connected a trainer with sharing scopes enabled (Section 1.8), that trainer can read the scoped workout/nutrition/body/photo data from a web dashboard.

With Apple: sign in, subscription, and HealthKit flow through Apple's services per their privacy policies.

On Apple iCloud (CloudKit): the optional Groups & Leaderboards feature stores group records, the group name, its members' display names, and each member's leaderboard entry for the group's metric, in Apple's CloudKit public database so members of the same group can see the shared leaderboard. These records are written only when you create or join a group, are hosted by Apple under Apple's privacy terms rather than on our own backend, and are deleted when you delete your account (Section 5). If you never create or join a group, nothing is written to CloudKit.

4. How We Share Information

We do not sell, rent, license, or otherwise disclose your personal information to any third party for marketing or commercial purposes.

We share information with the following service providers solely to operate Forgd. Each acts as a processor on our behalf and is contractually limited in what they may do with the data:

Apple, as necessary to provide Sign in with Apple, HealthKit, In-App Purchase, and, for the optional Groups & Leaderboards feature, CloudKit storage of your group records (Section 3). Apple's handling is governed by Apple's Privacy Policy at apple.com/legal/privacy.
Cloudflare, our hosting provider for the forgd-backend Worker, the forgd.fit marketing website, and the trainer dashboard at trainers.forgd.fit. Cloudflare also handles DNS, TLS termination, and edge caching for these properties.
Supabase, the managed Postgres host for the backend database described in Section 3, and the private object-storage host for your synced progress photos and any form-check videos.
Anthropic, our AI provider (see Section 1.11). Only when you actively use an AI feature, we send the relevant input, your coach-chat message, or the specific photo you choose to scan or get feedback on, to Anthropic's API to generate the response. Anthropic processes it only to fulfill that request and, under its commercial API terms, does not use it to train its models.
Google, in two narrow situations: (a) if you choose to sign in with Google, we receive the Google account identifier and verified email Google attests to; (b) if you tap the "How To" tutorial on an exercise, the in-app private web view loads YouTube content from youtube-nocookie.com or m.youtube.com directly. Google's handling of those video-loading requests is governed by Google's Privacy Policy and YouTube's terms; Forgd does not pass Google any other information about you.
Resend, when we send you transactional email: verification messages, password-reset links, and trainer-decision notifications. Resend processes the message and your email address; it does not receive any of your fitness or nutrition data.
USDA FoodData Central and Open Food Facts, the public food databases we query when you search for a food or scan a barcode in the Nutrition tab. Only the search text you type or the scanned product code is sent, so we can return nutrition facts; no account, identity, or health data is included in the lookup.
Stripe, only if you are an approved trainer who sets up payouts. Stripe processes the trainer's identity and bank/payout details to pay out subscription revenue (Stripe Connect). A regular (non-trainer) user's data is never sent to Stripe; we never see or store your card details for your own subscription, which Apple handles.
Sentry, our error-monitoring provider, which may receive backend error and diagnostic information (error messages, stack traces, and request metadata such as the endpoint and a user identifier) when something fails, so we can diagnose and fix it. It is not used for advertising or analytics profiling.
Connected trainers you have explicitly chosen to share with, via the per-scope toggles described in Section 1.8.
Other Forgd users you choose to interact with through the optional community features (Section 1.12): friends you connect with see your activity feed, display name, and profile; challenge participants see your challenge progress and display name on the leaderboard. This is user-directed sharing that only happens when you add a friend or join a challenge, and it stops for future activity when you remove the friend, leave the challenge, or delete your account.
Law enforcement or regulators, if required by a valid legal request. We retain only the minimum information described in Section 1.7 and Section 1.8; we cannot disclose data we do not hold.

5. Your Rights and Choices

You control your data at all times:

Access and export: from the Profile → Data → Export All Data screen, you can download a ZIP archive containing the JSON of your locally-stored data plus your saved progress photos.
Delete account and all data: from Profile → Account → Delete Account, you can permanently delete your local data, app session, your backend account record, all your synced data (workouts, nutrition, body data, and progress photos in Supabase Storage), your community data (friend relationships, activity feed events and reactions, challenge participation and invitations, and referral records), and any trainer-shared access on our backend. This is immediate and irreversible.
Disconnect a connected trainer: Profile → Connected Trainer → End Relationship. Disconnect requires you to type the trainer's name to confirm; once confirmed, the trainer loses access immediately and the mirror is wiped as part of relationship cleanup.
Adjust trainer sharing scopes: Profile → Connected Trainer lets you toggle each scope (workouts, nutrition, body data, photos) independently. Turning a scope off stops further mirror updates for that scope.
Revoke Apple sign-in: from iOS Settings → your Apple ID → Sign in with Apple → Forgd → Stop Using Apple ID, you can disconnect your Apple ID from the app at any time.
Revoke HealthKit access: Settings → Health → Data Access & Devices → Forgd.
Revoke location and photo access: Settings → Privacy & Security.
Opt out of notifications: Settings → Notifications → Forgd or from the in-app Notifications settings.
Cancel subscriptions: Settings → your Apple ID → Subscriptions, or via Profile → Subscription → Manage Subscription inside the app.

Lawful bases for processing (EEA / UK). We process your account record (Section 1.7) under contract necessity (Art. 6(1)(b) GDPR), providing the app you signed up for. Trainer-mirror data (Section 1.8) is processed only under your explicit consent (Art. 6(1)(a)), which you give per-scope and may withdraw at any time. HealthKit data (Section 1.2) is processed under your explicit consent for special-category health data (Art. 9(2)(a)).

Data-subject rights (EEA / UK / California). You have the rights to: (i) access the personal information we hold about you, (ii) rectify inaccurate data, (iii) erasure ("right to be forgotten"), handled by Profile → Account → Delete Account, (iv) restrict processing, (v) object to processing, (vi) data portability, handled by Profile → Data → Export All Data, and (vii) not be subject to a decision based solely on automated processing. Forgd makes no such decisions about you. EEA / UK residents may also lodge a complaint with their supervisory authority. To exercise any right we cannot provide directly in-app, email the contact address below.

California residents: Your CCPA Rights. We do not sell or share your personal information as those terms are defined under the California Consumer Privacy Act (Cal. Civ. Code § 1798.140). We have not done so in the preceding 12 months and do not anticipate doing so. There is therefore no opt-out mechanism to provide; if this changes we will update this notice and provide one. You retain the rights described above to access, correct, and delete your information.

EU representative. Forgd does not target EU residents and does not regularly offer goods or services to data subjects in the European Union. We have not designated a representative under GDPR Article 27. If this changes we will update this notice.

6. Children

Forgd is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us information, please contact us and we will delete it.

7. Data Retention

Your local data and the synced data in your Forgd account are retained until you delete them. You control retention by deleting entries or your account.

Backend account data (Section 1.7) is retained for as long as your account is active. Email-verification and password-reset tokens are short-lived (hours) and self-expiring. Refresh tokens are revoked when you sign out, change your password, or delete your account. When you delete your account, the account row is anonymized within minutes and all of your synced data (workouts, nutrition entries, body data, progress photos and form-check videos in Supabase Storage, messages, weekly check-ins, and live-session aggregates) is removed. An anonymized account stub (containing no personal or fitness data) is preserved for up to 30 days for compliance and audit purposes before being purged.

Trainer-mirror data (Section 1.8) is retained while your account exists. When you disconnect a trainer, the relationship is marked as ended and that trainer immediately loses access; the underlying mirror rows remain associated with your account so they can re-populate seamlessly if you re-connect or grant access to a different trainer. The mirror rows are deleted in full only when you delete your account. Trainer admin-decision audit rows persist (with the user reference set to null on account deletion) so we can answer compliance and account-recovery questions later.

8. Security

On your device we rely on Apple's platform security: device-level file encryption, Keychain-protected credentials, and App Transport Security for all network calls.

For backend data we operate, traffic uses TLS 1.3 in transit; the database enforces row-level security defaults that deny non-service requests; passwords are stored only as PBKDF2 hashes generated via Web Crypto; refresh tokens are rotated on use and revocable; the trainer admin panel sits behind Cloudflare Access (single-administrator policy) and every approve/reject decision is recorded in an immutable audit log. Trainer-shared data is gated by the per-scope consent toggles you control.

No system is perfectly secure; report suspected vulnerabilities to the contact email below. If we become aware of a personal-data breach affecting your information, we will notify affected users without undue delay and within 72 hours where required by law, and provide a clear description of what happened, what data was affected, and what mitigations we recommend.

9. International Transfers

Cloudflare and Supabase operate global networks. Backend requests are accepted at Cloudflare's nearest point-of-presence and proxied to Supabase's primary region in the United States, where account data and trainer-mirror data are stored at rest. Apple's services follow Apple's own data-handling policies. If you are based in the European Economic Area or the United Kingdom, you are sending data internationally to the United States when you sign in or use trainer features; you can stop at any time by signing out, deleting your account, and / or never connecting a trainer.

10. Changes to This Policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top reflects the latest change. Material changes will be surfaced in the app before they take effect.

11. Contact

Questions, requests, or concerns: forgd.fit@gmail.com

Data controller. Forgd Fitness is operated by Bryce Harr from the United States.
Email: forgd.fit@gmail.com

If you prefer to send postal correspondence (for example, a formal data-subject access or erasure request), email the address above and we will provide a mailing address by reply within five business days.

12. Website Cookies and Trackers

Forgd's marketing website at forgd.fit and the trainer dashboard at trainers.forgd.fit are hosted on Cloudflare Pages. The marketing site sets no first-party cookies for tracking or analytics. Web fonts are loaded from Bunny Fonts (fonts.bunny.net), an EU-based privacy-friendly font CDN that does not log IP addresses for tracking purposes. The trainer dashboard uses session cookies (HttpOnly, Secure, SameSite=Strict) for authentication only. These are functional and not used for tracking.

The Forgd iOS app does not use the web cookie infrastructure for app data; identity tokens live in the iOS Keychain (Section 3).