Delete your Ascent Mode account and data.

Request account and associated-data deletion, including when you cannot sign in.

​

Draft request page, not a connected deletion tool.

​

The preview does not sign in, submit a request or erase an account. The final public web route and in-app journey require launch verification.

​

Ascent Mode, LLC operates Ascent Mode. The intended standalone app path is Settings → Privacy → account deletion, with recent same-account authentication and explicit confirmation. The public no-login fallback is privacy@ascentmode.app. Removing the app or deactivating access is not account/data deletion.

Option 1: start inside the app

Open Settings → Privacy, review/export records you want to keep, choose account deletion and follow the fresh confirmation. Account and associated service-data deletion must be available from the final iOS and Android app. Invitation withdrawal or suspension does not cancel privacy rights; provider-pending deletion must keep an appropriate retry or reviewed follow-up route.

​

Option 2: use the public email route

​

Email privacy@ascentmode.app with “Ascent Mode account or data request.” State whether you want account deletion, access/export, correction, withdrawal or help with a retained copy. Include your account email if available. You do not need an active invitation, sign-in, a new account or a reinstall.

​

Email a privacy request

​

Do not send passwords, tokens, recovery keys, health records, member records or a full workout export. Ask for an approved secure follow-up route when necessary. These preview email buttons show the destination; they do not submit a message.

Final app and public web paths

The proposed public route is /delete-account. Google Play’s outside-app resource can use a functioning support email; it must actually accept account and associated-data requests. Apple requires an easy-to-find in-app initiation path for an ordinary account-creating app; email-only intake is not a substitute. Both routes must describe the same scope, retained categories and completion states. Google Play deletion requirements; Apple deletion guidance.

​

Access, correction, withdrawal and deletion

​

Use Settings → Privacy for account export, optional usage-analytics choices and account deletion. Use the body-record controls for individual readings and History for supported workout-time corrections. Access requests can include account, invitation, support, retained-copy and provider categories beyond the normal account export; a business CSV is not your portability bundle.

​

You can also email privacy@ascentmode.app without signing in, registering again or holding a valid invitation. State the request and account email if available. Do not send passwords, tokens, recovery keys, health records or a full export in your initial message. Ask for a secure route if sensitive follow-up is needed.

​

We verify only what is proportionate to the request. A fresh same-account sign-in or reviewed original-service ownership evidence can help; matching an email or nickname alone does not establish ownership. Government identification is not requested by default. If self-service is unavailable, the privacy mailbox remains available.

​

Response and appeals

​

The adopted operating targets are acknowledgment within two business days and completion of requests or appeals within 30 calendar days. These are working targets, not universal legal deadlines. We record receipt and the applicable legal clock, use any shorter requirement, and explain a permitted extension, refusal or unresolved provider step with its reason and next action.

​

To appeal, email privacy@ascentmode.app with “Privacy appeal” and your request reference. The sole business owner reconsiders the evidence and reasons in a fresh review; this is not an independent reviewer. The response explains the decision and the applicable complaint route. See the state-specific health-data rights and complaint routes below the health notice’s rights section.

Deletion, copies and restoration safeguards

Account deletion closes the Ascent account, removes owned live service records, revokes device access and minimizes related shared references. Removing one body reading removes its live values, notes, raw/duplicate content and derived current-device reading when cache removal succeeds. Minimal source identifiers can remain to prevent the same reading from being reimported.

​

Copies under Ascent’s control: operator exports, source/staging/QA copies, migration archives, encrypted backups and processor-held copies remain within the request review. We track affected copies, send applicable downstream deletion instructions, follow up on completion and document any justified exception or unresolved step. A downloaded operator file is still Ascent’s responsibility.

​

App and provider states: live app erasure and Firebase sign-in deletion are recorded separately. A provider-pending response is not completed provider deletion. The closed account retains an appropriate retry or reviewed provider follow-up route. A receipt for one step does not certify every backup or processor copy is erased.

​

Files held independently: we cannot automatically recall files you downloaded, screenshots or shared files independently kept by recipients, or original Apple Health/Health Connect records. Other devices may retain offline copies that need removal on those devices. These limits do not exempt Ascent-controlled files or contracted processors from the deletion procedure.

​

Restricted closure, withdrawal, deleted-reading and identity-link evidence may remain while needed to prevent delayed writes or old backups from restoring deleted data or withdrawn choices. It remains personal data, is limited to that purpose and receives quarterly minimization review. Restore procedures require a newer, separately protected suppression ledger before a recovered service opens. Provider backup periods and actual restore acceptance still require release verification; no universal erasure deadline is promised.

​

Narrower choices

​

You can request correction, removal of a specific reading, analytics withdrawal or connection revocation without treating every action as account closure. Revocation stops future authorized health uploads; earlier imports and original phone-health stores are separate. See the category retention schedule and consumer-health rights and legal clocks for request handling.

​

General privacy · Consumer health privacy · Account support