What Ascent Mode uses, who receives it and how to exercise your choices.
Future launch notice · Draft for review.
Prepared October 10, 2026; website information updated October 30, 2026. The standalone-service notice remains a draft for review and is not effective on the existing app. The website section describes the published marketing website’s current configuration. Final standalone-service providers, supported jurisdictions, affiliate facts and legal review remain launch decisions.
Need to make a privacy request?
Email privacy@ascentmode.app; an active beta invitation is not required for this contact route. See account deletion and data-request steps. Website cookie choices and optional app analytics are separate controls.
Ascent Mode, LLC, Florida, United States operates Ascent Mode for adults 18+. Privacy requests and appeals: privacy@ascentmode.app. App help: support@ascentmode.app. Technical reports: developer@ascentmode.app. Read the distinct consumer health data privacy notice.
This page combines a draft notice for the intended standalone launch service with current information about the published marketing website. The notice in the original service governs its existing operation. A migration does not erase responsibilities for retained original-service records. Supported U.S. jurisdictions and any required postal contact details remain unconfirmed; international availability is not implied.
Website visits, technical processing and email
The published website uses GoDaddy Websites + Marketing hosting, platform components and asset delivery. These services can process technical delivery and security information. The website does not connect to an Ascent Mode account or read workout or body records. The interactive sample saves no workout. A complete inventory of every provider request, storage lifetime and browser behavior remains a separate review.
Google Analytics 4 and GoDaddy measure marketing-website visits, traffic sources and engagement. GoDaddy’s native integration uses Google Consent Mode: Google receives cookieless measurement pings, including page URLs and technical consent information, before you choose or if you decline optional cookies. Google Analytics cookie storage remains denied until you accept. Google and GoDaddy can receive page URLs, referrers, browser and device information, and cookie-based identifiers. Google signals, advertising personalization and user-provided data collection are off. We do not send beta form values, workout records, body measurements or app account identifiers to Google Analytics. Automatic form and search tracking are disabled. The website chat widget remains disabled. Website cookie choices and optional app analytics are separate controls. See Cookies & preferences for the reviewed settings and inventory limits.
Beta requests: the live form requests an email address and optional name. It has no message field, uploads or marketing opt-in. Submissions create a GoDaddy Conversations inquiry, with notifications routed to support@ascentmode.app. We use those contact details to review the request and reply about access. GoDaddy and Google reCAPTCHA process the form and related technical information for delivery and spam protection. Requesting access does not create an app account, guarantee an invitation or subscribe you to marketing.
The marketing website was published October 12, 2026. Publishing the website does not adopt the proposed standalone-app notice or change the original app’s governing notice. Website controls and app choices are separate; see the website cookie choices.
Sending an email creates a Google Workspace business-mailbox record: sender/contact details, subject, message, attachments you send, correspondence and delivery/security metadata. The source is you or your mail provider. We use it to answer support questions, consider a beta inquiry, discuss a requested program, investigate a technical/security report or handle a rights request. Privacy/developer addresses route to the support business mailbox; access is restricted to the sole operator and Google Workspace’s service role.
An inquiry does not create a promotional subscription. A future promotional subscription needs its own clear choice and unsubscribe/suppression handling. Gym/home location and phone platform are optional context unless needed to resolve your specific request. Do not email health records, full exports, member records, credentials or invitation tokens. Ask for an approved secure route when sensitive follow-up is necessary. See the category retention schedule below.
Identity/profile: account identifiers, name, verified sign-in email when available, goals, units, schedule and time zone. Invitation/eligibility: verified Google name/email, adult confirmation, country/U.S. state, existing-workout status, notice version, review outcome and times. These administer requested access and jurisdiction/adult review. Birth date, street address and identity documents are not requested by default. Sign-in alone does not grant admission.
Training: routines/exercises, session times and corrections, working/warmup sets, load, reps, effort/recovery ratings, notes, rewards, target responses/override reasons and review history. Generated context: comparisons, suggested targets, supporting reasons/limitations, estimated training information and weekly reviews derived from records. Optional body/health: entered/confirmed weight, BMI, body composition, circumference, water/muscle, metabolism, cardiovascular, score and segmental fields, plus source/app/device names, identifiers and modification/sync times, duplicate decisions and connection preferences.
Sources are your entries, reviewed routine files/imports, supported separately authorized health connections, authenticated original-account transfers and Ascent’s calculations/service records. Purposes are account/access administration, logging/history, synchronization/recovery, the requested training guidance and selected sharing. Device screenshot recognition saves confirmed measurements rather than the screenshot; final device/network behavior remains an implementation check.
Provider roles for the intended standalone service
Firebase Authentication: sign-in identity, credentials/session and security metadata. Workout and body values are not sent through Ascent’s sign-in integration.
Cloudflare Workers and D1: app API/service operation and storage of account, invitation, training, body, privacy, Crew and service/audit records; also relevant technical logs/recovery copies.
Google Workspace: business email, restricted rights registers, encrypted operational archives and reminders.
ChatGPT Sites original service: retained source-account records, authentication/hosting and migration copies are addressed separately, rather than treated as the new-user launch sign-in service.
Chosen recipients: Crew friends/challenge participants and recipients of files/cards see the specific information explained below.
Future Apple/Google store payment/status processing, FCM/APNs phone alerts and Apple Health/Health Connect permissions require the final enabled configuration and separate relevant disclosures. Their presence in source/dependencies is not a claim that they are enabled for launch. The reviewed recipient inventory names no affiliate recipient; actual affiliate status/receipts remain unverified in this draft.
Restricted business access
The sole operator’s restricted service projection covers names, verified emails, choices, workout completion summaries, challenge participation and referrals for support/service operation. It excludes loads, reps, private notes and body values. Optional action reports include consenting accounts only. Access is recorded with actor, dataset, action, count and time; operator exports have their own protection and disposal schedule.
Optional Crew: what others can see
Enabling Crew shares your chosen nickname and internal profile identifier with people receiving your friend code or invitation. Accepted friends can see the relationship status and invite you to challenges. Joining a challenge shares nickname, membership/status, completed workout dates, workout-day totals, points/rank and high-fives with its participants.
Accepted friends in the same active challenge can receive completion updates with nickname, challenge name/date and internal account/challenge references. These participation fields can reveal fitness activity. Loads, reps, private notes and body values are excluded from the documented Crew responses.
Review this audience before joining. You can pause Crew, block someone or leave/close a challenge; these actions stop future visible participation and invalidate related alerts. They cannot recall what recipients already saw or captured. Other participants’ earned results may retain substituted membership/award references. Those are minimized personal data, not certified anonymous.
Shared routine files contain the exercises/instructions you choose to export; achievement cards contain what their preview shows. Recipients can keep or reshare files. This chosen file sharing is separate from ordinary account storage, analytics and promotional email.
The reviewed browser configuration enables optional first-party product analytics only after a current separate choice. Events identify fitness-app activity even though they exclude raw load, rep and measurement values. They are account-linked, not anonymous. Ascent Mode, LLC uses them to understand feature use and reliability; Cloudflare stores them for Ascent. The reviewed inventory identifies no advertising, CRM or health-marketing recipient for these events.
Stored fields are account ID, event ID/name, allowed properties, occurrence and receipt timestamps, and an ephemeral session UUID for browser sessions. Allowed context is limited to surface, setup step, engine version, fixed reason, import type, platform/source, plan, notification category, sandbox/first-use flags and session UUID as relevant. Private notes, name/email, arbitrary errors/URLs, raw loads/reps/measurements, phone-health payloads and advertising identifiers are excluded.
See the active browser/service event inventory
These are the reviewed emitting paths, subject to the feature being used and current consent; an allowlisted name alone is not proof an event is collected.
Recommendation shown/opened names are reserved without a reviewed emitter. Health-permission/connection telemetry is disabled. Native first-party telemetry wrappers and native-context browser analytics are disabled. Billing/push event names belong to disabled or separately gated service paths and are not represented here as active collection. Final SDK/build and physical-device observation govern the released inventory.
Live usage events have the 90-day cleanup rule in the retention schedule. In Settings → Privacy, “Turn off & remove usage events” stops optional event collection once withdrawal is observed, removes stored owned usage events and clears available device queues. A request already in flight may reach the service before a concurrent withdrawal; event storage rechecks the current choice. Consent wording/version, revision, choice and time, necessary service/security records, actual workout records and Crew participation records remain distinct.
The proposed wording version is 2026-10-10.usage-v2 and requires a fresh choice. A training-settings save, terms acceptance, website cookie choice or phone permission does not opt you in. Backup/processor follow-up and restore suppression apply to withdrawals too.
Advertising and promotions
No app data sale, targeted advertising or promotional delivery is enabled in the reviewed configuration. This does not certify the existing website’s unreviewed tags. Inactive marketing preferences are not permission to start a campaign. Training/health records must not become a website promotional list or advertising audience.
The app/operational periods below are adopted for launch; the ordinary-mailbox criterion is explicitly proposed pending adoption. It describes periods or triggers, not evidence that cleanup is already running. Specific documented legal holds can override an ordinary period; their purpose, scope and review/expiry are recorded with restricted access.
Account, profile, training, routine and body records: are retained for the account until the relevant record or account is removed. There is no inactivity-expiry rule.
Privacy/analytics wording and choice receipts: retained while the account exists; withdrawal updates the choice without erasing the evidence of what was agreed. Minimal closure/suppression evidence is handled separately.
Optional usage events and operator-access audit: a 90-day cleanup rule from receipt/recording, subject to documented holds. Account deletion and analytics withdrawal also remove owned usage events. Cleanup execution and monitoring must be verified at launch.
Pending/reviewed invitation applications: expire 30 days after submission or last operator-review activity. Viewing a request does not restart the period. Declined contact/state details are removed 30 days after the decision. Approved details remain while access is active. Non-approved requests can be withdrawn; revoked cases are reviewed under the request/hold procedure.
Unclaimed expired invitation links: 30 days after expiry. Invitation audit: 90 days after recording, except documented holds. A consumed link does not become reusable when details are removed.
Ordinary support, beta and program emails — proposed criterion, pending adoption: kept to resolve the conversation and any requested follow-up. At the monthly retention review, resolved correspondence without an outstanding access request, support issue, agreed pilot follow-up or documented legal/security need is selected for removal or minimization. This draft purpose/closure criterion and its operational disposal rule need owner adoption; no fixed mailbox auto-delete period has been adopted. Provider copies and any retained exception need separate review.
Website beta inquiries: GoDaddy Conversations, notification emails and provider copies need a separate retention and disposal procedure before the form goes live. The app’s invitation-application cleanup does not automatically remove website inquiries or mailbox copies. Contact privacy@ascentmode.app to request removal; identity checks and any justified exception are handled through the rights-request process.
Operator task CSVs: removal within seven days after the task is completed, covering the operator’s controlled copies and verified storage disposal.
Daily encrypted archives: 30 days from creation under the adopted rotation schedule. Migration archives: removal review 90 days after the verified switch; a stalled switch is reviewed every 30 days. A rights request may require earlier scoped action.
Minimal closed rights/appeal tickets: 12 months after closure/completion. Tickets contain necessary request evidence, not a full health export. This is distinct from retaining an entire ordinary email thread.
Closure, suppression and identity-link evidence: while required to keep recoverable copies or delayed writes from reviving records or choices, with quarterly minimization review. No final purge date or anonymity claim is made.
Device caches, recovery files and user downloads: until explicitly removed on the relevant device or by their independent holder. Signing out is not an erase-all action.
Hosting/authentication/email security logs and provider recovery copies: according to verified configuration, service need, account-specific provider terms and applicable deletion obligations. Some reviewed windows are known: the reviewed Free D1 plan has a seven-day Time Travel window, and Workers Free Logs has three-day retention if enabled at this review date. The source check did not enable application request logs; this is not a period for all Cloudflare security records. Firebase documents sign-in IP logs for a few weeks and authentication-data removal from live/backups within 180 days after customer-initiated deletion. These provider statements and the final enabled plan/configuration require launch recheck; the internal archive schedule is not a universal provider erasure guarantee. D1 recovery, Workers Logs, Firebase retention.
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.
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.
Changes, security and children
HTTPS and account-scoped checks are documented safeguards; devices can hold offline records and unlocking a device can expose them. No system is risk-free. Material changes in purpose, recipient or optional use require an updated notice and any required fresh choice. The effective date will be added only after the final launch notice is adopted.
The intended service is 18+. If a minor’s information may have been supplied, contact privacy@ascentmode.app. No health history is needed in the first message.
Consumer health privacy · Delete account & data · Cookies & preferences · Contact the operator
We use Google Analytics and GoDaddy to understand website visits. Choose whether to allow optional analytics cookies. Google also receives cookieless measurement pings before consent or after decline. Hosting and form protection have separate purposes. Read Cookies & preferences and Privacy.