RideWatts has no RideWatts account system or application server. Most app data is stored in the app's local container. This policy explains what RideWatts stores, what can leave your device, why it is used, and the choices available to you.
Data stored on your device
RideWatts stores settings, selected Bluetooth device identifiers and names, imported and cached workouts, Intervals.icu account details, ride history and ride recordings locally. Ride recordings can contain timestamps, workout names, power, cadence, heart rate, speed, distance and summary statistics.
Intervals.icu credentials are stored in the platform keystore — the Keychain on Apple devices, the Android Keystore on Android — and not in a RideWatts server. On Linux, which has no universal keystore, they are stored as plain JSON in the app's private container instead; the app says so on the accounts screen.
On Android, RideWatts disables Android Auto Backup, so its container is not copied to your Google account. On other platforms your operating system may include the app container in a device or cloud backup, and copies in such a backup are governed by that provider's retention and deletion practices.
Crash reporting and analytics
Supported release builds can use PostHog's EU Cloud for product analytics and crash reporting. RideWatts asks you on first launch, and sends nothing until you answer. If you decline, the analytics SDK starts disabled and does not contact PostHog. You can change your answer at any time in Settings.
PostHog assigns a persistent random identifier to the app installation; RideWatts does not send your name, email address or Intervals.icu athlete ID as an analytics identity, and never calls the SDK's identify function. That identifier is random rather than anonymous: it does not name you, but it does distinguish your installation from another. RideWatts shows it to you in Settings under "Copy analytics ID", so you can quote it if you ask what was collected or ask for it to be deleted.
Analytics can include app name, version and build, device type and model, operating system, screen size, locale, time zone, network type and whether the build came from TestFlight.
As with any network request, sending an event necessarily reveals your IP address to the receiving server. Our PostHog project is configured to discard client IP data, so the address is not stored on events and is not used to derive your location; no country, region or city is recorded. PostHog may still process connection information transiently for delivery and security under its own privacy terms.
Your trainer. To understand trainer compatibility and reliability, RideWatts records the trainer's advertised Bluetooth name after attempting to remove a recognized serial-like suffix, plus manufacturer, model, firmware, hardware and software versions and advertised capabilities such as power range and ERG support. Hardware names do not follow one standard, so this normalization cannot guarantee that every unit-specific fragment is removed. RideWatts does not request the Bluetooth Serial Number or System ID characteristics.
When your trainer misbehaves. We record trainers that fail to connect, as a classified reason and a number of attempts; trainers that refuse a command, as the numeric Bluetooth command and response codes; and, for each ride, how often the trainer dropped or fell silent, how many commands it refused, and how many seconds it spent disconnected.
Heart rate monitors and remotes. For a heart rate monitor we record only the manufacturer, model and firmware versions it reports — never its Bluetooth name, which routinely contains a per-unit serial such as "Polar H10 12345678". For a handlebar remote we record only that one is in use, and what kind it is.
Your rides. How long a ride lasted, whether it was ERG or free ride, whether it was resumed after an interruption, and whether the workout came from a local file or from Intervals.icu. If a ride ends abnormally — a crash, a force quit, a flat battery — we record that it did and how long it had been running.
RideWatts does not intentionally add your name, email address, Intervals.icu credential or athlete ID, workout or ride names, sensor readings, full ride recordings, Bluetooth addresses, or the advertised name of a heart rate monitor or remote to analytics events. Crash reports contain exception messages, diagnostic context and stack traces; unexpected error text may include other runtime information.
We do not use this information for advertising, sell it, or use it to track you across other companies' apps or websites. PostHog retains telemetry according to the retention settings of our PostHog project and processes it on our behalf.
You can turn analytics and crash capture off for the whole device in RideWatts settings, and back on again at any time. The setting takes effect immediately, without restarting the app. Where you have declined or turned it off, the SDK is started in an opted-out state and is configured not to fetch feature flags or surveys while starting, so it does not contact PostHog; while disabled, RideWatts does not intentionally capture analytics events or crash reports.
Intervals.icu
Connecting Intervals.icu is optional. If connected, RideWatts communicates directly with Intervals.icu, authenticating with an access token obtained when you sign in through Intervals.icu in your browser, or with an Intervals.icu API key if you have chosen that method instead. The app can read and locally store account and athlete IDs, athlete names, profile-image URLs, followed or coached athletes, FTP and training zones, planned workouts, workout-library entries, workout descriptions and notes, event identifiers, completion status, duration and training load. A profile image may be fetched from the URL supplied by Intervals.icu.
When upload remains selected on the ride summary, RideWatts sends a completed FIT activity directly to your selected Intervals.icu athlete account. The FIT file can contain timestamps, duration, power, cadence, heart rate, speed, distance and summary values. The request also includes the ride or workout name, a RideWatts ride identifier, the recording-device name and, when applicable, the planned-event ID. This transfer does not pass through a RideWatts server.
RideWatts intentionally sends your access token or API key only to Intervals.icu, and stores it as described under "Data stored on your device" above. Intervals.icu processes data under its own account terms and privacy policy.
Bluetooth
RideWatts uses Bluetooth to scan for and connect to an FTMS smart trainer and, optionally, a heart rate monitor and handlebar remote. It stores identifiers and advertised names for devices you select so it can reconnect. Sensor readings are handled locally except when included in an Intervals.icu ride upload as described above. On Android 11 and earlier, the operating system requires location permission for Bluetooth scanning; RideWatts does not request or use GPS coordinates.
Retention and deletion
You can delete individual rides from ride history. When a new ride starts, RideWatts generally keeps the newest 50 settled rides; pending uploads, failed uploads and unfinished recordings may remain until you delete them. Imported workouts, cached workouts and per-rider settings may remain until the app is removed or its data is cleared.
Removing an Intervals.icu account removes its saved credential from the account list, but does not automatically delete existing rides, cached workouts, selected devices or per-rider settings. You can revoke the API key through Intervals.icu. Removing the app or clearing its app data deletes its local container, although copies may remain in operating-system backups.
You may email us to ask about access to or deletion of telemetry or support information. RideWatts does not associate PostHog's random installation identifier with your contact details, so on its own we cannot tell which telemetry records are yours — but the app shows you that identifier in Settings under "Copy analytics ID". If you send it to us with your request, we can locate and delete the telemetry for that installation. Turning telemetry off prevents further intentional capture; it does not withdraw what was already sent, which is why the identifier is worth keeping if you intend to ask.
Website and support
This website is hosted by Cloudflare, which may process connection information such as your IP address, browser information and request logs for delivery and security. The site does not contain RideWatts analytics, advertising pixels, cookies or forms.
If you email support, we receive your email address, message and any information or attachments you choose to provide. We use it to respond, diagnose issues and maintain appropriate support records, and retain it only as long as needed for those purposes or legal obligations.
Third-party services
PostHog processes telemetry on our behalf. Intervals.icu receives account and activity data at your direction. Cloudflare hosts this website. Each service also publishes its own privacy terms.
Children
RideWatts is not directed at children under 13, and we do not knowingly collect information from them.
Contact
Questions or privacy requests? Email Eric Evenchick at [email protected].
Eric Evenchick is the person responsible for the protection of personal information — the Privacy Officer for the purposes of Quebec's Law 25 — and can be reached at the same address.