Your data / Your history

Your jumps.
Your privacy.

How your information is collected, used, stored and protected.

Last updated: 6 November 2026

BreakOff 2.1 / Private web access

The logbook is private.
The plan is checked separately.

The read-only browser preview uses Apple’s CloudKit sign-in to read the latest available publication in your own private iCloud account. The published data can include saved jump details, GPS, altitude, heart-rate and other retained readings, gear context and saved notes. It is a phone-published snapshot, not continuous live recording or a second independently edited logbook.

Your iCloud Apple Account identifies that private logbook. An App Store purchase may belong to a separate App Store account. Connecting web access in the updated iPhone app links the verified plan to the intended iCloud account; iCloud ownership alone is not proof of a paid plan. Free, Logbook and Pro determine the visible history and features.

What the access-verification service processes

A separate BreakOff service verifies account, app and purchase evidence with Apple and returns an account-bound access response. This flow processes account-scoped Apple/iCloud identifiers and authentication evidence; App Attest public-key identifiers, attestations and replay-protection counters; App Store product, app and transaction identifiers, purchase/account-link tokens, subscription status and expiry information; browser-access credentials; and limited request timing, status and abuse-prevention fingerprints. These are used to authenticate the connection, recognise the plan, prevent conflicting purchase claims and protect the service.

This plan-verification flow does not receive your jump recordings, GPS tracks, heart-rate readings, gear library or source videos. Your browser reads the published logbook from Apple’s private iCloud service. Apple-hosted sign-in handles your Apple password; do not send that password to BreakOff support.

Current verification providers and release status

The isolated Sandbox/TestFlight web preview now uses BreakOff’s existing hosting for subscription verification and its verification records. Production web verification for the public website remains disabled pending release checks. The earlier Firebase verification service is disabled, with its verification state retained for controlled rollback. This change does not affect the iPhone app’s Firebase Analytics described below or separately managed Garmin services. A test-preview connection does not activate public web access.

Sessions, exports and disconnecting access

The browser requests a short-lived verified access response. Its current private view is cleared on sign-out and account changes. The web app keeps its downloaded logbook and browser-access credential in memory rather than saving them to its own persistent browser storage. Apple’s authentication services and your browser have their own storage behavior. Files you deliberately download remain separate copies in your chosen download location.

Temporary challenges and browser credentials are subject to logical expiry checks. Expired records can remain in storage until the service’s retention and maintenance process removes eligible entries. Account-to-purchase ownership and device replay-protection records can be retained longer to prevent replay and conflicting claims. Reset web access invalidates browser credentials; it does not cancel an App Store subscription, delete your saved jumps or promise immediate deletion of every security record. Use the contact details below for a data request.

Maps and recording limits

Opening an Apple map or satellite view sends the requested map area or coordinates needed to Apple to obtain that imagery. Map imagery is a flat geographical reference, not terrain or ground-clearance evidence. Browser imports and editing are not part of this read-only release. Ordinary published logbooks do not automatically include retained original FIT files, pending recordings or linked local videos.

Your privacy choices · Contact BreakOff about web access ↗

BreakOff 2.1 / Mac + your common logbook

Your devices.
Your private record.

The Mac app stores a local review library containing the recordings, phone publications, exports and review notes you choose to use. It can read your verified iPhone logbook through your user-private iCloud/CloudKit account when both devices use the same iCloud Apple Account.

When you deliberately submit a Mac addition, edit or deletion request, the updated iPhone app validates and applies the request to the common logbook, then publishes the result. FIT additions may transfer their retained original FIT evidence and required review material through your private iCloud for iPhone processing. A pending request is separate from a completed logbook save.

Published app data can include saved gear configurations, at-use component snapshots and history; optional profile notes, coach/instructor ratings, tunnel time and licence expiry; and personal dropzone details or notes you choose to save. Mac gear review is read-only; changes are made on iPhone.

Equipment/licence-date and recency reminders are optional local notifications on iPhone. They use your saved dates, last saved jump and chosen preferences. Notification permission is requested when you deliberately choose the permission control. Notification text omits equipment names, serial numbers and jump dates.

Linked source videos and Mac video offsets remain local. Videos are not automatically uploaded or synchronized through the common logbook, and a phone media bookmark does not transfer the file. An ordinary logbook JSON/iCloud backup is not a full device or original-evidence backup. Retain important originals, pending recordings and source videos separately.

The Mac app has no Firebase or Meta analytics integration. The iPhone app’s analytics and advertising-measurement disclosures below remain applicable. Apple iCloud/CloudKit, StoreKit/App Store and map services use network services when you choose the corresponding features; BreakOff does not claim that every operation is offline.

Backup and original-evidence guide ↗

V2 / Garmin recordings and original FIT import

Your recording.
Your choice to import.

The BreakOff Garmin watch app records a Garmin fitness activity. Depending on your device, permissions and available readings, the FIT may contain timestamps, GPS coordinates, altitude, barometric pressure and heart-rate readings, plus BreakOff jump-phase markers and recording-quality information. Garmin heart-rate readings are separate from Apple Watch HealthKit access.

The activity is saved on your Garmin device. If you sync it to Garmin Connect, Garmin processes it under its own services and privacy terms. BreakOff does not control Garmin Connect’s storage or sharing settings.

Transfer into the BreakOff iPhone app is manual and initiated by you: export the original FIT and select it for import. The Garmin app does not automatically send recordings through a BreakOff-operated relay or directly to the iPhone app.

BreakOff processes the imported file to show recorded evidence and prepare a logbook entry. Nothing is added to or linked with a jump until you confirm the import decision. Original files are retained locally on the iPhone for import and review until you explicitly remove the relevant copy. Imported logbook data follows the device, iCloud/CloudKit and export settings described below.

Pending Recording Inbox imports and pending Watch recordings are separate from an iCloud logbook backup. Export retained originals and finish pending saves before deleting BreakOff or changing phones.

Imported GPS, altitude, heart rate and jump telemetry are excluded from BreakOff’s advertising and analytics event payloads and are not used for advertising. Your selected data can be included when you deliberately share or export a record. Concise analysis summaries exclude precise coordinates. Detailed exports may include precise location, depending on the format and retained evidence. Sample CSV offers an explicit GPS choice; some JSON and comparison exports can contain coordinates without a separate location toggle. Review the selected export format before sharing.

You control Garmin sensor permissions, Garmin Connect activity privacy and your retained recordings through the applicable app and device controls. Garmin recording does not require a BreakOff subscription. Reviewing and saving Garmin imports on iPhone requires Logbook or Pro; Apple processes those subscription transactions.

Recovering recordings from the earlier Garmin pilot

If you used an earlier BreakOff Garmin pilot, you can choose Garmin pilot recovery in the iPhone app. This optional recovery uses Sign in with Apple and a separate Firebase relay to verify your account and iPhone, manage existing pilot connections, and retrieve retained recording copies into Recording Inbox. A manual relay check can also send the review decision for a previously received pilot recording.

The relay can process account identifiers, device or pairing identifiers, authentication and app-verification evidence, review decisions and the recording copies retained from the pilot. Opening the app or importing an original FIT does not run a relay check. New pairing is disabled. You can revoke an earlier watch connection or request deletion of the pilot relay account in Garmin pilot recovery. Deleting that account does not remove your saved iCloud logbook or copies already in Recording Inbox.

Landing-target names and coordinates, analysis review markers and canopy history are user-selected or derived record data. They support the corresponding app features and remain subject to the storage, sharing and export choices in this policy. They are not included as sensitive telemetry in advertising events.

Your privacy

Cookie preferences

This website loads no advertising or analytics scripts. Fonts, product images and the background film are served with the site. External forms and linked services use their own privacy policies.