Privacy policy

Last updated: 29 August 2026

Rider Tracker (“the app”) is a group-ride navigation product operated for the Android app com.ridertracker.app. This policy describes what we collect, why, who sees it, and how you can delete it. We do not sell personal data.

Who we are

Contact: use Profile → Delete account in the app, or ridertracker.com/delete-account. Public site: https://ridertracker.com.

What we collect

• Account. When you sign in with Google we store your Firebase user id, display name, email, and (if you choose) profile photo. You may set a catalog avatar or a phone number for pack “Call” — the phone number is not verified by SMS.
• Precise location (continuous during a ride). While you are a joined member of an active ride, the app records high-accuracy GPS in a foreground service. Live coordinates are published to other joined members of that ride only. A local GPS trace is stored on your device and, when the ride ends, uploaded so the recap and (if shared) public trip page can show the host route. Location sharing stops when you leave, the host ends or cancels the ride, or you sign out.
• Ride metadata. Ride name, planned route, stops, member list, status messages (refuel, food, rest, help), and recap stats (distance, duration, trace).
• Optional stop photos. If you attach a photo to a stop, the compressed image is stored in Firebase Storage and visible to joined members. A public trip page uses a download token, not an open bucket listing.
• Push tokens. Firebase Cloud Messaging tokens so we can notify you when a ride starts, a pack member needs help, or the ride ends.
• Diagnostics. Crashlytics crash reports (stack traces, device model, app version) and Firebase Analytics events for product funnels (trial, paywall, navigation engine). We do not use ads SDKs.
• Purchases. If you subscribe to Rider Tracker Pro, Google Play processes payment. We store a hashed purchase token and expiry on your entitlement document so we can unlock Navigation SDK guidance. We do not see your full card number.
• Navigation (Pro). When Pro or trial navigation is on, Google Navigation SDK processes your location and the shared route to provide turn-by-turn guidance. Google’s Maps terms apply. You can decline Pro and keep using the free in-app map.

Who we share with

• Joined ride members see your live location, status, name, and avatar for that ride only.
• Google (Maps, Places, Routes, Navigation SDK, Firebase, Play Billing, Play Integrity) processes location, search, routing, and purchases as needed to run the app. Google’s terms apply to those services.
• We do not sell data, run ads, or share location with emergency services. “Need help” alerts the pack only.

Legal bases and purpose

We process this data to provide the group-ride product you request: plan a route, invite a pack, navigate together, and recap the ride. Precise location is required for live pack positions and is not used for advertising or profiling.

Retention

• Live location in the realtime database is removed when the ride ends, is cancelled, or you leave.
• Finished rides, recaps, memberships, GPS traces, stop photos, share pages, and trip indexes are deleted by a scheduled job after 90 days.
• Expired route drafts (1 hour) and unused invites (7 days) are deleted hourly.
• Crash reports follow Google Firebase Crashlytics retention.

Your choices

• Decline location or notification permission — you cannot host or join a live ride without location.
• Leave a ride or ask the host to end it to stop sharing immediately.
• Delete your account in the app (Profile → Delete account). We cancel rides you host, leave rides you joined, delete your profile and trip list, delete stop photos you uploaded, and delete your Auth record. Residual copies in other members’ recaps may remain until the 90-day ride retention job runs.

Children

The app is not directed at children under 13 (or the applicable age in your country). Do not create an account for a child.

International processing

Firebase project data may be processed in Google Cloud regions used by this project (including the United States for Storage and nam5 for Firestore, and asia-south1 for Cloud Functions).

Changes

We will update this page if collection or sharing practices change. Continued use after an update means you accept the revised policy.