Live Ride
1. Overview
Live Ride stores ride history locally and requires no rider account. Optional feature counts help us improve the app; online services support maps, routing, weather and purchases. This policy explains those separate data flows. Live Ride is developed by FloHub. There are no subscriptions or advertising profiles.
2. Information excluded from feature analytics
Feature reports do not include your name, email, advertising identifiers, recorded routes, GPS coordinates, ride measurements, health readings, searches, names you enter or a persistent analytics identifier. Purchase processing is separate and can involve a persistent customer identifier.
3. Information stored on your device
Rides, recorded GPS points, routes, bikes, dashboard presets and settings are stored locally using platform storage. Route naming assistance on supported Apple devices runs on-device, with an offline fallback. We do not receive your recorded ride history through analytics.
4. Location and online services
GPS supports ride recording, including background recording. On Apple Watch, the watch's GPS is used when you record a ride without your iPhone. Location permissions can be changed in device Settings, on the iPhone and on the watch. Weather requests send coordinates to Open-Meteo to fetch conditions. Current app versions send five decimal places; this is precise location, not coarse location. Apple map, search and routing services are used on iOS. Android uses OpenFreeMap map tiles, system geocoding and the project-osrm.org routing service, which receives route endpoints. Map tile requests can reveal the viewed area. These services receive network connection information such as IP addresses and handle requests under their own practices.
5. Health integrations
Apple Health and Android Health Connect integrations are optional and off by default. With permission, Live Ride saves workouts and can read heart-rate samples associated with rides. Feature analytics does not receive health values or workout content. Revoke permissions through the corresponding Health application or device settings.
The Apple Watch app runs a workout during rides so it can measure heart rate, and reads cadence and power from cycling sensors paired with your watch. It asks for Health permission on the watch the first time. These readings go from your watch to Live Ride on your iPhone over Apple's watch connection and are stored with the ride on your device; they are not sent to us. The watch's own workout is discarded at the end of each ride rather than saved to Health. Rides recorded on the watch alone are stored on the watch until they transfer to your iPhone.
6. Purchases and payment data
One-time purchases are processed by Apple App Store or Google Play. RevenueCat supports purchase validation, entitlement management, purchase support and paywall delivery. It processes purchase information and a generated customer identifier, even when no rider account is created. The support ID shown in the app can help locate purchase records. We do not receive payment card details or store account passwords. We do not attach the RevenueCat identifier to feature-count reports.
7. Storage and security
Ride history is stored on-device. Device/operating-system backups may include locally stored app data according to your settings. Android excludes analytics buffers and retry tokens from system backup and transfer. We use HTTPS for feature reports and restrict the developer dashboard with authentication. Network and hosting providers process connection metadata to deliver and secure requests.
8. Sharing you control
GPX exports, full backups and images you share can contain personal ride information. Files exported to other applications or storage services are handled under those services' practices and remain until you delete them there. Anyone with access to a full backup can inspect its contents.
9. Feature counts and service providers
Help improve Live Ride is on by default and can be switched off in Settings. The app displays an introductory notice before uploading. Approved actions are counted locally, including dashboard tile types present at ride start, tile additions/removals, ride-save milestones, navigation, route planning, GPX tools, statistics and paywall views. Reports include platform, app release and a new random batch token used to prevent duplicate processing. They contain no persistent analytics ID. Vercel receives reports and the application merges counts into weekly totals stored in Upstash Redis. Individual report payloads are not retained by our application. Hosting and network providers may retain connection/security metadata under their own policies. These services may process information outside Australia; consult Vercel and Upstash documentation for hosting regions and privacy practices. Online feature providers include Apple, Google, RevenueCat, Open-Meteo, OpenFreeMap and the OSRM routing service. No feature report is used for targeted advertising or linked to purchase customer records.
10. Children's privacy
The app is not specifically directed at children. We do not request a rider account or identifying profile. Contact us if you have a concern about information handled through support or third-party services.
11. Retention and deletion
Local ride data remains until deleted within the app or removed with the app, subject to device backups, exports and operating-system behaviour. Turning feature sharing off clears unsent counts and stops further collection/upload attempts; a report already received cannot be recalled. Device retry batches expire after seven days; server retry-token hashes expire after 14 days. Weekly aggregate counters expire after 365 days. Merged totals cannot be attributed to an individual for deletion. Purchase providers and hosting providers apply their own retention policies.
12. Your choices and requests
You can disable feature sharing, revoke location/health permissions, and export or delete local rides. Rider identity is not included in feature totals, so we cannot locate an individual's contribution within merged counts. Contact us about privacy requests, purchase/support information or complaints. The absence of a rider login does not remove applicable privacy rights.
13. International processing
External service providers may process purchase, connection, routing, weather or analytics information in countries other than your own. Applicable rights depend on your location and the information involved. Contact us for information about the providers and arrangements relevant to your request.
14. Policy changes
Material changes to data handling will be reflected here with an updated effective date and surfaced within the app where appropriate.
15. Contact
Privacy questions, requests and complaints can be sent to liveride@flohub.xyz.