Privacy control
Delete a Beta account
Delete from the app when possible, or begin a verified request here if you no longer have access to it.
Delete in the app
- Open You, then Settings, then Privacy & account.
- Choose Delete account and confirm.
- Complete recent Google reauthentication when asked.
- Keep the app installed until Beta confirms server deletion and clears local data.
If a retry is needed, the app keeps the deletion status instead of pretending that the account is gone. Unsynchronized performed work is not silently discarded during sign-out.
Request deletion without the app
Send the request from the email address associated with the Google account used for Beta. State which provider you used. Do not send passwords, authentication tokens, pain notes, screenshots of private training data, or an account export.
The monitored request address is awaiting a release owner.
An email request begins the process; it does not bypass identity verification. Support may ask you to complete provider reauthentication or another reviewed account-ownership check.
What is deleted
- Beta profile, goals, capabilities, preferences, locations, and equipment.
- Workout proposals, performed session events, history, assessments, and progress state.
- Device, synchronization, export, and active-session records associated with the account.
- The Beta identity and sessions in Better Auth. Your Google account itself is not deleted; no cloud export files are created.
What may remain
A restricted hashed receipt prevents old tokens, retries or offline sync from recreating a deleted account. It is pseudonymous security data, not a claim of anonymity. Its retention period and backup expiry must be specified before launch. Other devices and any exports you downloaded require separate local cleanup; backups are not immediately erased.
Registering again after deletion
At present, the same Google identity also cannot register a new Beta account after deletion. This prerelease limitation blocks fresh registrations as well as stale requests. The retention and re-registration policy must be finalized before launch.
Expected completion
The operator must respond without undue delay and normally within one month. A legally permitted extension for complexity or number of requests must be explained within the first month. Submitting a request or sending an email does not complete deletion. If fulfillment fails it stays pending or retryable; the app clears its local private account data after confirmed server completion.