RecordsOPENBIKE
DownloadFeaturesOpen Records
//

PRIVACY POLICY

OpenBike · Last updated 3 August 2026

OpenBike has no account, no server and no paywall. It does not send your rides anywhere. Everything below explains what that means in practice.

The short version

OpenBike stores your rides, routes and settings on your device. There is no OpenBike account to create and no OpenBike server to sync with, so there is no copy of your training data held by us to lose, sell or hand over.

What OpenBike stores on your device

  • Your training settings, such as FTP and body weight.
  • Your ride history and the activity files each ride produces.
  • GPX route files you import, and the workouts you create or use.
  • The identifiers of sensors you have paired — trainer, heart-rate monitor, cadence and speed sensors — so the app can reconnect to them.
  • App preferences, such as units and display options.

This data stays in the app's own storage. Uninstalling OpenBike, or clearing its data from your device settings, removes it.

What OpenBike sends off your device

Nothing, by itself. OpenBike does not upload your rides, routes, settings or sensor data. It contains no advertising SDK and no third-party analytics.

Data only leaves your device when you move it: when you export a ride as a .fit file and share, upload or copy it somewhere else. Where it goes then, and what happens to it, is governed by whichever service or app you sent it to.

Sensors and permissions

To talk to a smart trainer and your sensors, OpenBike needs Bluetooth access. On Android, scanning for nearby Bluetooth devices also requires the "nearby devices" permission, and on older Android versions the system requires location permission to perform that scan. OpenBike uses it only to find and connect to your training hardware — it does not collect, store or transmit your geographic location.

The app also needs access to files you choose, so it can read the .gpx routes you import and write the .fit files you export.

Installing from Google Play

OpenBike is distributed through Google Play. Google collects its own data around app distribution — installs, crashes and, if you have opted in, usage statistics — under Google's privacy policy. That collection is Google's, not ours, and we receive only aggregate, anonymous statistics through the Play Console.

OpenBike and Records

OpenBike is made by the team behind Records, but the two do not share data. Downloading a .gpx route from your Records profile and opening it in OpenBike is a manual step you take yourself. There is no automatic sync in either direction, and OpenBike does not sign you in to Records or read your Records profile.

Records has its own, separate privacy policy covering accounts and race results: records.run/privacy-policy.

Children

OpenBike is a training tool intended for a general audience and is not directed at children. Since it collects no personal data, it does not knowingly collect anything from children either.

Your rights

Under the GDPR you have the right to access, correct, export and erase your personal data. Because OpenBike holds your data only on your own device and we hold no copy, there is nothing for us to retrieve or delete on your behalf: your data is already entirely in your hands. You can export it at any time as .fit files, and erase it by clearing the app's data or uninstalling it.

Changes to this policy

If a future version of OpenBike introduces a feature that changes any of the above — an optional account, ride sync, or crash reporting — this policy will be updated before that version ships, and the date at the top will change.

Contact

Questions, or something here that does not match what you see in the app? Open an issue on GitHub or email support@records.run.

OpenBike v1.0.0 · A Records app
RecordsPrivacySupportRelease notes