Privacy Policy
Haptics collects the minimum data needed to provide its features. Your ride data and AI Coach conversations are synced to Google Firebase so they work across your devices. We do not sell your data, show ads, or share your data with third parties except as described below.
Haptics is available on iPhone, Apple Watch, Android, Wear OS, and Garmin devices. This policy covers all platforms.
What we collect and why
Account information
Haptics offers two sign-in options:
Sign in with Apple. Apple provides a one-time name and an optional private relay email address. Your name is displayed within the app but is never transmitted to our servers or stored in our database. If you choose to hide your email, Apple provides a private relay address instead; we never see your real email.
Sign in with Google. Google provides your name and email address to Firebase Authentication (Google's own infrastructure). Your name is displayed within the app but is never written to our database. Your email is held by Firebase Authentication for account management purposes only.
In both cases, your account is identified in our database solely by an opaque Firebase-generated UID (e.g. vK9mX3pQr2...), never by your name or email.
You may also use the app without signing in (anonymous mode), in which case no identifying information is collected.
Ride and training data
Completed rides, imported routes, indoor workout records, and app settings (FTP, power zones, heart rate zones, weight, emergency contact) are stored in Google Firestore under your account. This enables cross-device sync and powers AI Coach analysis.
AI Coach conversations
Messages you send to the AI Coach are transmitted to our Firebase Cloud Functions backend, which forwards them to Anthropic's Claude API for processing. Your conversation history is stored in Firestore under your account so the AI Coach can maintain context across sessions.
Anthropic does not use API inputs or outputs to train its models. See Anthropic's privacy policy.
Real-time AI coaching during rides
When the AI Cadence Coach or mid-ride coaching features are active, anonymised ride telemetry — including cadence history (steps or revolutions per minute), heart rate, road grade, and elapsed time — is sent to our Firebase Cloud Functions backend approximately every 45 seconds. This data is forwarded to Anthropic's Claude API to generate real-time coaching cues and cadence target adjustments. This telemetry is not stored after the coaching response is returned.
Rider memory
The AI Coach extracts a short summary of your training profile (fitness level, goals, preferences across cycling, running, and swimming) from your conversations and stores it in Firestore. This is used to personalize future coaching responses. You can view and delete this in Settings.
Where your data lives
| Data | Where |
|---|---|
| Live location during a ride | On-device only, never transmitted |
| Heart rate (Apple Watch / Wear OS) | On-device during the ride; saved into completed ride records in Firestore |
| Cadence (BLE sensor / Garmin / Wear OS) | On-device during the ride; saved into completed ride records in Firestore |
| Samsung Health ride data | Synced to Firestore under your account on Samsung devices |
| Strava / Ride with GPS OAuth tokens | Stored securely server-side in Firestore (never your password) |
Third-party services
Google Firebase (Auth + Firestore + Cloud Functions)
Your account data, ride history, AI Coach conversations, and rider memory are stored in Google Firebase. Google's privacy policy.
Anthropic (AI Coach)
AI Coach messages are processed by Anthropic's Claude API. Anthropic does not use your messages to train AI models. Anthropic's privacy policy.
RevenueCat (Subscriptions)
Subscription purchases are managed by RevenueCat. RevenueCat receives your App Store transaction data (product ID, purchase date, expiry) to verify entitlements. We never see your payment information. RevenueCat's privacy policy.
Meta (Advertising measurement)
To understand which of our advertising campaigns are effective, we use Meta's advertising tools:
- Marketing website: our website uses the Meta Pixel to record page views and clicks on the App Store / Google Play download buttons.
- Subscriptions: when you start or renew a subscription, RevenueCat forwards limited purchase information (such as product and date) to Meta on our behalf, so we can measure at an aggregate level how many subscriptions our campaigns generate. No payment information is shared.
The Haptics app itself does not use the advertising identifier (IDFA) and does not track you across other apps or websites. The subscription measurement above is performed server-to-server and is not tied to a device identifier, and we do not show ads inside the app.
Our marketing website uses cookies for the Meta Pixel. Where required by law (for example, for visitors in the EEA and UK), we ask for your consent before these cookies are set. Meta's privacy policy.
Apple StoreKit (In-App Purchases)
All payment processing is handled by Apple. Apple's privacy policy.
Strava (optional, user-initiated)
If you connect Strava, Haptics exchanges the OAuth authorisation for an access token, which is stored securely server-side in Firestore under your account and used solely to upload completed rides from Haptics to your Strava account. We never import activity data from Strava, and we never see or store your Strava password.
Ride data analyzed by the AI Coach comes exclusively from Haptics' own on-device recording, not from data retrieved via Strava's API. This is consistent with Strava's API agreement, which prohibits the use of Strava-sourced data in AI or machine-learning models. Strava's privacy policy.
Ride with GPS (optional, user-initiated)
If you connect Ride with GPS to import routes, the OAuth access token is stored securely server-side in Firestore under your account and used to make API requests to api.ridewithgps.com on your behalf. Imported route data is stored under your account. We never see or store your Ride with GPS password. Ride with GPS's privacy policy.
Garmin Connect IQ (optional, paired device)
On iOS and Android, Haptics communicates with paired Garmin watches and Edge cycling computers via the Garmin Connect IQ Mobile SDK. Haptics sends route cues, coaching messages, and workout data to your Garmin device. Your Garmin device sends heart rate and cadence sensor readings back to the Haptics app during rides. This sensor data is used on-device for haptic feedback and real-time coaching, and is included in completed ride records saved to Firestore. We do not transmit this data to Garmin's servers. Garmin's privacy policy.
Samsung Health (optional, Samsung devices — Android only)
On Samsung Android devices, Haptics can sync completed rides from Samsung Health. Ride data (distance, duration, heart rate) is stored in Firestore under your account. Samsung Health's privacy policy.
Wear OS / Google Health Services (Android only)
On Android, the Haptics Wear OS app reads heart rate, distance, and calories from Google Health Services on your paired Wear OS watch during rides. This data is used on-device to display real-time metrics and is included in completed ride records saved to Firestore via your Android phone. We do not share this data with Google beyond what Health Services itself collects. Google's privacy policy.
PostHog (Product analytics)
We use PostHog to understand how the app is used (for example, which features are opened) so we can improve it. PostHog records pseudonymous in-app usage events along with basic device and app-version information, identified by a random analytics ID rather than your name or email. We do not use PostHog for advertising, and we do not sell this data. PostHog's privacy policy.
Google Analytics (Website analytics)
Our marketing website uses Google Analytics 4 to understand aggregate visitor traffic: how many people visit, which pages they view, and which countries and referral sources they come from. Google Analytics uses cookies and records pseudonymous usage data; we do not use it to identify you by name or email, and we do not use it for advertising. Where required by law (for example, for visitors in the EEA and UK), we ask for your consent before these cookies are set. Google's privacy policy.
MailerLite (Email marketing)
If you sign up for our beta waitlist or mailing list, your name and email address are stored with MailerLite, our email marketing provider. MailerLite may record whether you open an email (via an invisible tracking pixel) and whether you click links in our emails (via Google Analytics link tracking). This helps us understand which emails are useful and improve future communications. You can unsubscribe at any time using the link in any email we send. MailerLite's privacy policy.
Location data
Haptics requests "When In Use" location access to track your position along a route during a ride. Your location data is used solely on-device for navigation and haptic cues. Location is never transmitted to us or any third party.
HealthKit data (Apple Watch)
The Haptics Watch app reads heart rate from HealthKit during rides. Heart rate data is used on-device to display real-time metrics and is included in completed ride records saved to Firestore. We do not share HealthKit data with any third party.
Health Services data (Wear OS)
The Haptics Wear OS app reads heart rate, distance, and calories from Google Health Services during rides. This data is used on-device to display real-time metrics and is relayed to your paired Android phone to be saved in Firestore as part of your completed ride record. We do not share Health Services data with any third party.
Firebase Crashlytics (Crash reporting)
We use Firebase Crashlytics to collect anonymous crash reports when the app unexpectedly quits. Crashlytics captures the stack trace, device model, iOS version, and app version at the time of the crash. This data is used solely to identify and fix bugs. Crashlytics does not collect your name, email, location, or any personal identifiers. Firebase privacy policy.
Analytics and advertising
We use PostHog for product analytics to understand in-app usage (see the PostHog section above), Google Analytics to understand aggregate visitor traffic on our marketing website (see the Google Analytics section above), MailerLite to send and track our emails (see the MailerLite section above), and Meta's advertising tools to measure how well our marketing campaigns perform (see the Meta section above). We do not show ads inside the app, we do not sell your personal data, and aside from the advertising measurement described above we do not track you across unrelated apps or websites. Crash data collected by Crashlytics is used solely for debugging and is not used for advertising or profiling.
Data retention
Your Firestore data (rides, conversations, settings) is retained as long as your account exists. You can delete your account and all associated data by contacting us at the address below.
Children's privacy
Haptics is not directed at children under 13. We do not knowingly collect data from children.
Your rights
You may request access to, correction of, or deletion of your personal data at any time by contacting us. If you are in the EEA or UK, you have additional rights under GDPR, including the right to data portability and the right to lodge a complaint with your local supervisory authority.
Changes to this policy
We will update this page if our data practices change. The "Last updated" date at the top reflects the most recent revision.
Contact
Questions or data requests: support@haptics.coach