THE DETAILS, IN THE OPEN
Privacy policy.
Your ride is personal. Here’s how your information is used.
This policy covers the ProTour cycling app and this marketing website. It describes the app’s current data flows. Privacy requests and questions can be sent to [email protected].
1. Account and rider profile
When you sign up using email or Sign in with Apple, the app uses a user identifier and your email address, including a private relay address if supplied by Apple. Your rider profile can include your display name, weight, functional threshold power (FTP), rider type, and home country.
Account and profile information is stored using Supabase to authenticate you, personalize your experience, and support the squad features. Profile information and pending changes may also be cached on your device to support interrupted or offline use.
2. Optional Apple Health access
With permission, the app requests access to heart rate, resting heart rate, active energy, cycling distance, cycling power, and cycling workouts. It also requests permission to write completed rides as workouts.
Data read directly from Apple Health is handled on your device, not uploaded to our servers or used for advertising. This is separate from the Bluetooth ride summaries described below. Apple Health access is optional, and you can change permissions in the Health app or iOS Health privacy settings.
Workouts already written to Apple Health remain under your control in Health, including after account deletion.
3. Ride and Bluetooth sensor data
The app receives live power, heart rate, and cadence readings from compatible Bluetooth sensors you connect. Completed ride summaries can include start and end times, average power, average heart rate, average cadence, distance where available, and ride mode.
Ride summaries are saved locally first and backed up to your account in Supabase when a connection is available. Rider profiles, FTP test records, and ride summaries support progress tracking. The app’s squad features allow invited squadmates to view shared profile and ride information.
4. Location and ride weather
If you allow location access, the app requests your location while in use and sends coordinates to the Open-Meteo forecast API to obtain current conditions. Coordinates are formatted to four decimal places for the request. The app does not maintain a location-history database. Weather responses are temporarily cached on your device.
Open-Meteo receives the coordinates and normal network request information. The current weather feature uses Open-Meteo, not Apple WeatherKit. You can revoke location permission in iOS Settings.
5. Microphone and Team Radio
Team Radio records short voice clips when you use the push-to-talk control and allow microphone access. Clips are stored in Supabase Storage, with sender identifiers, timestamps, duration, and clip references stored for delivery to squadmates. Temporary local recordings support upload and retry behavior.
Do not include sensitive information in shared voice clips. Microphone access is optional and can be revoked in iOS Settings.
6. Coach voice generation
To generate selected coach voices, the app sends coaching text and a voice identifier through our backend to ElevenLabs. The request does not include your account name, email, or location, and it does not upload your Apple Health records. The app can also use on-device system speech as a fallback.
7. Purchases and subscriptions
Apple processes App Store payments. We do not receive your payment-card details. RevenueCat processes an app user identifier and purchase and subscription information so the app can determine access to paid features. Manage or cancel subscriptions through your Apple account. Deleting an app account does not cancel an App Store subscription.
8. Service providers and security
The app uses Apple for authentication, Health, and payments; Supabase for account data, profile and ride storage, squad connections, and Team Radio; RevenueCat for purchase status; ElevenLabs for generated coach audio; and Open-Meteo for weather requests.
Network requests use encrypted HTTPS connections. Access to account data is subject to authentication and database access controls. No system can guarantee absolute security. We do not sell personal information or use Health data for advertising, and the app does not include advertising or cross-app tracking integrations.
9. Retention and deletion
Account, profile, ride history, FTP test, squad, and Team Radio data is retained to provide your account features. You can initiate account deletion in the app under Settings → Account → Delete Account. If deletion does not complete, or you want to request access to your information, contact [email protected].
Deletion of your app account is separate from Apple Health records and App Store subscriptions. Local caches, operational records, or provider backups may be subject to their own retention and removal processes. We do not promise an instant deletion deadline for every provider copy.
10. This website
This is a static marketing website. It does not include analytics, advertising pixels, third-party embeds, account registration, or an email-capture form. It does not read your app account or Apple Health data. The hosting service may process normal request information, such as IP addresses and browser details, to deliver and secure the site.
If you email support, your email provider and our email provider process the message and the contact details you choose to send.
11. Children and policy changes
The app is not directed at children under 13, and we do not knowingly collect their personal information. Contact us if you believe a child has provided information. This policy will be updated when the app’s data practices materially change.
12. Contact
Brick Outdoor Living, Inc.
[email protected]