Privacy Policy
Last updated: 3 July 2026
The short version: Crux has no account, and your rides, training data and bike details are never uploaded — they're analysed and stored on your phone. Crux makes limited technical network requests to check for app updates and load route maps, as explained below.
What Crux stores — on your device
- Rides you import — the activity files (e.g. FIT) you add, and the metrics Crux computes from them: power, heart rate, distance, elevation, training load, zones and gear usage.
- Your bikes & settings — the drivetrains, preferences and values (FTP, weight, units) you enter.
All of this is saved locally in the app on your phone. Crux doesn't upload it.
What Barton Works receives from the app
Crux has no analytics, no advertising and no cross-app tracking. The app doesn't send your rides, training data, bike details or any app analytics to us — we have no way to see your data.
When Crux connects to the internet
Crux's ride analysis works offline. The app makes two kinds of standard network request, and neither sends your rides, training data or bike details:
- App updates. Crux uses Expo's update service to deliver improvements. Update requests contain technical information needed to serve the correct update, including the device operating system, Crux project ID, a randomized installation token and standard network information such as the IP address. No ride, training or bike data is included, whether you installed Crux from the App Store or Google Play. See Expo's privacy policy.
- Route maps. When you open a map for a ride or course, the map provider for your platform — Apple Maps on iPhone, or Google Maps on Android — receives the map region being viewed, along with standard request information such as your device, software and network details (including IP address), so it can provide map imagery. Crux requests no location permission and shows no live location, and does not send the map provider your FIT or GPX files, training metrics or bike details. See Apple Maps & Privacy and Google's privacy policy.
Device backup
If device backup is enabled, your phone's operating system may include Crux's local data in your encrypted device backup — iCloud Backup on iPhone, or Google's backup service on Android. Barton Works cannot access that backup.
Importing files
When you import an activity file — or open one into Crux from another app — it's read and processed entirely on your device. Crux doesn't upload it.
Your control
- Delete any individual ride in the app at any time.
- Remove all Crux data by deleting the app — its local data goes with it. A copy may remain in an encrypted device backup (iCloud on iPhone, or Google's backup on Android) until that backup is updated or deleted.
This website
This website (barton.works) is operated by Barton Works and served by a third-party hosting provider. As with most websites, the host automatically records standard server logs — your IP address, browser type and the pages requested — to keep the site secure and reliable. The site runs no analytics, sets no advertising or tracking cookies, and serves its fonts from the site itself, so loading a page makes no third-party tracking requests.
Email correspondence
If you email us at brad@barton.works, we keep your message and email address so we can reply and follow up. We don't add you to a mailing list or use your address for marketing.
Changes to this policy
We'll update this page if Crux's data practices change. If Crux-managed cloud features, such as cross-device sync, are added in future, they would be strictly opt-in and described here before you use them.
Contact
Questions about privacy: brad@barton.works.