Private by default.
Road to 50 is designed to support a small-group fitness and accountability challenge without turning private body or health information into public competition.
1. What this policy covers
This Privacy Policy describes how the Road to 50 iOS app (“Road to 50,” “the app,” “we,” or “us”) handles information when you use the app.
2. Information used by Road to 50
Identity and account information
When you use Sign in with Apple, Road to 50 and its authentication provider may process your Apple-linked user identifier, display name, and email address when Apple provides one.
Shared accountability information
Road to 50 stores team names, memberships, invite codes, weekly execution scores and score components, workout A/B completion states, activity events, weekly results, and reactions used by the private team experience.
3. HealthKit and private fitness data
With your permission, Road to 50 can read selected Apple Health / HealthKit information to reduce manual logging, including data such as steps, sleep, workouts, weight, body fat percentage, lean body mass, BMI, and height.
What stays private
Road to 50 does not upload raw HealthKit samples such as your raw step counts, sleep durations, weight, body-fat measurements, or other body metrics to the Road to 50 Supabase backend.
The app may share derived execution information needed for the private team experience — for example, movement points, sleep points, weekly execution score, and whether Workout A or B was completed. These are adherence/game mechanics rather than raw HealthKit measurements.
Road to 50 does not use HealthKit information for advertising, data brokerage, or cross-app tracking.
4. Information stored locally on your device
The current version keeps several sensitive items in app-local storage rather than uploading them to the Road to 50 backend, including:
- starting and target weight;
- your personal “Why”;
- raw body-composition and HealthKit detail displayed by the app;
- meal logs, meal photos, and notes;
- progress photos and Then/Now comparisons; and
- your Road to 50 profile photo.
Road to 50 does not intentionally upload these items to its Supabase backend. Device-level backups, including Apple/iCloud backups, are controlled by your device and Apple account settings.
5. How information is used
We use information only to provide and operate Road to 50, including authentication, onboarding, scoring, team membership, private leaderboards, team missions, progress views, reminders, account security, and account deletion.
Road to 50 currently contains no third-party advertising and does not sell personal information or use personal information for cross-app advertising tracking.
6. Service providers
Supabase
Road to 50 uses Supabase for authentication and the shared team database. Supabase processes server-side account and team information on our behalf to provide those functions.
Apple
Road to 50 uses Apple platform services including Sign in with Apple, HealthKit, local notifications, and standard iOS system capabilities. Information handled directly by Apple is also governed by Apple’s policies and your Apple settings.
7. Data sharing
Road to 50 does not make your data public. Other active members of a team can see team-visible accountability information such as your display name, weekly execution score, rank, workout-achievement events, weekly wins, and reactions.
Raw weight, body composition, progress photos, meal photos, and raw HealthKit detail are not made visible to teammates by the current app.
8. Retention and account deletion
Server-side account and team information is retained while your Road to 50 account remains active, unless it is removed earlier as part of normal app operations.
You can permanently delete your Road to 50 account from Profile → Account → Delete Account. The deletion flow removes the account and associated server-side data, clears Road to 50’s local private data from that device, and revokes the Sign in with Apple authorization used by the app.
If you own a team with another active member, ownership is transferred before your account is removed. If no other active member remains, that team is deleted.
9. Security
Road to 50 uses measures designed to limit access to shared information, including authenticated access, Supabase Row Level Security policies, member-scoped team access, and device-local storage for particularly private content. No security method is guaranteed to be perfect, but the app is designed to minimize the amount of sensitive information stored on its backend.
10. Children
Road to 50 is not directed to children under 13, and we do not knowingly solicit accounts from children under 13.
11. Changes to this policy
We may update this policy as Road to 50 changes. The current version will be posted at this URL with its effective date.
12. Contact
Questions about privacy or Road to 50 can be sent to support@neilbuilds.com or through the Road to 50 Support page.