This policy describes the current RunMyTurf app and website, including the development release. RunMyTurf is operated by Anandsagar Sah. For privacy questions or support, email sah.anandsagar@gmail.com or use our contact form.
Activity and location data
When you record a walk or run, the app processes route locations, timestamps, distance, duration, steps and available motion information. Background location supports an activity you choose to record. GPS and motion evidence can also validate Territory claims and Race Turf results. These features require the relevant device permissions.
Your phone and your account
Guest activities are stored on your phone. Signing in uses Firebase Authentication and your selected sign-in provider. Supported activity history, private route backups, fitness settings and unit preferences can sync to your account. Optional fitness details include weight, height, birth year and the sex used by the calorie equation; they support estimates and remain private. Imported daily health totals remain on the phone. Not every device or appearance preference syncs.
Shared features
Your chosen public name, avatar or profile photo can appear with Territories, race results and group participation. Public territory boundaries and public race courses are visible through those features. Private workouts and fitness profiles are not public profiles. Group live location sharing is optional and limited to eligible participants while enabled; access expires independently of cleanup.
Sharing an image exports the content you select, which may reveal a route. Consider what you include before sending it to others.
Safety and adult testing
The initial testing release is intended for adults aged 18 and over. We store your acceptance of the current community terms and adult confirmation, your private block list, and reports you submit (account IDs, content reference, reason and timestamps) to operate shared features and respond to abuse. Reports and moderation decisions are accessible only to authorised service operators. They are not public posts. Account deletion removes associated reports and block records through the erasure worker.
Invitations
The website sends the code you open or enter to our service to check its category and availability. Anonymous previews do not show names, destination IDs, private routes or meeting locations. Joining and referral attribution require explicit actions in the app.
Service providers and security
Google Firebase and Google Cloud provide authentication, hosting, storage, database, notifications and server processing. Mapbox provides app maps. Its SDK can send de-identified location and map-usage data to Mapbox; use the information/attribution control on the map to review Mapbox’s policy and opt out of its telemetry. Mapbox’s control is separate from the Firebase analytics and crash options. Sign-in providers process authentication according to their own policies. Cloud service infrastructure may process data outside your country. Access controls separate private account data from shared features; no service can guarantee absolute security.
Optional app diagnostics and analytics
The app offers separate, default-off controls in Privacy for Firebase Crashlytics and Google Analytics. If enabled, these services process technical information such as app version, device information, crash stack traces, app interactions and pseudonymous installation identifiers. Analytics may derive approximate geography from network information. We do not attach your account ID, routes, fitness measurements, invitation codes or profile to analytics events. Advertising identifiers and advertising consent are disabled. You can turn either option off at any time. Turning off analytics resets its local identifier; previously processed reports are subject to the providers’ retention controls.
Website and support requests
This website uses no advertising or analytics trackers. Hosting and server providers process network information needed to serve and protect the site. Invitation and contact endpoints use time-bounded counters keyed by a daily hash of network addresses to limit abuse. The support form collects your email and message, a reference number, submission time and request status. These records are private to the service team. Do not submit passwords or sensitive health information.
Retention and deletion
Guest data remains on your device until removed. Account data remains while your account and the corresponding records exist; there is no blanket automatic expiry for activity history. Deleting a workout queues removal of its cloud backup when sync succeeds. This does not automatically remove associated shared Territory or race records.
You can request account and associated-data deletion. In the app, open Account & sync → Delete my account and sign in again to confirm. Accepted deletion blocks new cloud writes and schedules retryable cleanup of your account, profile, backups, settings, invitations, territories, race participation and groups/courses you created. Cleanup starts after a short drain period, normally within ten minutes; service failures may delay completion. Deleted storage objects remain in Google Cloud’s restricted soft-delete recovery for seven days before permanent removal. A minimal account-ID deletion marker is retained to prevent stale devices from restoring deleted data. Deleted accounts are removed from referral totals. If your referrer deletes their account, we retain only a minimal already-referred status on your still-active account, without their identity or code, to prevent reassignment of referral eligibility. Email deletion requests require ownership verification before the same cleanup can be initiated. Uninstalling or signing out does not delete a cloud account. Request records and infrastructure logs are not covered by a promised fixed deletion period in this development release; ask the team about the scope of your request.
Your choices
Use your device settings to manage location, motion, health and notification permissions. Use the app’s activity controls to manage saved workouts and sharing controls to manage participation. Contact the team to request access, correction or deletion of account information.
Changes
We will update this page when the service’s data practices change. Store privacy disclosures will be completed against the actual release before public app distribution.