Privacy and your data

Effective 9 November 2026. Ride Compute is provided by TimeMechanic, the developer shown on Google Play. Contact [email protected] for privacy, support or data requests.

Request deletion of your online identity or data

Ride information on your phone

Ride recording, saved routes and ride history are stored on your device. Records can include exact location, times, speed, elevation, heart rate, cadence, power estimates and connected sensor information. Rider and bike settings, workouts, privacy zones and attached photos are also stored locally. The features and sensors you use determine which information is recorded. We do not upload your full ride history to our backend as part of subscription verification or Group Ride.

Permissions and choices

• Location supports ride recording and navigation, including an ongoing ride while the screen is off.
• Bluetooth connects compatible cycling sensors. Notifications show ongoing ride activity.
• Optional microphone access supports acoustic coasting detection. Audio is processed on your phone; raw audio is not saved or uploaded.
• Optional safety and check-in SMS can send your location to a recipient you choose, including automatically while you enable that feature. SMS is handled by your carrier and is not end-to-end encrypted.
• Nearby-device and Wi-Fi permissions support available positioning features. Android settings let you change permissions.

Maps, weather, searches and routes

Online requests can reveal your IP address and the map area, coordinates, search text or route involved. Online maps load directly from OpenFreeMap. The app also uses Open-Meteo for weather and fallback elevation, Photon and Overpass for online place information, BRouter for online routing, and Google Play services for Android location. These providers process requests under their own policies.

Offline downloads are prepared by our privately managed map service. A request includes your verified online identity, selected city or area and, for a route download, the saved route, stops and guidance. We retain these requests and private package records to prepare, resume and refresh downloads and enforce usage limits. Map, road and place data comes from redistributable OSM-derived datasets; shared map resources contain no personal ride history. Custom-area and route downloads remain usable on your phone for six months after verification or refresh; city downloads do not automatically expire. Expiry never deletes your saved routes or ride history. Installed offline maps, place search and route calculation run on your phone within their downloaded coverage. Weather and other online services still require a connection. Use the deletion-request process below to remove your online download records.

Accounts and optional Community

Core recording works without a public profile. Online services use a RideCompute identity. A verified email-code or Google account is required for Community, account allowances and new subscription purchases. Our Supabase services run on privately managed servers. Sign-in providers process authentication information. We retain your identifier, verified email, profile choices, friendships, Club memberships and usage receipts while providing the service.

Profiles start private. Username discovery, statistics audiences, public profiles, public leaderboards and public Club contributions are separate choices. The public website can show deliberately published names, preset artwork, trophies, selected basic totals and selected Club affiliations without visitor sign-in. Public profiles exclude email, heart rate, weight, ride maps and exact ride times. Publication cannot recall copies another person saved. Blocking and reporting are available.

Optional activity sync uploads aggregate distance, active time, ascent and bounded observed active intervals for future eligible RideCompute recordings. It does not upload GPS tracks, raw sensors, heart rate or weight. Sync requires a separate account-bound opt-in. Imported and simulated activities do not earn trophies. Offline uploads, corrections and moderation may change provisional results. Contributions follow membership, plan and publication permissions. Private recordings retain their full statistics.

Optional private account library

Private library sync is separate from activity contributions and public sharing. It starts only after you enable selected scopes for your verified account and explicitly attach device items. Depending on your selection, it can upload complete ride records, exact GPS tracks, sensor samples and diagnostics, lap marks, ride notes and points of interest, personal planned routes, stored progress summaries and saved map-area references. Private library objects are restricted to your account; signing in does not attach existing device data or publish it to other riders.

You can pause future sync. Removing an account copy leaves the device original in place, clears that cloud object and its replay copies, and removes unreferenced raw ride parts and derived progress. Parts still referenced by another account copy you chose to keep remain until those copies are removed. Deleting a device original does not silently remove a retained account copy. Account deletion removes the private library and consent. Minimal revision, checksum and deletion records remain to prevent restored or delayed items from recreating deleted content. Restricted backup and snapshot windows described below also apply. The service enforces object, payload and request bounds and reports unavailable storage or conflicts; it does not claim that a failed or interrupted transfer succeeded.

Live group rides and home privacy

Live rides are separate from permanent Clubs. The service processes membership, names, deliberately shared planned routes and invitations. It processes your latest location only when you enable sharing. Joining does not enable sharing or start recording. Home privacy zones hide protected geometry in supported viewing and sharing surfaces; private recorded measurements remain unchanged. Do not put private addresses in profile or route descriptions.

Live markers hide after 60 seconds without updates. Cleanup clears stale positions and positions in ended or expired sessions. Live sessions expire after eight hours; their records and routes are removed seven days later. Permanent Groups, friendships and opted-in content remain until deleted or no longer needed. Short-term abuse and retry records follow the operating policy. Minimal moderation and deletion receipts may remain to prevent abuse and restored data from republishing deleted activities.

Subscriptions

Google Play handles purchases and payment details. RevenueCat processes the RideCompute account identifier, purchase tokens and purchase history, subscription status, product information and technical information such as app/SDK versions and device/platform information. Our backend checks subscription eligibility and retains verified access periods linked to the verified RideCompute account. It does not receive your payment-card number. Google Play and RevenueCat operate internationally and their processing may occur outside Australia. See RevenueCat's privacy policy and Google's privacy policy.

Subscriptions renew according to the offer shown by Google Play. Manage or cancel them in Google Play subscriptions. Deleting app data or uninstalling the app does not cancel a subscription.

App security checks

For selected online actions, Google Play Integrity checks the app version, Google Play license and device integrity. Google processes app and device attestation information and a cryptographic hash that binds the check to the request. We send no readable route, location or review code in that hash. Our backend sends the encrypted token to Google for verification and records only the action category and verification result, without the token, account identifier or location. These checks support abuse prevention and do not run for each recorded GPS update. See Google Play Integrity data handling.

Sharing you choose

Exports and backups may contain exact locations, ride and fitness metrics, settings and saved own-analysis reports. User-supplied integration credentials require a separate credentials export choice. Authentication tokens, entitlement grants, private signing keys and privileged backend keys are excluded. Keep archives private. Automatic backups use your selected device folder, schedule and retention controls. Manual backup and restore remain available. Optional intervals.icu uploads use the credentials you supply. Sharing, directions hand-offs and SMS use the destination or recipient you choose. Deleting a local record cannot recall copies already exported or shared.

Security and retention

App-to-backend connections use HTTPS. Database access is restricted to the backend, with private administrator access. Backup copies are held in access-restricted storage. Infrastructure providers process operational and security metadata, including network addresses and request timing, under their retention policies. Our application does not intentionally log request bodies or precise ride locations. We use service providers for app functionality, purchases, reliability and abuse prevention; the app has no advertising integration.

Local records remain until you delete them or clear the app's storage. Account, usage and verified access records remain while needed or until verified deletion is processed. Deleting a downloaded asset or saved report does not refund its finalized allowance. Payment providers may separately retain transactions for legal, tax and fraud-prevention obligations.

Delete your online identity or data

Verified users can request deletion in Community → Account settings after resolving permanent Club ownership. Publication is withdrawn before asynchronous erasure across Community, live rides, downloads, authentication and RevenueCat. Failed provider steps remain pending for retry and are not reported complete. Cancel Google Play subscriptions separately.

Email a deletion request to [email protected]. Put “Ride Compute data deletion request” in the subject. State whether you want your entire online identity deleted or only specific online data. Include your online ID if available in the app's privacy section, or enough information to locate your purchase or group, such as a Google Play order reference or group name and date. You can make a request without reinstalling the app.

Do not send passwords, access tokens or payment-card details. We verify ownership before acting and may ask for additional information to locate the correct records. A verified identity-deletion request removes that identity, its group memberships, groups it hosts and associated routes, access records and corresponding RevenueCat customer data. Other members may lose access to a deleted hosted group. Routine database backups, deployment database checkpoints and disk snapshots each follow a seven-day window. A snapshot containing an earlier database backup may retain removed data for up to fourteen days. Deletion receipts are replayed before restored data is exposed. Minimal deletion and fraud-prevention receipts are retained separately; any legally required retained records and the reason will be explained when handling your request. Google Play's own transaction records and copies previously shared with other recipients are controlled by those parties.

You can delete saved rides within the app or clear its storage in Android settings. These local actions do not delete online records or cancel subscriptions. Cancel subscriptions separately in Google Play.

Questions and changes

Use the contact address above to ask about access, correction or deletion of your information. This page's effective date changes when the policy is updated. Ride Compute provides cycling and fitness information, not medical diagnosis or treatment.