Privacy policy

Notice version 2026-11-04 · Updated 4 November 2026

DavesWorkouts is run by David Kee Crees in Australia. He is responsible for the personal information handled by this service. For privacy questions, corrections, access or deletion requests, email privacy@davesworkouts.com.

This notice covers the Android app and website, including the testing preview at daves-workout-lab.fly.dev. Production Google/advertising/payment setup and Google Play publication are not yet complete. Features described below operate only when their provider and account settings are enabled.

The short version

Age ranges and young people

DavesWorkouts is for ages 13 and up. We ask for an age range, not a date of birth. People under 13 must not use the app.

Ages 13–15
Guest solo workouts remain on your device. Account creation and online social or sharing features are blocked while a verifiable parent or guardian process is not available. A checkbox or acknowledgment of this notice is not treated as verified parental permission.
Ages 16–17
Eligible online features are available after the privacy notice and age range are recorded. Your workouts start private; you may choose an unlisted link. Public publishing is restricted to adults. No advertising requests are made for your age group.
Ages 18 and up
Optional online features and moderated public publishing are available. Android advertising requires the applicable privacy choices described below.

Existing accounts must record the current age range and notice before continuing online features. They can still access their privacy controls, data export and deletion. If your age range is wrong, correct it in privacy settings or contact us. Age-range declarations are not identity verification.

Information we handle and why

Local workouts and preferences
The app or browser stores your shuffle seed, current card, progress, timing, workout history and preferences such as theme, sound and age/privacy choices. Guest solo progress does not require an account or personal-history upload. Requests to load the website, assets or API still send ordinary connection information, such as your IP address and request headers, to hosting providers.
Optional reminders and transfers
Workout reminders use your chosen local time and device notification permission; they do not enroll you in a marketing or remote push service. Calendar invitations are files you choose to add to your calendar. A casual workout transfer is an explicit file containing its recipe, shuffle and progress, including reported reps or equipment load where recorded. Authentication tokens, room credentials and private set notes are excluded. Anyone you give the file to can read and import it; imported copies remain casual and cannot establish a strict challenge time.
Accounts and sign-in
When Google sign-in is configured and you choose it, we verify the Google ID token and retain a hashed Google account subject, your app alias and account records. Your Google real name is not automatically made your public alias. The server stores hashes of its session tokens, and sessions expire after 30 days. Hashing reduces direct exposure; these identifiers are still account-linked personal information, not a promise of anonymity.
Restricted preview access
A private preview can use an owner-supplied access key and chosen display name to issue a non-admin test identity. The key is not stored in your profile or returned in public configuration. Preview sessions can be revoked by rotating the key or ending preview mode.
Tester profiles
When tester access is enabled, eligible testers can choose an alias to create a non-admin profile without Google sign-in or an owner access key. Each new tester profile gets a random account identifier; choosing the same alias does not recover or access another profile. Your signed-in session stays on this device and expires after 30 days. Signing out, losing that session or clearing app data means creating a new tester profile; an alias alone cannot recover its online history. The same account privacy, export and deletion controls apply. Tester sessions stop working if tester access or preview mode is disabled.
Online workouts and participation
We store the workouts or exercise submissions you create, including any suit/rank card rules, selected visibility and versions, room membership and progress, private-group membership, results and timing needed for history or leaderboards. A rematch creates a fresh waiting room and invitations for the previous participants; it never joins or readies someone without their action. These records let you resume, sync, share and compare the sessions you choose. We also store reports and blocks needed to moderate content and protect members.
Optional training records
You may record actual completed reps, external dumbbell or equipment load, effort ratings, private notes, favorites and a weekly programme. These records support your own history and progress. External load is equipment weight, not body weight. Personal notes and detailed set records stay private to your account; selected challenge load and self-reported totals can be shown to your chosen room or private group. These entries are optional and are not used to target advertisements.
Community terms
Before an online content upload, we record the community terms version you accepted and its acceptance time. This is separate from privacy acknowledgment and advertising choices.
Privacy choices
For an account, we store its age range, notice version and acknowledgment time, together with the resulting advertising and public-publishing restrictions. A notice acknowledgment is separate from advertising consent and parental verification.
Purchases
Google Play processes payments. We receive the purchase token needed to verify ownership with Google, then retain its hash, product, entitlement status and latest verification time. The app may temporarily keep a pending token while verification retries. We do not receive your payment-card number. Purchase restoration and refund checks use Google Play's services.
Technical and security information
Hosting and provider systems process connection information and operational logs to deliver the service, diagnose faults and respond to abuse or security incidents. Our application does not intentionally log authentication tokens or request bodies as routine analytics. We do not run a separate browser analytics or marketing-tracking service.

The app asks for exercise activity, not medical conditions, diagnoses, body weight, heart rate or other clinical measurements. Exercise records can still be personal and sensitive depending on their context. Do not put another person's private or health information into a workout description or public submission.

Who can see what you share

Your alias and relevant progress are visible to participants in rooms or private groups you join. Private workouts and personal history are restricted to their owner. Anyone with an unlisted link can access the linked workout and may forward the link. Approved public workouts are visible publicly; public publishing is an adult opt-in action and is subject to moderation. The app does not have a global leaderboard.

Authorised service operators may access records to provide support, handle privacy requests, review reports or protect the service. Infrastructure and chosen identity, payment and advertising providers process the data needed for their functions. We do not sell workout histories or supply them as advertising-targeting profiles.

If you use WhatsApp, Signal or another calling app alongside a workout, that provider handles the call under its own terms. DavesWorkouts does not receive or record the call's audio or video.

Advertising, choices and device storage

The browser has no advertisements or checkout. Android advertising is disabled for users under 18 and unknown age ranges. For adults, advertising is requested only after the app's consent flow permits it and purchase checks do not show verified ad-free access. Google User Messaging Platform is used for the applicable privacy messages. Declining optional advertising does not require buying the app or completing a workout.

Requests are configured for non-personalized ads. That does not mean zero processing: Google's SDK may handle IP address, app/ad interactions, diagnostics and device or account identifiers subject to the controls applied. See Google's Mobile Ads data disclosure and Google's privacy policy. We remove advertising-ID and Android AdServices permissions from our app manifest; this does not remove every technical datum a provider may process.

Use the app's privacy settings to change choices. Where Google's consent system requires an advertising privacy-options control, the app exposes it. Withdrawing consent affects future processing; it does not undo earlier lawful processing. Verified remove-ads ownership disables the app's startup and footer advertising.

Browser local storage and the offline cache keep settings, sessions, authentication state and static app assets. Native storage keeps the corresponding app data; native sign-in sessions use encrypted credential storage. These stores support the features you request. Clear local data through app/browser controls when you want to remove device-only copies. Account deletion and removal of data from other devices are separate actions.

Where information is processed

The current preview's primary service runs on Fly.io in Singapore, with an encrypted Fly volume. Private database backups use Tigris through Litestream. We do not claim that the backup provider stores every copy in Singapore. Google and other selected providers may process information in other countries under their own service arrangements.

Encrypted storage and HTTPS reduce risk; they do not make the service anonymous or establish a legal basis for international transfers by themselves. Provider locations, contracts and any legally required transfer safeguards must be reviewed before broader public release.

Retention and deletion

Account information and saved online workout history are kept until you delete the account or request applicable removal; the preview does not currently delete inactive accounts automatically. Login sessions expire after 30 days and expired session records are cleaned during normal service activity. A private deletion journal keeps the account-linked deletion identifier and time so later backup recovery can reapply deletions; it is not a public activity record. We retain operational information only for the support or security purpose that justifies it; provider log and infrastructure-snapshot retention are being confirmed for public release.

Deleting your account removes its active login sessions, profile/privacy record, personal results, authored workouts and exercise submissions, reports, blocks, rematch invitations and group memberships. Groups owned by the account are removed. Shared rooms kept for other participants replace your direct account identifiers and alias with a per-room deleted-member marker; unfinished sessions end. Other participants may still recognise the session from context, so this is not a claim that the retained room is fully anonymous.

A minimal receipt-token hash and entitlement status can remain detached from the deleted account to support valid purchase restoration and prevent duplicate claims. Ask us to review receipt-related retention if you want that information removed; Google controls its own purchase records.

Database backups are configured for a seven-day retention window. Prior backup copies, infrastructure snapshots, database journals or provider records may not disappear immediately when an active account is deleted. The operator must reapply relevant deletion requests before reopening a restored database. Backup and snapshot retention require operational review; we do not promise instant, irreversible erasure of every historical byte.

Your controls and privacy rights

You can change your alias and privacy choices, download your own account data, and delete the account. The website's Privacy & your data controls offer a data download; the authenticated API also provides GET /v1/me/export. Account exports do not expose other members' private records or login/purchase secrets. Device-only records on another phone or browser are not automatically included in an account export.

Depending on the law that applies, you may also ask for access, correction, erasure, restriction, portability, withdrawal of consent or objection to processing. Email privacy@davesworkouts.com. We may need enough information to verify that the request concerns your account, and will protect other people's information when responding. We do not ask you to send a password, preview key, purchase token or identity document in an initial email.

Where GDPR applies, requests are generally answered within one month; a permitted extension and its reasons must be explained within that period. You can also complain to the Office of the Australian Information Commissioner or the relevant European supervisory authority. The app does not make automated decisions with legal or similarly significant effects about you.

Purposes, permissions and changes

We use information to provide the account and workout features you request, maintain service security, handle purchases and privacy requests, and provide optional adult advertising when permitted. The legal basis and any additional condition for sensitive data depend on the applicable jurisdiction and purpose. The preview's legal-basis, processor and transfer review must be completed before broader release; accepting this notice alone does not authorise every form of processing.

We will update this notice when the service or its data handling changes and ask for a new acknowledgment where appropriate. This testing notice describes the implemented design and remaining operational review; it is not a GDPR certification or a guarantee against legal claims.