Privacy Policy
Last updated: May 16, 2026
Cranq is designed to work without creating an account and without collecting personal data beyond what is described below. This policy explains what data is handled and where it is stored.
App data — stored locally on your device
Bike setup and pressure-calculation preferences you enter are stored locally on your device only using Ionic Storage (IndexedDB on supported platforms). Cranq does not transmit your bike or pressure data to any server.
- No user accounts.
- No login required.
- No personal data collected or stored by Cranq servers.
Analytics and crash reporting
Cranq uses Firebase Analytics to collect product usage events (for example: onboarding completion, pressure calculations, and bike profile creation) so we can understand feature adoption and improve the app.
Cranq uses Firebase Crashlytics to collect crash diagnostics and technical device/app metadata needed to detect, investigate, and fix stability issues. Analytics and crash data are processed in aggregate and are not linked to personal identities.
Strava integration
Cranq offers an optional Strava connection to automatically track bike mileage and import your gear. Connecting Strava is entirely voluntary. If you choose to connect, the following applies.
What data is accessed
When you authorise Cranq to connect to your Strava account, Cranq accesses the following data via the Strava API — read-only:
- Profile: your Strava display name and numeric athlete ID (used to match incoming ride events to your account).
- Activity summaries: distance (km), duration (seconds), date, and activity type for each ride. GPS tracks, photos, segment data, heart rate, and power data are never fetched or stored.
- Bikes & gear: the names and Strava IDs of bikes linked to your Strava account, used to route synced rides to the correct bike in Cranq.
How it is used
Ride summaries are stored in Cranq's servers solely to update your bike's odometer and maintenance component counters. Strava data is never combined with other data, shared with third parties, used for advertising, or used for AI/ML training.
Strava may collect and use data related to API access to your account in accordance with Strava's Privacy Policy.
How to withdraw consent
You can disconnect Strava at any time inside the Cranq app: Settings → Strava → Disconnect. You can also revoke Cranq's access directly from your Strava account at strava.com/settings/apps.
Revoking access on the Strava side will automatically trigger deletion of your Strava tokens, gear mappings, routing rules, and all synced ride summaries from Cranq's servers within minutes.
How to request deletion of your data
When you disconnect Strava in the app, Cranq permanently removes all Strava-sourced ride summaries from Cranq's servers immediately.
You may also request full data deletion at any time by emailing cranq.team@gmail.com. Requests are processed within 30 days in accordance with GDPR Article 17 (Right to Erasure).
Data retention
Synced ride summaries are retained only while Strava remains connected, unless you manually delete individual rides earlier. If Strava sends a ride-deletion webhook event, the corresponding ride is removed from Cranq within 48 hours. OAuth tokens are refreshed automatically and deleted immediately upon disconnection.
Third-party sharing
Cranq does not sell or share your data with third parties beyond Google's Firebase platform (Analytics and Crashlytics), which is subject to Google's Privacy Policy.
GDPR and CCPA
Your bike and preference data is stored only on your device. You can remove it at any time by clearing app storage or uninstalling the app. To opt out of Firebase Analytics on a mobile device, use your device's standard opt-out mechanism in system settings. For Strava-connected data, see the deletion options described above.
Contact
Questions about this policy: cranq.team@gmail.com.