Privacy

Your rides and Apple Health

Bonked stores ride records, routes, preferences, and connected-sensor information on your device. A ride can include time, distance, speed, elevation, calories, location, heart rate, cadence, and power, depending on the permissions and sensors you use. Location and Bluetooth can continue during an active ride while your phone is locked or another app is open.

With your permission, Bonked reads cycling workouts, routes, and relevant measurements from Apple Health to show history and personalize estimates. These can include heart rate, resting heart rate, weight, age, and cycling metrics. Bonked can save cycling workouts, routes, recorded measurements, and weight changes to Apple Health. You choose which Health data to allow and can change access in Apple's settings. Bonked does not use Health data for advertising or feature analytics.

If you enable Apple Watch in Bonked's iPhone Sensors settings, the Watch companion requests Health access to heart rate and workouts. During an active iPhone ride it uses a HealthKit workout session to collect heart rate and sends readings to the paired iPhone through Apple's workout mirroring connection. Bonked can include those readings in the ride record, FIT file, and Apple Health workout you choose to save, and in uploads or group heart-rate sharing you enable. The Watch also receives ride state and workout cues from iPhone and sends pause and resume commands. Rides start and save on iPhone; Bonked discards its temporary Watch workout rather than saving a second workout. Review the Watch's Health permissions in its Settings app.

FIT exports and iCloud ride backups can contain ride measurements and route coordinates. Files you share go to the destination you choose. Copies in your iCloud account are handled by Apple and your iCloud settings; removing the app does not remove those copies.

Maps, search, navigation, and weather

Bonked uses Mapbox for maps, destination search, and navigation, and Apple WeatherKit for weather. Requests can include the location, search terms, or route information needed for the feature. Mapbox also processes identifiers, precise and approximate location, search history, usage, performance, and diagnostic data for service operation, analytics, and search personalization. These mapping-service practices are separate from Bonked's optional feature-usage switch.

See Mapbox's privacy policy and Apple's privacy policy for their handling and retention of service data. Downloaded map resources are stored on your device and can be removed in Bonked.

Group rides

Group rides are social, with each rider recording and saving their own ride independently. When you create or join a group, Bonked sends the chosen group and rider names, membership identifiers, and live ride statistics through our Cloudflare-hosted service to other members of that room. Heart-rate and location sharing are optional. Group members can see the information you share; Bonked cannot remove screenshots or copies they make.

Leaving stops your participation. Group rooms expire 24 hours after creation, and the service schedules deletion of room data at expiry. This is separate from your own saved ride. Cloudflare also processes network requests to provide and protect the service.

Spectator live-ride links

Location sharing starts only when you choose Start sharing location during a ride. Bonked sends the latest available coordinates, riding or paused status, and update times to a separate Cloudflare-hosted sharing session. Anyone with the complete link can open it in a browser without an app, account, or group membership, and can pass the link to others. Viewers can see the latest shared location on a Mapbox map, ride status, last update time, and link expiry. The link does not show your name, health measurements, or full recorded route. Displaying the map sends the shared coordinates and the viewer's network request to Mapbox.

Stop sharing, saving, or discarding the ride stops new location updates and asks the server to disable the link. Pausing a ride does not turn sharing off. Once the server confirms the stop or end, it removes the stored location sample and the link can no longer retrieve it. If your phone is offline, the stop remains pending and retries; the last shared location may remain viewable until the server confirms or the link expires. Relaunching Bonked does not automatically resume sharing; it attempts to stop the earlier link. Updates depend on connectivity and iPhone background availability, so a stale location is not a guarantee of the rider's whereabouts. This is not an emergency monitoring service.

A session expires within six hours of starting sharing. Each accepted update replaces the previous sample; the service does not keep a route history for the link. After a confirmed stop or end, session identifiers, hashed sharing credentials, timestamps, and stopped or ended status remain until the original expiry to prevent the link from being reactivated. At expiry, access is refused and a server alarm is scheduled to delete the session data; this is not a promise of deletion from every infrastructure log or backup at that instant. Cloudflare and Mapbox apply their own infrastructure and service retention practices. Bonked cannot remove screenshots or copies made by viewers. Stopping a link does not delete your saved ride, FIT exports, iCloud backups, or activities already uploaded elsewhere.

Strava and Intervals.icu

Connecting either service is optional. Authorization runs through the provider, and Bonked's Cloudflare-hosted API handles authorization exchanges. Authorized FIT uploads go directly from your iPhone to Strava or Intervals.icu. Connection credentials are stored in the iPhone Keychain. Completed FIT uploads may contain precise location, heart rate, and other ride measurements. Automatic upload is a separate setting; you can also choose individual rides to upload.

Disconnecting stops Bonked's future use of that connection. It does not delete activities already uploaded. Manage those copies and access in Strava or Intervals.icu. A failed revocation may require you to remove Bonked's access in the provider's settings, as explained in the app.

Optional feature analytics

Share feature usage is off unless you explicitly enable it in setup or Settings. When enabled, Bonked sends a limited set of feature names, actions, outcomes, app-version information, and coarse timing categories to PostHog in the United States. A random, resettable installation identifier links these events across launches. This is not a promise that the events are anonymous.

These events do not contain your name, email, account identifiers, location, routes, health measurements, sensor identifiers, or free-text content. Bonked does not send screen recordings or session replay. The receiving project is configured to discard client IP addresses from stored events, and Bonked disables location enrichment for its events. Like any network provider, PostHog receives the connection IP while processing a request.

Turning sharing off stops future delivery and removes the local queue and analytics identifier. Resetting the identifier starts a new usage history. Neither action deletes events already accepted by PostHog. Unsent local events expire after 14 days. We do not currently apply a fixed automatic deletion schedule to accepted feature-usage events; they remain subject to our deletion requests and PostHog's service retention. See PostHog's privacy policy.

Optional live app presence

Live app presence is a separate, off-by-default setting. If enabled, Cloudflare receives a temporary foreground session and updates about once a minute to count open app sessions. It does not include names, locations, routes, health readings, or recording status. Background recording does not count as an open app. Turning it off stops updates; an earlier session may remain in the live count for up to three minutes. That counting window is not a statement about infrastructure-log retention.

Bonked Plus and support

Apple processes subscription payments. Bonked uses verified StoreKit purchase information to determine Plus access and restore purchases. We do not receive your payment-card details. Manage subscriptions in your Apple account settings.

If you contact support, we receive your message, return address, and any information or attachments you choose to send. Email to support@bonked.co is received through Apple iCloud Mail and forwarded to Freshdesk (Freshworks) to create support tickets and send replies. Please avoid sending health records, ride files, or precise locations unless they are needed for your request. Support correspondence is retained to handle your request and follow-up; there is currently no fixed automatic deletion schedule for support correspondence. Apple and Freshworks also handle service data under their own policies. See Freshworks’ privacy notice.

Service providers and security

We do not sell your personal information or use it for cross-app advertising tracking. Apple, Mapbox, Cloudflare, PostHog, and Freshworks process information for the features described above. We require providers handling information on our behalf to protect it consistently with this policy and Apple's applicable privacy requirements. Services you connect or share to receive the information you authorize. We may also disclose information when required by law. Provider processing can occur outside your country; Bonked's feature analytics uses PostHog's US service.

Bonked uses encrypted network connections and the iPhone Keychain for connection credentials. No storage or transmission method can guarantee complete security. Service-provider infrastructure and security logs follow the provider's retention practices; the app's sharing switches do not delete those logs. See Cloudflare's privacy policy.

Your choices and deletion requests

Change feature analytics and live app presence in Settings. Manage Health, Location, and Bluetooth permissions in iOS, and Health permissions on Apple Watch. Stop spectator sharing in the Ride link screen; the pending-stop behavior and expiry are described above. Delete saved rides in History; the deletion options identify whether to also remove Bonked-owned Health data and iCloud backups. Deleting a ride in Bonked does not delete previously uploaded activities from connected services.

To ask about access, correction, or deletion of information held by Bonked, contact support@bonked.co. We may need enough information to locate the relevant records and verify the request. Feature analytics does not include your name or email, so we may be unable to associate earlier events with you, especially after the installation identifier has been reset. We do not request unrelated health or location information to verify an analytics request.

Updates and contact

We update this policy when our practices change and show the revision date above. Questions about this policy can be sent to support@bonked.co.