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.
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.
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.
This Privacy Policy explains how BreakOff collects, uses, stores and protects information when you use the BreakOff website, website contact and feature-request forms, iPhone app, Apple Watch app, Garmin watch app, Mac app and read-only web logbook, or previously joined our launch notification list. It also reflects Firebase/Google Ads measurement added for BreakOff v1.1 and Meta App Events measurement introduced in BreakOff v1.2.1 (Build 127). It also covers the Mac review workspace, private iCloud common-logbook exchange, saved gear/component history, optional profile and dropzone details, and optional local iPhone reminders introduced in v2.1.
Important safety note: BreakOff is a skydiving jump tracker, automatic logbook and gear-management app. It is not a certified altimeter, audible altimeter, emergency device or life-saving system. Do not use BreakOff for altitude awareness or safety-critical decisions during a skydive.
1. Who we are
BreakOff is an Apple Watch-first skydiving app for licensed skydivers. It helps users track the jump cycle, build a digital logbook, manage gear information and review jump history on iPhone and Mac.
For privacy questions, contact: privacy@breakoffapp.com
2. Information we collect
Depending on which features you use, BreakOff may process the following categories of information:
Website forms, previous launch signup and contact information
- Name and email address.
- Inquiry type, feature title, app area, subject, message, suggested feature, current workaround and other information you enter into a website form.
- App version, device and operating system information you choose to provide for support.
- Files, screenshots or other attachments you choose to upload.
- Any optional fields or preferences included in a website or previous launch signup form.
- Optional email/product update consent.
- Messages, support requests or feedback you choose to send to BreakOff.
Jump and logbook data
- Jump number, date, time, drop zone, aircraft, discipline/jump type and notes.
- Exit altitude, deployment altitude, freefall time, canopy time, landing information and related jump metrics where available.
- Manual edits or corrections you make to your logbook entries.
Signing and QR sign-off data
- When an in-person sign-off is requested or applied, BreakOff may process the signer’s name, role, licence, member or certificate number, optional rating title and expiry year, comments, sign-off time and sign-off status.
- A reusable Signing Identity is stored locally on the iPhone where it is created. Its QR code contains the signer details, a locally generated identity identifier and the date the identity was last updated.
- A short-lived sign-off request QR code may contain a request identifier and the selected jumps’ internal sync identifiers, jump numbers and dates. A response QR code may contain signer details and comments.
- Request and response QR codes expire after 15 minutes.
Apple Watch and sensor-related data
- Barometer, motion and device sensor signals used to help identify jump phases and create jump records.
- Altitude, vertical movement and phase timing data generated during a tracked session.
Location data
- GPS/location data used for jump path review, map display, drop zone context, wind context and canopy/debrief features where enabled.
- BreakOff may store coordinates for saved dropzones and compare a jump’s landing coordinates with saved or previously used dropzones to offer nearby suggestions. This matching occurs on-device, and a suggestion never automatically changes the selected dropzone.
- Location permission is controlled by your device settings.
Weather and wind data
- BreakOff may request weather or wind information from OpenWeatherMap or similar weather providers to show pre-jump wind context.
- These requests may include location coordinates or a selected drop zone/location so the provider can return relevant weather data.
Gear data
Container, main canopy, reserve canopy, AAD, lineset and related gear details that you choose to enter. This includes named rig configurations, exact at-use component snapshots, earlier revisions, lifecycle events such as sale or retirement, starting/lifetime counts and known recorded uses, lineset history, reserve repack/inspection dates, AAD battery/service dates, maintenance notes and reminder settings.
Optional profile, dropzone and reminder data
Profile notes, coach/instructor ratings, tunnel time, licence expiry and personal dropzone details or notes that you explicitly save. These records are not automatically verified credentials. Local iPhone reminders use eligible saved equipment/licence dates, the last saved jump, your chosen 30/60/90-day recency interval, local reminder hour and any snooze preference. These data are not used as advertising-event content.
Mac review and common-logbook requests
Local FIT originals and prepared evidence, verified phone publications, local iPhone JSON exports, chart/replay preferences, local review annotations, linked-video references and offsets, and the additions, edits or deletion requests you deliberately submit. Request status and validation results are retained to explain whether the phone has saved and published the change.
Media data
- Photos or videos you choose to link to a jump record.
- BreakOff only accesses media that you select or allow through system permissions.
Camera and QR scanning
- BreakOff requests camera access only when you choose to scan an in-person sign-off QR code.
- QR recognition is performed on-device.
- BreakOff does not save or upload the scanner’s camera feed, photographs or video.
Subscription and purchase data
- If BreakOff offers paid features or subscriptions, purchases are processed by Apple using StoreKit and the App Store. BreakOff may receive subscription status, product identifiers, transaction identifiers, renewal status and related receipt information needed to unlock paid features and support purchases.
- Payment card details are handled by Apple, not BreakOff.
App analytics and advertising measurement data
- From BreakOff v1.1, the iPhone app may use Firebase Analytics / Google Analytics for Firebase to understand app installs, app opens, subscription purchase events, entitlement-related events, non-sensitive feature usage, campaign attribution and general app performance.
- This may include app instance identifiers, device and app information, approximate location derived from IP address, product identifiers for subscription purchases, transaction-related analytics events, and advertising or campaign identifiers where provided by Google, Apple or your device settings.
- Firebase and Google Ads measurement are used to measure campaign performance and app/subscription conversion activity. BreakOff does not use Firebase Analytics to store or transmit skydiving logbook content, signer identities, QR payloads, sign-off details, full GPS tracks, gear records, HealthKit heart-rate data, jump notes, photographs or videos.
Meta iOS SDK / Meta App Events in the iPhone app
From BreakOff v1.2.1 (Build 127), the iPhone app uses the official Meta iOS SDK / Meta App Events to measure:
- App installations and activations.
- Subscription checkout attempts.
- Eligible trial starts.
- New immediately paid subscriptions.
- Advertising campaign performance and attribution.
Depending on the event and Meta SDK processing, event information may include:
- App and device information.
- Approximate location derived from IP address.
- App-scoped or device identifiers supplied by the Meta SDK.
- The subscription product identifier and whether the plan is monthly or yearly.
- Price or value and currency.
- A transaction or order identifier used for event deduplication.
Facebook Login is not used. Beginning with BreakOff v1.2.1 (Build 128), the iPhone app requests permission through Apple's App Tracking Transparency (ATT) framework before enabling Meta advertiser-ID measurement. If you grant permission, the Meta iOS SDK may access the Identifier for Advertisers (IDFA), and BreakOff may use that identifier for advertising campaign attribution and the deliberately selected acquisition events described above. If permission is denied, restricted or not yet determined, Meta advertiser-ID collection and Meta acquisition-event reporting remain disabled. BreakOff otherwise continues to work.
Automatic StoreKit purchase logging is disabled. BreakOff sends only deliberately selected and verified acquisition events from its subscription flow. Restores, entitlement refreshes, renewals, reinstalls and Family Sharing are not reported as new subscription acquisitions.
BreakOff does not send the following information to Meta through this integration:
- Jump logs or jump telemetry.
- GPS tracks or landing coordinates.
- Barometric or altitude samples.
- HealthKit, heart-rate or workout data.
- Gear, canopy or lineset records.
- Emergency or dropzone contacts.
- User notes, signer identities, QR payloads, sign-off details, signatures, photographs or videos.
- Full iCloud backup contents.
Meta processes App Events information under its own terms and may link it with other information it holds, as described in Meta’s Privacy Policy.
Diagnostics and technical data
- Crash reports, device model, operating system version, app version and basic technical logs used to improve reliability.
Website analytics and marketing data
The current BreakOff website loads no advertising or analytics scripts. Fonts, product images and the background film are served with the site. External contact/feature-request forms and services you open have their own privacy practices. The website’s cookie-preferences control describes this current setup. This is separate from the iPhone app analytics and acquisition measurement described above.
3. How we use information
We use information to provide jump tracking, logbook, gear-management and review features; display jump history, maps, charts, wind context and optional local reminders; provide the Mac debrief, reports and user-initiated common-logbook requests; improve reliability and performance; respond to support and feedback; manage product communications; process App Store subscriptions where applicable; measure app installs, campaign performance, subscription conversion events and non-sensitive app usage; maintain security; and comply with legal obligations where required.
Personal Trends are calculated locally from existing jump records, including dropzone, canopy, owned or rental gear, heart-rate and wind information. These calculations are not transmitted to Firebase, Meta or another analytics provider as logbook content.
4. Product emails and previous launch signups
Before BreakOff launched, visitors could join a launch notification list through the website. If you joined that list, we may use the information you provided to send the App Store link, product updates and related BreakOff communications. The launch signup form is no longer active on the website.
You can unsubscribe from product update emails where an unsubscribe option is provided, or request removal by emailing privacy@breakoffapp.com.
BreakOff uses GoHighLevel and related email service infrastructure to process website contact and feature-request forms, retain previous launch signup records, manage support and feedback workflows, maintain contact lists, and send submission confirmations or permitted emails. These providers process contact data only to help us manage those communications and requests.
5. Storage and sync
BreakOff is designed with a privacy-first approach. Logbook, gear and jump data may be stored locally on your iPhone and Apple Watch. The Mac app retains a separate local review library. Where private cloud publication, backup, restore or common-logbook exchange is enabled, app data may be stored using Apple iCloud/CloudKit, subject to your Apple Account settings and Apple’s privacy terms.
The Mac common-logbook view reads the last verified phone publication, not a continuously shared live phone database. Both devices need the same iCloud Apple Account. Mac additions, edits and deletions are explicit requests; the updated iPhone app validates and applies eligible changes, including duplicate and gear checks, then publishes the result. FIT requests may include retained original evidence and review material in the user-private exchange. The Mac gear library is read-only.
Saved rig/component and lineset history, at-use snapshots and optional saved profile/dropzone details may be included in the phone publication and backup. Local reminder scheduling and preferences apply to that iPhone. They are not a remote push-notification service.
Ordinary logbook JSON/iCloud backup is not a full original-evidence or device backup. Pending Watch recordings, pending Recording Inbox imports, local-only review material and source video files may require separate preservation. On Mac, a user-initiated verified library archive copies the admitted local review folders to a destination you choose; it may contain private locations and original evidence. Linked source videos remain separate files.
Reusable Signing Identity details remain in local app preferences on the iPhone where the identity is created. After a sign-off is applied, the signer details, comments, sign-off time and status become part of the jump record.
Applied sign-offs may sync to the paired Apple Watch and the user’s private iCloud/CloudKit database. They may also be included in backups or exports that the user chooses to create.
Website form submissions, support and feature-request records, previous launch signup records, and related email communications may be stored by BreakOff and trusted service providers for request tracking, contact management, communications and support purposes.
Firebase Analytics / Google Analytics for Firebase analytics events may be processed by Google/Firebase to provide app analytics, subscription event measurement and Google Ads attribution. Selected Meta App Events may be processed by Meta for app-install, checkout, trial, new-subscription and advertising measurement. These analytics events are separate from your local/iCloud logbook database.
The web-access verification service is described above. Further account, integration or marketplace changes will be reflected in this policy before they are released.
7. Location and sensor data
Location and sensor data are central to some BreakOff features, including jump path review, map display, phase tracking, wind context and canopy/debrief tools.
BreakOff may store coordinates for saved dropzones. It may compare a jump’s landing coordinates with saved or previously used dropzones to offer nearby suggestions. This matching occurs on-device, and suggestions never automatically change the selected dropzone.
You can disable location access in iOS Settings. Some features may not work correctly without location or motion/sensor permissions.
BreakOff location and sensor features are for tracking, logging and post-jump review. They are not intended for real-time safety-critical decisions.
8. Photos and videos
If you choose to attach or link photos or videos to jump records on iPhone, BreakOff may request access to your Photos library. You control this permission through iOS Settings and can limit access to selected items where supported by iOS.
On Mac, you explicitly choose a local video for linked debrief and can set its timing offset. The link and offset remain local. Source videos are not automatically uploaded through private iCloud common-logbook exchange or embedded in ordinary phone backups. A phone media reference/bookmark does not transfer a file to Mac. You can unlink a Mac video without deleting the source file.
9. HealthKit
BreakOff uses HealthKit on Apple Watch. When you start a tracked jump, the Watch app asks for permission to read heart-rate and workout data, and to save a workout to Apple Health. These permissions are optional: if you decline them, jump tracking, the logbook and gear features continue to work, and heart-rate figures are simply omitted from the jump record.
If you grant access, BreakOff records a workout session for the jump and samples your heart rate while that session is running. It uses those samples to calculate the average and maximum heart rate for the jump, which are stored alongside the rest of that jump’s data.
Heart-rate values recorded with a jump are stored with your logbook on your devices. When private iCloud backup or publication is enabled, it can include heart-rate values and can run in the background. A PDF, CSV or jump card that you choose to export or share can also include these values.
Heart-rate readings can be used in the recording and analysis features you choose, including private iCloud publication and your signed-in browser analysis. This publication can send retained readings through Apple’s services to your own signed-in devices and browser. BreakOff does not sell HealthKit data or use it for advertising or marketing. Health access depends on the permissions you grant. You can review or revoke BreakOff’s Health permissions at any time in the Health app or in your Apple Watch settings.
10. Analytics and diagnostics
BreakOff may use privacy-conscious diagnostics and crash reporting to understand bugs, crashes and performance issues. This may include app version, device type, operating system version, crash logs and general usage events.
From BreakOff v1.1, the iPhone app may use Firebase Analytics / Google Analytics for Firebase to measure app installs, app opens, subscription purchase events, entitlement-related analytics events, non-sensitive feature usage and Google Ads campaign attribution.
Firebase Analytics / Google Analytics for Firebase is separate from your BreakOff logbook database. BreakOff does not use Firebase Analytics to store or transmit skydiving logbook content, signer identities, QR payloads, sign-off details, full GPS tracks, gear records, HealthKit heart-rate data, jump notes, photographs or videos.
From BreakOff v1.2.1 (Build 127), the iPhone app uses Meta iOS SDK / Meta App Events for app-install and activation, subscription checkout, eligible trial, verified new paid subscription, campaign-performance and attribution measurement. Automatic StoreKit purchase logging is disabled, and restores, entitlement refreshes, renewals, reinstalls and Family Sharing are not reported as new acquisitions.
The Mac app does not integrate Firebase Analytics or Meta App Events. Its local review content and common-logbook requests are not sent to those services by the Mac app.
The current website loads no advertising or analytics scripts. This website setup is separate from the iPhone integrations described above. External forms and linked services have their own privacy policies.
iPhone diagnostics, Firebase analytics and deliberately selected Meta App Events are separate from the local/private-iCloud logbook database. Original FIT evidence, precise tracks, profile notes, gear history, dropzone notes, local reminder details and linked media are not advertising-event payloads.
11. Third-party services
BreakOff may use the following third-party services, depending on which website or app features you use:
- Meta iOS SDK / Meta App Events: iPhone app-install and activation, subscription checkout, eligible trial, verified new paid subscription, advertising-measurement and campaign-attribution reporting. See Meta’s Privacy Policy.
- Firebase Analytics / Google Analytics for Firebase (iPhone): app analytics, install and app-open measurement, non-sensitive app usage events, subscription purchase event logging and Google Ads campaign attribution.
- Google Ads: advertising campaign measurement and attribution for App Store downloads or subscription-related events where enabled.
- Separate Firebase Garmin pilot relay: account and app verification, existing pilot connection management, retained recording recovery, and relay account removal when you choose the earlier pilot tools.
- GoHighLevel: website contact and feature-request forms, request tracking, previous launch signup records, contact-list management, submission confirmations and permitted email communications.
- OpenWeatherMap: weather and wind data used for pre-jump wind context and related app features.
- Apple StoreKit and App Store: subscription purchase, renewal and entitlement status where paid features are offered.
- Apple iCloud and CloudKit: user-private phone publication, backup/restore and common-logbook request/evidence exchange where enabled by your Apple Account settings.
- Apple map services: maps and satellite imagery requested for the areas you view. Map imagery requires a network connection; retained geometry and charts can remain available without those tiles.
- Garmin / Garmin Connect: Garmin recording, activity storage and original FIT export when you use those services. Import into BreakOff remains manual.
- Apple HealthKit: heart-rate or related health data only if you grant HealthKit permission and the feature is enabled.
Your logbook data is stored locally and in your private Apple iCloud account where publication, exchange or backup is enabled. Website forms, iPhone Meta App Events, Firebase/Google Ads measurement, weather/map requests and App Store purchase processing are handled separately by the applicable providers listed above. Mac has no Firebase/Meta integration. iCloud/CloudKit, StoreKit and map features use Apple network services; local-first does not mean every feature operates offline.
12. Your choices and controls
- You can edit or delete jump records inside the app where supported. Mac common-logbook changes are deliberate requests that the updated iPhone validates and applies. Check the result before removing recovery copies.
- You can edit or clear optional profile and dropzone details, choose whether to use private iCloud exchange, retain/export original FITs and create a separate Mac library archive.
- You can turn local iPhone reminders off, change their categories/hour/recency interval, snooze eligible reminders or change notification permission in iOS Settings. Choosing not to allow notifications does not remove your logbook.
- You can unlink a Mac video or change its local timing offset. Keep or remove the source file separately using your own file controls.
- You can change location, motion, Camera, Photos, HealthKit and notification permissions in iOS Settings.
- Denying or revoking camera access disables QR scanning only. The rest of the BreakOff logbook remains available.
- You can edit or clear your reusable Signing Identity on the device where it was created.
- You can control device-level advertising and tracking preferences through iOS Settings where available.
- You can use Google advertising controls to manage ad personalization associated with Google services where applicable.
- You can disable iCloud sync or remove app data through your Apple device and iCloud settings where applicable.
- You can review the current website cookie/analytics setup through Cookie Preferences in the footer. The current website loads no advertising or analytics scripts.
- You can unsubscribe from marketing/product update emails where an unsubscribe option is provided.
- You can request removal from the previous BreakOff launch notification list by emailing privacy@breakoffapp.com.
- You can ask us to access, correct or delete a website form submission by emailing privacy@breakoffapp.com.
- You can contact us to request help with access, deletion or export of data.
13. Children
BreakOff is intended for skydiving users and is not directed to children. We do not knowingly collect personal data from children. If you believe a child has provided personal data, contact us and we will take appropriate action.
14. Changes to this Privacy Policy
We may update this Privacy Policy as BreakOff evolves. If we make material changes, we will update the “Last updated” date and, where appropriate, provide additional notice in the app or on the website.
15. Contact
For privacy questions or requests, contact:
privacy@breakoffapp.com
For contact-list removal or product update email questions, contact:
privacy@breakoffapp.com
For app support, general enquiries or feature requests, use our Contact & Feedback page or email info@breakoffapp.com.
