Play Data Safety Answers — TrackIron

Last updated: September 2, 2026

App: TrackIron (com.trackiron.app)

Developer: Shrikant Deokrishna Hiwase

Use this page when filling out the Google Play Console → App content → Data safety form. Answers match current product direction: Google sign-in is optional — guest mode lets you use the app fully on-device with no account — local-first workout/nutrition storage, Supabase cloud sync for profile/leaderboard (signed-in users only), and no advertising or analytics SDKs.

Play Console labels change over time. Map these answers to the closest matching categories in the form. Update this page again if guest mode, ads, or analytics SDKs change.

1. Overview answers

Does the app collect or share user data? Yes, for signed-in users. Guest-mode users generate no server-side data.
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 account/fitness data: App functionality. Fields below are collected only for users who choose Google sign-in; guest-mode users are not required to provide any of this.

Personal info

Type	Collected?	Notes
Name	Yes (signed-in users)	Display / profile name. Stored on device; synced to Supabase only if signed in.
Email address	Yes (signed-in users)	Collected only when the user chooses to sign in with Google (via Google → Supabase Auth). Not collected in guest mode.
User IDs	Yes (signed-in users)	Supabase auth user ID for the signed-in account. Guest mode has no server-side user ID.
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	Workout/nutrition logging for app functionality only. No analytics SDK is used.
Device or other IDs (advertising ID)	No — the app does not use advertising or analytics SDKs

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), plus Android Backup / Restore Credentials for device migration.
Supabase: Profile fields and eligible leaderboard PRs. Leaderboard entries (display name + lift details) are visible to other signed-in users.
Advertising / analytics providers: None. The app does not use advertising or analytics SDKs.
Sold? No. Data is not sold.
Purpose of sharing: App functionality only (account, sync, leaderboard).

4. Processing / ephemeral vs stored

Data is stored (not only ephemeral): on-device SQLite / app storage for all users; cloud rows on Supabase for signed-in users only.
Sign-in is optional — guest mode is a fully local, no-account mode.

5. Account model

Item	Behavior
Guest mode	Available — full local logging with no account, nothing sent to the cloud
Email / Google account	Optional — required only if the user chooses to sign in
Local workouts / nutrition / PRs	Yes (device), for both guest and signed-in users
Cloud profile sync	Yes (Supabase), signed-in users only
Cloud leaderboard PRs	Yes, when eligible and signed in
Restore Credentials (device migration)	Signed-in users only; guest users stay in guest mode on a new device

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

Privacy policy URL: your published Privacy Policy page.
Data deletion URL: Request Data Deletion.

If Play Console asks whether health data is collected: answer Yes for signed-in users. If it asks whether that data is shared: answer Yes for cloud profile sync / leaderboard (signed-in users), and No for advertising or analytics partners.