Privacy Policy

Local Training Data

Depending on which features you use, BeepSync stores training data locally on your device to power its timers, progression and MODUS OS features. Only the categories tied to features you actually use will apply to you. This can include:

• • Completed sessions and training history
• • Readiness check-ins and RPE
• • MODUS OS, HELIX and progression state
• • Journal entries
• • Fight Camp data
• • LiftSync sessions
• • Sculpt sessions
• • Motion-based session data
• • ROADWORK workout history
• • App preferences and settings
• • An optional Tale of the Tape fighter photo, if you add one
• • Other local training state produced as you train

An optional fighter photo is stored locally on your device. It is not uploaded to BeepSync or any third party by normal app behaviour.

Offline-First Design

MODUS OS and HELIX process your training history entirely on your device. Outside of ROADWORK's optional location tracking and the optional Fight Arc generation feature — both described below — and purchases handled by Apple and RevenueCat, BeepSync does not send your training data anywhere.

ROADWORK & Location

ROADWORK's optional outdoor-run tracking is the only feature in BeepSync that uses your device's precise location.

• • Location is requested only when you start an outdoor ROADWORK session — never at install, onboarding, or app launch.
• • BeepSync asks for foreground (“When In Use”) location first. If tracking needs to continue while the app is in the background — for example if you lock your screen mid-run — BeepSync may separately ask for background location, after showing an in-app explanation of what that means.
• • Tracking runs only for the duration of the active outdoor session and stops automatically when the session ends.
• • Raw route coordinates are transient: they are used on-device to calculate distance and pace, then discarded. They are not retained in your workout history, and BeepSync does not display, store or share a route map.
• • What is retained in your workout history is performance information derived from that tracking, such as distance and pace for the session — not the coordinates themselves.
• • ROADWORK does not track your location outside an active outdoor session, and does not use location for advertising or profiling.

Motion & Device Sensors

Some training features, including Motion-based session tracking, use your device's built-in motion sensors (such as the accelerometer and gyroscope) to detect movement during a session. This is processed on-device to support training features like rep or strike-event detection. It is not medical monitoring, and BeepSync does not use it to diagnose any health condition.

Optional Remote Fight Arc Generation

Edge works offline with 60 opponent profiles and six built-in Fight Arcs. Optional AI-generated Fight Arcs are a separate, opt-in feature. Before any request is sent, BeepSync shows this consent disclosure:

• • Only the specific context relevant to that request — things like recent readiness, RPE, execution feel and HELIX focus tags — is sent. Your full training history, name, email and Journal notes are never included.
• • The request is handled by a Supabase Edge Function that BeepSync operates, which forwards the relevant context to OpenAI to generate the fight arc script and returns it to your device.
• • If you do not give consent, no request is ever sent, and Edge continues to work fully offline using its built-in opponents and Fight Arcs.
• • You can turn this setting on or off at any time in Settings.

Apple & RevenueCat (Purchases)

BeepSync Pro is a one-time purchase. BeepSync Elite is an optional auto-renewing subscription, billed monthly or annually. All purchases are processed through the Apple App Store.

• • Apple handles payment processing, App Store transactions and your Apple ID account information under Apple's own terms and privacy policy. BeepSync does not receive your full payment card details.
• • BeepSync uses RevenueCat as its purchase and entitlement processor. RevenueCat receives purchase and transaction information from the App Store and uses it to determine your entitlements (Pro, Elite), and to support Restore Purchases and subscription status.
• • BeepSync has no account or login system — your plan is tied to your Apple ID through Apple and RevenueCat, not a BeepSync account.
• • The RevenueCat public SDK configuration key used by the app is a public client identifier, not personal data.

You can restore a previous purchase, or manage or cancel an Elite subscription, from Settings → Account & Plan inside the app.

Supabase

BeepSync uses Supabase as backend infrastructure for the specific features that require remote processing — currently, the Fight Arc generation feature described above. The app connects to Supabase using a public client configuration (a project URL and anon key), which is standard for this kind of setup and is not itself personal data. Using Supabase for a specific feature does not mean your full BeepSync training history is synchronised to it — your session history, MODUS/HELIX state and Journal are not sent to Supabase.

Analytics, Crash Reporting and Push

The BeepSync app contains no analytics SDK, no crash-reporting SDK and no push SDK. RevenueCat and Supabase are used only for the purchase and remote-processing purposes described above — neither is used for analytics or tracking.

Website Cookies & Tracking

The BeepSync website does not currently use non-essential cookies, analytics cookies, advertising pixels or third-party embedded media tracking.

Your browser may cache first-party website files such as images, video, fonts, scripts and styles so pages can load and work normally. The site may also read device preferences such as reduced-motion settings to present the website appropriately.

When you choose to submit a website form, the information you provide is processed through Netlify's form service. Current BeepSync forms use a honeypot field for spam protection and do not use reCAPTCHA.

If we introduce analytics, advertising technology, third-party embeds or other non-essential storage or tracking in future, we will reassess the consent requirements before enabling them.

Website Forms

Information submitted through website forms — such as Founding Testers applications or the feedback form — is processed separately from the on-device app training data described above. These forms are handled by Netlify, the host of this website, as set out in the two sections below.

Founding Testers Applications

Founding Testers recruitment is not currently open to the public. This section describes how it works whenever it is open, so it stays accurate if recruitment reopens. If you apply to the Founding Testers programme while it is open, the details you submit are used for one purpose: reviewing your application and contacting you about the programme. Applying does not add you to any marketing list.

Submissions are collected and stored by Netlify, the host of this website, and are reviewed manually. We do not ask for medical information, injury history, date of birth, home address, identification documents, photographs or body measurements, and you should not send them.

If we need to confirm your training context, we will ask you first. We do not contact a club, gym or coach on your behalf without your explicit permission.

How long we keep application data:

• • Unsuccessful applications: kept for up to 12 months, then deleted
• • Waitlisted applications: kept until the cohort closes, then up to 12 months
• • Accepted testers: kept for the testing period, then up to 24 months as a programme record
• • Verification notes: kept only while needed, then deleted
• • Feedback you send us: kept while the related product decisions are active, then anonymised or deleted

You can withdraw an application, or ask us to delete your application data, at any time by emailing the address below. Accepted testers are asked to agree to separate participation and confidentiality terms, and we will always ask for separate permission before quoting anyone publicly.

Product Feedback

If you send product feedback through the feedback form, the information you submit is used to review that feedback and to improve BeepSync. Sending feedback does not add you to any marketing list, and we do not sell feedback information.

Submissions are collected and stored by Netlify, the host of this website, and are reviewed manually. Your contact details are used to identify the submission and to reach you if we need clarification. The access level you select is contextual information you provide yourself, not a verified entitlement check.

The feedback form does not accept screenshots or any other file uploads. Please do not send payment details, passwords, identification documents or health information.

How long we keep feedback data:

• • General feedback: may be kept while the related product decision remains active, then anonymised or deleted
• • Bug reports: may be kept through investigation and release verification, then reviewed for deletion or anonymisation
• • Contact details: normally removed or disconnected from the feedback once they are no longer needed
• • Duplicate feedback: may be anonymised while an aggregate count is retained

You can ask us to correct or delete your feedback at any time by emailing the address below. We will always ask for separate permission before quoting anyone publicly.

Data Export & Deletion

Settings gives you two local data controls:

• • Export My Data — creates a JSON file on your device containing your local BeepSync data (sessions, history, readiness/RPE, Journal, Fight Camp, LiftSync, Sculpt, and MODUS/HELIX history) so you can review or keep a copy of it.
• • Clear Training Data — removes your local training data and history from the app. It preserves your app configuration, legal and privacy links, and your Edge Remote Processing consent choice.

These controls affect data stored on your device. They do not delete transaction or purchase records that Apple or RevenueCat are required to keep under their own policies, and they do not delete separate website form submissions — contact us directly for those (see Founding Testers Applications and Product Feedback above).

Retention

• • Local training data remains on your device until you use Clear Training Data, remove it through another supported in-app control, or uninstall the app.
• • ROADWORK route coordinates are transient and are not retained as route history — see ROADWORK & Location above.
• • Apple, RevenueCat, Supabase and OpenAI each retain data under their own legal and operational requirements for their part of the service; BeepSync does not control those retention periods.
• • Website form submissions are retained as described in the Founding Testers Applications and Product Feedback sections above.

What This Policy Covers

• • What training data is stored locally on your device
• • What data may leave your device, and why
• • How ROADWORK handles location data
• • How purchases are handled by Apple and RevenueCat
• • How Supabase and OpenAI support optional Fight Arc generation
• • What export and deletion controls are available
• • How Founding Testers application data is handled
• • How product feedback submissions are handled

Contact

For questions about this policy or how your data is handled, email us.