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, the optional Fight Arc generation feature, and anything you deliberately publish to The Yard — all described below — and purchases handled by Apple and RevenueCat, BeepSync does not send your training data anywhere.

The Yard: Accounts & Community

The Yard is BeepSync's optional member community, available inside the app and at community.getbeepsync.com to BeepSync Pro and Elite owners. It is the only part of BeepSync that uses an account. You can use every training feature without one.

If you create a Yard account, BeepSync collects and stores on its servers:

• • Account identity — your email address and a password. The password is stored only as a hash by our sign-in provider; BeepSync never sees it. Moderators also register an authenticator app.
• • Yard identity — the handle you choose and, if you add them, a display name and a short bio. Other members see these on your Yard Card.
• • What you post — threads, replies and reactions, and the items you save.
• • Work Logged — only when you choose to publish a completed session: a summary of that session (the training mode, when it was completed, whether it was completed or ended early, and headline figures such as rounds, duration or distance) and an optional caption. Nothing is published automatically.
• • Fight Camp status — if you are an Elite member running a Fight Camp, the camp name, current week, length and start date are sent to The Yard so your own Yard Home can show it. Only you can see it.
• • Safety records — members you block, reports you send, and any moderation decision about your account or content.
• • Settings — your reply-notification and Yard Card visibility choices.
• • Membership — whether your BeepSync purchase currently includes Pro or Elite, so The Yard can confirm access (see Apple & RevenueCat below).

Work Logged never includes readiness, RPE, Journal entries, notes, MODUS OS or HELIX data, motion or strike data, or location. Your training history stays on your device unless you deliberately publish a session summary as described above.

Threads, replies, Work Logged and your Yard Card are visible to other Yard members. They are not public on the open web and are not used for advertising.

Yard Safety & Moderation

Posts and Yard identities are checked automatically against a list of prohibited terms when you submit them. Content that matches may be refused or held for review by a moderator before anyone else can see it. Members can report content or another member, and block a member.

When something is reported or held, The Yard keeps a moderation record: the report, a copy of the reported content as it was at the time, and the decision taken. Moderators can see reported content and that record. They cannot see your email address, your purchases or your private training data.

Deleting Your Yard Account

You can delete your Yard account inside the app at any time: open The Yard, then Account, then Delete Yard Account. The same screen lets you export the data The Yard holds about you first. You do not need to contact us.

• • Your access to The Yard is frozen as soon as you ask. Deletion is then carried out by an automated process and normally completes within minutes; the same screen shows its status. BeepSync does not hold deletions back. Only in exceptional circumstances, such as a technical failure that has to be retried or a legal obligation, can it take longer, and never more than 30 days.
• • Deleted: your email and sign-in, your Yard identity and Yard Card, your settings, your Fight Camp status, your reactions and saved items, the members you blocked, your notifications, and the link between your Yard account and your purchases.
• • The text of your threads, replies and Work Logged is erased. Where other members replied to you, an empty “withdrawn” placeholder with no name and no content stays in place so their conversation still makes sense.
• • Kept: moderation records about reported or held content (including the copy of the content that was reported), reports you sent, and an anonymous internal account reference with your last membership level. These are kept only for safety, dispute and legal reasons, cannot be seen by members, and are no longer connected to your email address.
• • Deleting your Yard account does not cancel a BeepSync subscription and does not remove training data stored on your device. Manage subscriptions in your Apple ID settings, and use Clear Training Data in Settings for on-device data.

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.
• • Without a Yard account, your plan is tied to your Apple ID through Apple and RevenueCat and to nothing else.
• • If you create a Yard account, The Yard gives it a random purchase identifier and the app registers that identifier with RevenueCat. RevenueCat then tells the Yard server whether that identifier currently has Pro or Elite. Your email address is not sent to RevenueCat.
• • 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: the Fight Arc generation feature described above, and Yard accounts and the Yard database. 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. Only what you deliberately publish to The Yard is stored there.

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, Yard and remote-processing purposes described above — neither is used for analytics or tracking. BeepSync does not track you across other companies' apps or websites.

Website Cookies & Tracking

The BeepSync website does not currently use non-essential cookies, analytics cookies, advertising pixels or third-party embedded media tracking. The Yard website (community.getbeepsync.com) sets the cookies needed to keep you signed in, and nothing else.

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.

Yard accounts have their own export and deletion controls inside The Yard — see Deleting Your Yard Account above.

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.
• • Yard account data and what you post are kept until you withdraw the content or delete your Yard account. What is deleted and what is kept afterwards is set out in Deleting Your Yard Account above.
• • Apple, RevenueCat, Supabase, Render, Netlify 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.

Who Processes Your Data

BeepSync does not sell personal data and does not share it for advertising. These companies process data on our behalf, only to run the features described in this policy:

• • Apple — App Store payments and subscriptions.
• • RevenueCat — purchase and entitlement status.
• • Supabase — Yard sign-in and the Yard database (hosted in the EU), and the function that handles optional Fight Arc requests.
• • Render — hosts the Yard server that the app and the Yard website talk to.
• • Netlify — hosts this website and the Yard website, and processes website forms.
• • OpenAI — generates optional Fight Arcs, only if you turn that feature on.

Like any internet service, these providers record technical request information such as IP address and time of request in their server logs for security and reliability.

What This Policy Covers

• • What training data is stored locally on your device
• • What data may leave your device, and why
• • What a Yard account stores, and what other members can see
• • How Yard moderation works and what it keeps
• • How to export and delete a Yard account
• • Which companies process data for BeepSync
• • 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, to ask for a copy or correction of your data, or to report a problem in The Yard, email us.