Privacy Policy

Effective date: 16 October 2026

This policy explains what personal data the JP Cycling app (the "App") and the jpcycling.app website collect, why we collect it, who processes it on our behalf, how long we keep it, and the choices and rights you have.

Who we are

JP Cycling is published by Kozio Digital, Inc, a company based in the United States, which is the data controller responsible for your personal data.

For any privacy question or request, email support@jpcycling.app.

Summary

  • You can use the App without an account. Your workouts, rides and settings are stored on your device.
  • If you create an account, we store your sign-in identity and a small set of training preferences in Google Firebase so they sync across your devices.
  • Strava upload is not yet generally available. If you connect Strava, your Strava access tokens are stored on our servers so our backend can upload rides for you. Your Intervals.icu API key stays on your device.
  • We collect crash reports through Firebase Crashlytics (you can turn this off). Public App Store and Google Play builds do not upload any other diagnostic logs.
  • We do not sell your personal data, show ads, or use advertising trackers.

Data stored only on your device

Your workouts, ride recordings (power, cadence, heart rate, speed, duration and the workout you rode), ride history, Workout Builder library, paired-device names and app settings are kept in a local database on your device. Apart from the preferences you sync when signed in, the ride files you choose to upload to Strava, and — in internal test builds only — diagnostic logs (all described below), this data is not uploaded to us.

When you export a ride as a FIT file, the file is created on your device and goes only where you choose to send it, for example through the system share sheet. Uninstalling the App deletes this local data from your device. If your phone backs up app data — Google backup on Android, or iCloud or computer backups on iPhone — the operating system may include the App's local data in that backup. Those backups are stored by Google or Apple under their own privacy policies and can restore the data if you reinstall; you can manage or delete them in your device or account settings.

Account and settings sync

Creating an account is optional. You can sign in with Apple, Google, or an email address and password. Sign-in is handled by Firebase Authentication (Google). We receive your email address, a unique user ID and, if your sign-in provider shares them, your name and profile photo URL. If you use Sign in with Apple's "Hide My Email", we receive only a relay address.

While you are signed in, these preferences are stored in Cloud Firestore so they follow you across devices: your FTP, W′ (anaerobic capacity), body weight if you entered it, ERG tolerance, ride-player display options (graphs and power smoothing) and trainer intensity-step settings. Your rides and workouts are not synced to our servers.

Strava

Strava upload is not part of the launch release; it is awaiting approval from Strava. This section describes how the integration works if it is available to you and you choose to connect it.

Strava upload is optional. When you connect Strava, you authorize JP Cycling on Strava's own website. Your Strava access and refresh tokens are then stored in our Firebase backend, in a location that neither the App nor any other user can read, and are used only by our backend to upload the rides you send (or have chosen to upload automatically).

We also store your Strava athlete ID, username, first and last name and profile-picture link to show the connection in the App, plus a record of each upload (ride ID, upload status and the resulting Strava activity ID). To upload a ride, the App sends the ride's FIT file to our backend, which forwards it to Strava; we do not keep a copy of the file.

Disconnecting Strava deletes the stored tokens and asks Strava to revoke JP Cycling's access. To be sure access has ended, you can also remove JP Cycling under Settings → My Apps on the Strava website. Data you upload to Strava is governed by Strava's privacy policy.

Intervals.icu

If you connect Intervals.icu, your API key is stored only on your device, in encrypted secure storage (iOS Keychain or Android Keystore), and your Intervals.icu athlete ID is kept in the App's local database. The App talks to Intervals.icu directly to import planned workouts and upload completed rides; this traffic does not pass through our servers. Disconnecting removes the key from your device. Data you upload to Intervals.icu is governed by its own privacy policy.

Subscriptions and purchases

Subscriptions are sold and billed by Apple (App Store) or Google (Google Play). We never receive your payment card details.

We use RevenueCat to validate purchases and keep track of your subscription status. RevenueCat receives purchase and transaction information from the store, an app user ID, and basic device and app information such as platform, app version and store country. When you sign in, your RevenueCat app user ID is set to your JP Cycling account ID so your subscription follows your account. RevenueCat notifies our backend of subscription changes, and we store your current subscription status (product, active/expired and expiry date) in Firestore.

Apple Health and Health Connect

If you choose to pair an Apple Watch or a Wear OS watch, the App asks for permission to read data from Apple Health (iOS) or Health Connect (Android). On iOS the App reads heart rate and blood oxygen saturation. On Android it reads heart rate, heart rate variability, blood oxygen saturation and calories burned.

This data is used to show your live heart rate, to add it to the ride recording stored on your device and, when enough recent heart rate variability readings are available, to calculate an HRV readiness indicator on your device (today's value compared with your 14-day baseline) that the home screen shows as training guidance. It is not used for advertising or marketing and is not shared with third parties — except that the health data saved with a ride (heart rate and, where available, heart rate variability, blood oxygen saturation and calories burned) is included in the ride's FIT file when you yourself export the ride or upload it to Strava or Intervals.icu. In internal test builds with diagnostic log upload enabled, heart-rate readings and these post-ride values can also appear in the diagnostic logs sent to our backend (see Crash reports and diagnostic logs). The App does not write data to Apple Health or Health Connect. You can withdraw access at any time in the Health app or Health Connect settings.

Bluetooth and location permission

The App uses Bluetooth Low Energy to find and connect to smart trainers and heart-rate sensors. On Android 12 and later, it asks for the Nearby devices permission and declares that it does not use Bluetooth scans to determine your location.

On Android 11 and earlier, Android requires the Location permission for any Bluetooth scan. The App uses that permission only to scan for your devices; it never reads, stores or sends your location.

Crash reports and diagnostic logs

Crash reports: the App uses Firebase Crashlytics (Google). When the App crashes or hits a serious error, Crashlytics collects a stack trace, the device model and operating-system version, the app version, app state such as memory and disk usage, and a Crashlytics installation identifier. For non-fatal errors only the error type and stack trace are sent, not the error message. Crash reporting is on by default; you can turn it off at any time in Settings → Privacy → Share crash reports, which also deletes any reports that haven't been sent yet.

Diagnostic logs: the App keeps a short technical log on your device to help us find and fix bugs — especially Bluetooth and trainer-control problems. Public App Store and Google Play builds do not upload this log. Only internal test builds (for example, TestFlight builds for invited testers) upload it, to our own backend in our Firebase project, and only while you are signed in. Logs contain timestamps, the log level, the screen that was open, app version and platform, error messages and stack traces, and descriptions of app events such as connecting to a trainer, changes to the ERG target, workout progress and the results of sync or upload attempts. They may contain technical identifiers such as the Bluetooth names of your devices, heart-rate readings from a connected sensor, and post-ride summary values from a paired watch (heart rate variability, blood oxygen saturation and calories burned). Before logs are stored, our backend removes email addresses, tokens and other secrets and does not record your IP address. Each log entry is tagged with a shortened one-way hash of your account user ID, but some log messages can still contain the user ID itself.

Our website

The jpcycling.app website is a static site hosted by Cloudflare, Inc. When you visit it, Cloudflare processes technical request data — such as your IP address, browser user agent, the page requested and your browser's language preference (used to send you to a page in your language) — to deliver and protect the site. The website has no analytics, advertising or tracking cookies; it only saves your light/dark theme choice in your browser's local storage.

Why we use your data (legal bases)

Where the EU or UK GDPR applies, we rely on the following legal bases:

  • To provide the App and the features you ask for — your account, settings sync, Strava and Intervals.icu connections and ride uploads: performance of our contract with you (Art. 6(1)(b) GDPR).
  • To validate purchases and manage subscriptions: performance of a contract, and compliance with legal obligations for transaction records (Art. 6(1)(b) and (c)).
  • To keep the App stable and secure through crash reports and diagnostic logs: our legitimate interest in providing a reliable service (Art. 6(1)(f)). You can opt out of crash reports in Settings → Privacy → Share crash reports.
  • To read heart-rate and related health data from Apple Health or Health Connect and use it for live heart rate, your ride recordings and the on-device HRV readiness indicator: your explicit consent, given through the system permission prompt (Art. 9(2)(a)). You can withdraw it at any time in your device settings.
  • To answer your support requests: performance of a contract or our legitimate interest in helping you.

Who processes your data

We use the following service providers, which process data on our behalf under contracts that require them to protect it:

  • Google LLC — Firebase Authentication, Cloud Firestore, Cloud Functions, Cloud Logging and Firebase Crashlytics (sign-in, settings sync, our backend, diagnostic logs and crash reports).
  • Cloudflare, Inc. — hosting and delivery of the jpcycling.app website.
  • RevenueCat, Inc. — subscription and purchase management.
  • Apple and Google — app distribution, payments, Sign in with Apple and Google Sign-In, under their own privacy policies.
  • Strava and Intervals.icu — only if you connect them. They receive the rides you choose to upload and handle that data as independent controllers under their own privacy policies.

No sale of personal data

We do not sell your personal data and do not share it for cross-context behavioral advertising. We do not use your data, including health data, for advertising, and we do not use it to build profiles for third parties.

International transfers

Our backend runs on Google Cloud in the United States, and RevenueCat processes data in the United States. When personal data from the European Economic Area, the United Kingdom or Switzerland is transferred to the United States, we rely on the EU–US Data Privacy Framework (and its UK and Swiss extensions) where the recipient is certified, and on the European Commission's Standard Contractual Clauses (with the UK Addendum where applicable).

How long we keep your data

  • Data on your device: until you delete it or uninstall the App.
  • Your account, synced preferences, Strava connection and upload records, and subscription status: until you delete your account.
  • A minimal deletion record (your account user ID and the time of deletion): kept after you delete your account so that a late subscription event from the store cannot recreate your data.
  • Crash reports: kept by Firebase Crashlytics for 90 days.
  • Diagnostic logs: kept for 30 days in Google Cloud Logging, then deleted automatically.
  • Support emails: for as long as needed to handle your request and any follow-up.
  • Website request data: processed by Cloudflare to serve and protect the site; we do not keep our own website logs or analytics.
  • Security records: Strava connection state records expire after about 10 minutes and rate-limit counters (keyed by user ID or IP address) cover only short time windows; expired records are deleted by an automatic expiry policy on our database.
  • Purchase records: kept by Apple, Google and RevenueCat under their own policies and legal obligations, such as tax law.

Your rights

If you are in the EEA, the UK or Switzerland, you have the right to access your personal data, correct it, delete it, restrict or object to its processing, receive it in a portable format, and withdraw consent at any time (without affecting earlier processing). You also have the right to complain to your local data protection authority — in the UK, the Information Commissioner's Office (ICO).

If you are a California resident, the CCPA/CPRA gives you the right to know what personal information we collect and how we use and disclose it, to access, correct and delete it, to opt out of its sale or sharing (we do not sell or share it), and to limit the use of sensitive personal information (we use it only to provide the App). We will not discriminate against you for exercising these rights. You may also use an authorized agent.

To exercise any right, email support@jpcycling.app from the email address linked to your account. We may ask for information to verify your identity, and we will respond within one month (GDPR) or 45 days (CCPA), as required by law.

Deleting your account

You can delete your account at any time in the App under Settings → Account & Sync → Delete account, or by emailing us. Deletion permanently removes your sign-in account and the data stored on our servers for it, except a minimal deletion record (your user ID and the time of deletion) described under retention. If the App reports that the server cleanup didn't finish, email us and we will complete the deletion.

How to delete your account

Children

The App is not directed to children under 13, or under 16 in the EEA and UK where local law sets a higher age. We do not knowingly collect personal data from children. If you believe a child has given us personal data, contact us and we will delete it.

Security

Data is encrypted in transit with TLS. Our database security rules let each signed-in user access only their own data, and Strava tokens can be read only by our backend. To protect our backend from abuse, the App uses Firebase App Check (Apple App Attest or DeviceCheck on iOS, Google Play Integrity on Android) to confirm that requests come from the genuine App, and our backend keeps short-lived rate-limit counters keyed by your user ID or IP address, plus short-lived state records while you connect Strava. No method of transmission or storage is completely secure, but we work to protect your data and limit what we collect.

Changes to this policy

We may update this policy from time to time. We will change the effective date above and, for material changes, tell you in the App or on this website before they take effect.

Contact

Questions or requests about your privacy? Email support@jpcycling.app