Play Data Safety Answers — TrackIron
Use this page when filling out the Google Play Console → App content → Data safety form. Answers match what the shipped app actually does: optional Google sign-in, local-first storage, and Supabase cloud sync only for signed-in users.
Play Console labels change over time. Map these answers to the closest matching categories in the form.
1. Overview answers
- Does the app collect or share user data? Yes.
- Is all user data encrypted in transit? Yes (HTTPS for Google Sign-In and Supabase).
- Can users request that data be deleted? Yes — see Request Data Deletion.
- Do you provide a way for users to request data deletion? Yes (in-app clear data / uninstall for local; email request for cloud).
2. Data collected
Declare collection for the types below. Primary purpose for each: App functionality.
Personal info
| Type | Collected? | Notes |
|---|
| Name |
Yes |
Display / profile name. Stored on device; synced to Supabase when signed in. |
| Email address |
Yes |
Only when the user signs in with Google (via Google → Supabase Auth). Not collected in guest mode. |
| User IDs |
Yes |
Supabase auth user ID for signed-in accounts. Guest mode uses a local profile id only on-device. |
| Address, phone, race/ethnicity, political/religious beliefs, sexual orientation |
No |
— |
Health and fitness
Yes — declare Health and fitness data. Play treats this category strictly.
- On device (guest or signed-in): weight, height, age, gender, activity level, calorie goals, workout logs (sets/reps/weights/duration), nutrition entries, personal records, progress metrics.
- Cloud (signed-in only): profile fitness fields (name, weight, height, age, gender, activity level, daily calorie goal) and eligible leaderboard personal records (display name, exercise, weight, reps, estimated 1RM).
- Not uploaded: full workout history, nutrition log, hydration settings, achievements remain on-device only.
Other common categories
| Category | Collected? |
|---|
| Financial info | No |
| Location | No |
| Photos and videos | No |
| Audio files | No |
| Contacts | No |
| Calendar | No |
| Messages / SMS | No |
| Web browsing | No |
| App activity / search history (beyond in-app workout/nutrition logging) | No separate analytics SDK; declare only what you actually log as app functionality above |
| Device or other IDs (advertising ID) | No advertising ID collection by the app |
3. Data shared
- Is data shared with third parties? Yes, for signed-in users only.
- Google: Sign-in (email / account identifiers as part of Google Sign-In + Supabase Auth).
- Supabase: Profile fields and eligible leaderboard PRs for signed-in users. Leaderboard entries (display name + lift details) are visible to other signed-in users.
- Guest mode: No cloud sharing of profile or fitness data.
- Sold? No. Data is not sold.
- Purpose of sharing: App functionality (account, sync, leaderboard).
4. Processing / ephemeral vs stored
- Data is stored (not only ephemeral): on-device SQLite / app storage; cloud rows on Supabase for signed-in users.
- Guest users: stored on device only.
5. Guest vs signed-in (important for accuracy)
| Guest | Google signed-in |
|---|
| Email / Google account |
No |
Yes |
| Local workouts / nutrition / PRs |
Yes (device only) |
Yes (device) |
| Cloud profile sync |
No |
Yes (Supabase) |
| Cloud leaderboard PRs |
No |
Yes, when eligible |
6. Security practices to declare
- Data encrypted in transit (HTTPS).
- Users can request deletion of cloud account/profile/leaderboard data.
- Users can delete local data via Android clear storage / uninstall.
7. Related links for Play Console
If Play Console asks whether health data is collected: answer Yes. If it asks whether that data is shared: answer Yes for signed-in cloud sync / leaderboard; guest-only use does not share health data off-device.