BikingoDownload on the App Store

Privacy

Privacy Policy

Bikingo processes workouts on your device and automatically syncs your Garage when iCloud is available.

This Privacy Policy explains how Bikingo handles your data.

Updated: October 7, 2026.

Summary

  • Bikingo reads cycling workout data from Apple Health only after you grant permission.
  • Bikingo does not create an account for you.
  • Bikingo does not sell your data.
  • Bikingo processes workout details and statistics on your device.
  • When iCloud is available to Bikingo, Garage sync starts automatically and stores Garage records and bicycle photo copies in your Apple Account’s private iCloud database. Workout identifiers are included only to connect workouts to bicycles; workout details and measurements are excluded.
  • Bikingo stores processed data locally on your device so the app, widgets, and watch surfaces can load quickly.

Data Bikingo Accesses

If you choose to grant Health access, Bikingo may read:

  • cycling workouts
  • workout route data, when available from Apple Health
  • workout metrics needed to calculate cycling statistics, recaps, and Eddington Number progress

Bikingo does not write workout data back to Apple Health.

How Your Data Is Used

Bikingo uses your data to:

  • calculate your Eddington Number and next-milestone progress
  • show distance, elevation, streaks, trends, and ride history
  • generate weekly and monthly recap views
  • update widgets and Apple Watch surfaces with your latest cached stats

Data Sharing

Bikingo does not share your cycling data with third parties for advertising, profiling, or resale.

Core functionality works without a Bikingo account or a developer-operated backend. Garage sync uses Apple’s iCloud service as described below.

Garage iCloud Sync

Garage sync starts automatically when you are signed into iCloud and your Apple Account allows Bikingo to use it. There is no setup screen in Bikingo Settings. If you previously explicitly turned Garage sync off, that choice is preserved. Without available iCloud, you can continue using your local Garage; pending changes can sync when access returns. Devices using another Apple Account have a separate private Garage, and an existing installation pauses if its bound account changes.

Garage sync stores:

  • bicycles, names, ownership dates, ordering, and the default bicycle
  • maintenance components and user-entered service dates and notes
  • workshop inventory, categories, sections, notes, and quantities
  • app-managed copies of selected bicycle photos, with source metadata removed
  • links between a workout’s identifier (UUID) and a bicycle

The workout UUID is the only value read from Apple Health that Garage sync sends to iCloud. It lets another device connect an assignment to the same workout in that device’s Health library. Bikingo does not send workout dates, distances, durations, routes, heart-rate samples, other Health measurements or metadata, service mileage, or derived cycling statistics through Garage sync. Bicycle photos are separate selected images; this feature does not upload the ride photo library.

Each device calculates bicycle mileage from the workouts available locally. Apple Health and iCloud Photos have their own Apple-controlled sync settings, independent of Bikingo’s Garage sync.

Garage data is stored in a private CloudKit database belonging to your Apple Account, rather than a shared public database. We do not operate a server that receives your Garage content or access other users’ private Garages. Cloud storage is subject to your iCloud availability and storage allowance.

Retention, Recovery, and Cloud Deletion

You can control whether Bikingo may use iCloud in system Settings → your name → iCloud, using its app access control when available. Preventing iCloud access keeps the local Garage and stops cloud transfers; it does not delete the copy already in iCloud. An explicit sync-off choice saved by an earlier Bikingo version is also preserved. Removing Bikingo from a device does not erase existing cloud records.

Deleting an item in Garage syncs its deletion to your other participating devices. Sync records used to prevent old devices from restoring deleted items, earlier photo copies, and retained note-conflict values can remain until the cloud Garage is erased. Local restore points can also contain earlier versions.

To erase the cloud copy while preserving your local Garage, first prevent Bikingo from using iCloud on every participating device. Keep that access disabled after deletion. Then open your device’s Settings → your name → iCloud → Storage (or Manage Account Storage). If a Bikingo app-data entry is available, use its data-deletion control. The Backups section manages device backups and is separate from the Garage’s CloudKit data. If the app-data control is unavailable, contact hello@bikingo.app for guidance; we cannot access or delete your private database on your behalf.

Keep iCloud access disabled for Bikingo after cloud deletion. The current version preserves the local Garage and stops syncing when it detects an externally deleted cloud record or zone; it does not offer an automatic reset and upload-again workflow. Contact support before reconnecting an existing installation after deleting its cloud Garage. Cloud Garage deletion does not delete workouts from Apple Health or original images from Photos.

Garage recovery files include local service-mileage values as well as syncable records. Bikingo excludes its Garage repository, photo copies, and recovery files from automatic device backups. Recovery tools are not exposed in the release Settings screen. Contact support before attempting recovery. If you retained recovery files from earlier testing, store them in a local folder outside iCloud Drive or other cloud-synced folders, and remove copies you no longer want to retain.

Local Storage

To improve launch speed and keep widgets and watch surfaces current, Bikingo stores processed snapshots locally on device.

These cached snapshots are used only to support the app experience on your Apple devices.

Notifications

If you allow notifications, Bikingo may schedule local reminders and ride-related notifications on your device.

These notifications are delivered locally and are used to support the app experience.

Third-Party Analytics

Based on the current app implementation, Bikingo does not include third-party analytics or advertising SDKs in the core product flow described here.

Your Choices

You can:

  • deny Health access
  • revoke Health access later in Apple Health settings
  • use Garage locally when iCloud is unavailable
  • control Bikingo’s iCloud access through system Settings
  • erase Garage data from iCloud separately from your local Garage, as described above
  • remove local recovery copies you previously exported
  • remove the app from your device

If Health access is denied or revoked, Bikingo may show empty states or limited functionality because cycling data is required for the app’s main features.

Children’s Privacy

Bikingo is not designed specifically for children.

Changes to This Policy

This Privacy Policy may be updated over time as Bikingo evolves. When it changes, the version published on this page should be treated as the current version.

Contact

For privacy questions, contact: hello@bikingo.app