Ridecoon
Privacy Policy
Ridecoon is designed to work mostly on your device. It does not require an account, does not operate its own backend, and does not upload your ride history to a Ridecoon server because there is no Ridecoon server.
What Ridecoon uses
Depending on the features you use, the app may access:
- Bluetooth, to connect to a compatible trainer and optional heart-rate monitor.
- GPX files you choose to import into the app.
- Ride metrics generated during your session, such as speed, cadence, power, heart rate, distance, elapsed time, calories, and route progress.
- Map content provided by Apple Maps when route maps are displayed.
How data is used
Ridecoon uses this data only to provide app functionality, for example:
- Connecting to your trainer and reading workout telemetry.
- Importing and displaying your selected GPX route.
- Showing your live ride metrics and saving ride history on your device.
- Rendering route maps through Apple Maps.
What Ridecoon does not do
Ridecoon does not require sign-in, does not create a user account, does not have its own cloud service, and does not sell your data.
Local storage
Imported routes, saved ride history, and certain app preferences are stored locally on your device. If you delete the app, iOS may remove that locally stored app data.
Apple Maps
When the app shows maps, map data is provided by Apple Maps. Network activity related to map rendering is handled by Apple, not by a Ridecoon backend.
Your choices
You can control Bluetooth access through iOS settings, choose whether to import GPX files, and delete saved rides or routes from within the app where supported.
Changes to this policy
We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated effective date.
Contact
For questions about this policy, please use the contact details on the Support page.