Privacy policy

Last updated: 27 September 2026. Draft for the open beta (v0.9); the founder reviews it before the store launch.

Beatweek is a workout log. This policy says what the app stores, where, and what leaves your device. The short version: your training data stays on your phone unless you create an account and turn on sync, and nothing is sold, shared with advertisers or used to profile you.

What the app stores on your device

• Workouts, sets, exercises, routines, programs and personal records you log or import.
• Preferences: units, bodyweight, height, age and sex if you enter them (optional; bodyweight and sex feed the strength-standards table, and all four feed Cut’s calorie estimate and safety floor if you set a Cut goal), rest timer, plate inventory, theme.
• If you use Cut: your daily bodyweight entries and your Cut goals, for the trend, the pace and the estimate only.
• The rest timer’s end time, so the alarm survives a restart.
• Movement diagrams: the app downloads the small looping figures it draws for some exercises from Beatweek’s own website and keeps them in its cache. Nothing about you is sent to fetch them — no account, no exercise you looked at, no identifier — and the diagrams are the same for everyone.
• If you use the watch app: the same data mirrored between phone and watch over the Wear OS Data Layer, which never leaves your devices.

All of this lives in the app’s private storage, and the training database is excluded from your device backup on every platform: it is not copied into an Android cloud backup, nor into an iCloud or iTunes backup on iPhone and Apple Watch. Your training history therefore does not follow you to a new device unless you turn sync on. On Android the app’s preferences are excluded as well; on Apple a small set of device preferences (units, theme, the rest timer’s end time — never your workouts) is part of the system backup. Your sign-in session is never backed up on either platform. Deleting the app, or Profile → Delete all local data, removes all of it.

Optional account and sync

You can use every feature without an account. If you create one (email and password, magic link, Google or Apple sign-in), Beatweek stores:

• Your email address and a user id, to identify your account.
• Your workouts, routines, records, bodyweight log, Cut goals and profile settings, so they sync between your devices and can be restored on a new phone.
• If you choose Sign in with Google or Sign in with Apple, your device asks that provider for a sign-in token; the provider learns that you are signing in to Beatweek, and the token carries your name and profile picture URL, which the authentication service (Supabase Auth) stores with your account together with the IP address and device description of each sign-in. Beatweek itself only shows your email. Email sign-in and magic links involve no third-party provider.

Account data is held on a Supabase project operated by the app’s developer. Rows are protected by row-level security so only your account can read or write them. Sign out to stop syncing; Delete account removes your account and every synced row from the server. Local data on the device is kept unless you delete it too.

Purchases (Beatweek Pro)

Beatweek Pro is sold through Google Play and the App Store. When you buy it, the store handles the payment: Beatweek never sees your card or your billing address. To unlock Pro on your devices and let you restore it, the purchase receipt, the product you bought and its expiry date are validated and stored by RevenueCat, the app’s billing provider, under a customer id. That id is random and anonymous until you sign in; after you sign in it is your Beatweek account id, so Pro follows your account. The app keeps the expiry date with your profile (pro_until) and syncs it with your account like any other profile field. RevenueCat’s own privacy policy applies to the data it processes for us. Nothing about a purchase is used for advertising. Manage or cancel subscriptions in your store account; a refund is handled by the store.

What is not collected

• No advertising identifiers, no ad networks, no trackers.
• No location, contacts, photos or health-platform data.
• No analytics or crash-reporting SDK. During the beta the phone app sends anonymous usage counts and error reports to Beatweek’s own Supabase project, and nothing else. Each record holds exactly: a random install id (created by the app, not a device or advertising id, and replaced when you use Delete all local data), the platform (Android or iOS), the app version, the OS major version, the device model (for example “Pixel 9” or “iPhone17,1”), the event name (such as “workout finished” or “error in the sync pass”), a few numbers, yes/no flags or fixed categories (such as how many sets, whether a workout came from a routine, which paywall was shown), and the time. An error report names only the kind of error and where in the app it happened, never its message. No workout content, exercise names, notes, weights you typed, names, emails, account ids, language or location are sent, and the records are not linked to your account: uploads are made without your account token. Like any web request, an upload reaches the server from your network’s IP address; the address is not stored with the records. They are kept for 90 days and then deleted. Turn this off any time with Profile → Share anonymous usage data; switching it off also deletes anything not yet sent. The watch apps send nothing. The only counts kept about purchases are which paywall was shown and whether a purchase completed, was cancelled or failed; never the price or the account.

Feedback email

Send feedback opens your own email app with a subject line and a device line (app version, OS version, device model, language) pre-filled. Nothing is sent until you send the email yourself.

Permissions

• Notifications (Android 13+): only to show the rest-timer countdown and the “rest over” alert.
• Wear OS: physical activity and body sensors, only so the watch can keep the workout session running in the background.

Children

Beatweek is not directed at children under 16.

Changes and contact

Changes are announced in the app’s release notes and dated at the top of this document. Questions: [email protected].

This page is generated from docs/legal/privacy.md in the app repository so the app and the site never differ.