Privacy policy

Routa Cycling is a local-first app. Your training data lives on your device by default. This page explains exactly what we collect, what we never collect, and the only situations in which any data leaves your device.

The following categories of personal data may be collected or transmitted by the app. These are the data types disclosed to the app stores. All third-party integrations are off by default and activate only when you sign in, subscribe, or enable them yourself.

• Email Address. Used for cross-platform subscription management. When you enable Google Drive sync, Google Sign-In also returns the account email to the app.
• User ID. Third-party identifiers received and stored so integrations can reconnect — specifically your RevenueCat app user ID.
• Purchase History. Subscription purchase records are tracked by RevenueCat so the correct subscription tier is entitled across your devices.
• Fitness. Power, heart rate, cadence, and workout files, plus FTP and body-weight history, sync optionally to Google Drive.
• Other User Content. Workout name and description strings are stored locally and included in optional workout/FIT backups to Google Drive.

The following information is stored locally on your device in the app's database, which is encrypted at rest so your training data is not stored in plain text. It is not transmitted anywhere unless you explicitly enable one of the optional integrations described above or below.

• Profile name, FTP, body weight, height, age, and gender (only what you enter yourself).
• App settings: theme, language, unit system, and other preferences.
• Workout history: date, duration, average and maximum heart rate, cadence, speed, training load, intensity ratio, efficiency factor, and decoupling.
• Time-series sensor data recorded during workouts (power, heart rate, cadence, speed, elevation grade, and GPS location coordinates from FIT files). See Location data below for details.
• Calculated performance metrics: fitness, fatigue and form scores, phenotype classification, fatigue resistance, and other derived metrics.
• Identifiers and names of Bluetooth and ANT+ sensors you have paired.

When a workout is recorded with GPS — either through a paired GPS-capable device or from an imported FIT file — the app stores precise location coordinates (latitude, longitude, and elevation) as part of the workout's time-series data. This lets you view your route on a map and calculate route-based metrics.

GPS location data is treated like all other training data: it is stored locally on your device and is not transmitted anywhere by default. It only leaves your device if you choose to back up or sync your workouts to iCloud or Google Drive, or export a workout/FIT file yourself. We do not use your location for advertising, profiling, or tracking, and we never share it with third parties for those purposes.

When you view a route on a map, map tiles are requested from the map provider (see Maps under Third-Party Services). This may reveal the approximate area of your route to that provider in order to serve the tiles, but your recorded coordinates are not uploaded to it.

• No advertising identifiers (such as IDFA) and no advertising networks.
• No personal data is sent to analytics or crash-reporting services.

Analytics and crash reports are off by default. You can opt in to either from Profile → Support, and you can turn them back off at any time from the same screen.

If you enable analytics, Firebase Analytics receives screen views and a small set of usage events (such as workout started/completed, sign-in, and subscription) tied to an anonymous Firebase Installation ID. No advertising ID (IDFA) and no personal data is collected.

If you enable crash reports, anonymized crash diagnostics are sent so we can identify and fix issues. Crash reports do not include personal data or your training data.

All of the following integrations are off by default. They activate only after you sign in, subscribe, or enable them yourself, and you can disconnect any of them at any time from the Profile screen.

• RevenueCat. Used to manage subscriptions across platforms. RevenueCat receives your purchase history, an app user ID generated for you, and — where required for cross-platform entitlement — your email address. Use of RevenueCat is governed by RevenueCat's own privacy policy.
• Google Sign-In & Google Drive. When you enable Drive sync, you authenticate with Google. Google Sign-In returns your account email to the app, and selected data (such as FTP and body-weight history, and optionally workout/FIT backups) is stored in your own Google Drive. Use of these services is governed by Google's privacy policy.
• iCloud (via CloudKit). When you back up or sync your data to iCloud, an encrypted copy may be transferred to your own iCloud container. Only you can access it.
• Maps. For workouts with GPS data available, the map tiles are downloadable or accessed in real-time via internet. The current map provider is OpenFreeMap, which does not require user accounts or collect personal data. Please refer to OpenFreeMap's privacy policy for more details. We reserve the right to change the map provider in the future, and if we do, we will update this privacy policy accordingly.

When you pair a sensor, the app stores its identifier and name locally so it can reconnect later. Live sensor readings (power, heart rate, cadence, speed) are processed on your device and stay on your device unless you choose to upload the resulting workout to one of the optional services above.

• All your data lives in the local database by default. Uninstalling the app removes it. However you can also export your data as a backup file, which you can store or share as you wish. Also, you have an option to back up your data to iCloud or Google Drive at your discretion, which allows you to restore it if you switch devices or accidentally delete the app.
• You can disconnect third-party integrations at any time from the Profile screen.
• You can delete individual workouts from your history at any time.

We may update this Privacy Policy from time to time. We will notify you of significant changes by posting the updated policy on this page with a revised date.

If you have questions about this Privacy Policy, please contact us at support@routacycling.com.