Consumer health data privacy

A separate explanation of training, body information and fitness-related sharing.

​

Future launch notice · Draft for review.

​

Prepared October 10, 2026. This is proposed wording for the intended standalone service and is not effective on the existing app. Final service providers, supported jurisdictions, affiliate facts and legal review remain launch decisions. The published marketing website does not connect to an Ascent Mode account or read workout or body records; see the general privacy notice for website inquiries.

​

On this page: Health-related fields · Crew sharing · Rights and requests.

​

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.

​

Operator: Ascent Mode, LLC, Florida, United States. Requests/appeals: privacy@ascentmode.app, including when you cannot sign in. A website visit does not read training/body records, but hosting/CDN requests still involve technical processing. See the general website and app notice.

​

Categories & purposes · Sharing & recipients · Requests · State rights & appeals.

What information is involved, and why

  • Training and context: routines/exercises, workout dates/times and corrections, sets, loads, reps, effort/recovery, notes and goals support your requested training record and comparable history.
  • Generated/inferred training information: suggested targets, reasons/limitations, estimates, comparisons, progression decisions/override reasons and weekly reviews support the guidance you request. They are interpretations of available records, not clinical findings.
  • Optional body/health records: supported measurements and associated source/app/device names, identifiers, modification/sync times, duplicate decisions and connection preferences support your chosen body record and synchronization.
  • Fitness participation: completed workout dates/day totals, challenge membership/status, points/rank, high-fives, rewards and selected cards support the optional social features you choose.
  • Account-linked activity events: optional app analytics can reveal workout/set, progression, Crew and other fitness-app use through event names, identifiers and times, even without raw performance/body values. They support feature/reliability analysis only after a separate current choice.
  • Associated identifiers and choices: account/source identifiers, invitation/eligibility and privacy-choice evidence can connect information to you and support authorized access, verification, requests and suppression.

​

Sources include your entries, reviewed imports, separately authorized supported health connections, authenticated original-service transfers, recipient interactions and Ascent’s calculations/service records. Device screenshot recognition saves confirmed measurements rather than the screenshot. Exact enabled native categories must match the final release build.

​

Optional measurement categories in the reviewed body-record model

​

You choose which records to enter or confirm; the model does not mean every field is collected automatically or available through a phone integration. These can include:

​

  • Core/circumference: weight, BMI, body-fat percentage, waist, hip and waist-to-hip ratio.
  • Composition: fat mass, fat-free/lean mass, subcutaneous fat, visceral-fat level/area, bone/mineral mass, protein percentage, and fat-free/fat-mass indexes.
  • Water: body-water percentage/mass, total/intracellular/extracellular water and ECW/TBW ratio.
  • Muscle: skeletal-muscle percentage/mass, muscle mass, dry lean/body-cell mass and skeletal-muscle index.
  • Metabolism/report fields: basal metabolic rate, metabolic age, standard weight and weight/fat/muscle control values.
  • Cardiovascular: heart rate and cardiac index.
  • Scores/classifications: body/InBody scores, obesity degree/level, muscle-storage level, phase angle and body type.
  • Segmental: lean/fat mass or percentage and impedance, with region/side/qualifier where provided.

​

These are stored readings/report labels, not an Ascent diagnosis. Source labels for a scale/body report are not a claim of a direct vendor integration. Final native permissions and enabled upload categories must be verified separately before release.

​

Collection choices

​

Core records are used for the service you request. Optional body uploads, health connections and optional analytics have separate explanations/choices. A phone permission or a policy/terms acknowledgment is not general authorization for new purposes. Revoking a supported connection stops future authorized uploads; it does not erase earlier imports or original Apple Health/Health Connect records. You can request narrower record deletion as well.

​

Where applicable law requires consent rather than requested-service necessity, the collection basis and any fresh choice must be implemented before that use. Optional health-related analytics and sharing are assessed separately from essential operation.

Shared categories and recipient roles

  • Cloudflare Workers/D1, service/storage processor: account-linked training, body, generated context, participation, privacy/service records and optional usage events necessary for its configured app role.
  • Firebase Authentication, identity/security provider: identity, credentials/session and security metadata; Ascent’s sign-in integration does not send raw workout/body values.
  • Sole Ascent operator, support/rights operations: restricted names/emails/choices, workout completion summaries, participation/referrals and request evidence. Normal operator reports exclude loads, reps, private notes and body values; any necessary sensitive rights follow-up uses a scoped private route.
  • Google Workspace, business communications/controlled records: inquiry/request correspondence and restricted operational registers/archives. Ordinary intake asks you to avoid health payloads.
  • Original-service host and controlled migration processors: retained original-service records and copies are handled through the same scoped requests, separately from the normal standalone sign-in journey.
  • Chosen friends/challenge participants or file recipients: only the audience and categories described in the Crew/sharing section below.

​

The reviewed inventory identifies no health-advertising, data-sale or CRM recipient for app health/usage records and no named affiliate recipient. Actual corporate affiliate status and any affiliate receipt still require factual confirmation; this notice stays draft. Future native health/store/notification providers are not described as enabled recipients without release evidence.

​

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.

Sharing choices are separate from collection

Joining a challenge, sending an invitation or sharing a file/card selects a defined audience; storing your workout does not authorize every sharing use. Review what the recipient can see before the action. Required health-sharing consent, where applicable, is distinct from collection consent; requested-service necessity is assessed for the specific action. Pausing, blocking or leaving stops future relevant participation/alerts without recalling independently captured files.

​

Optional fitness activity analytics

​

Account-linked events include app/setup, routine/import, workout/set, target-response/review, synchronization, Crew interaction and browser-reliability activity. They carry account/event identifiers, allowed restricted context, occurrence/receipt timestamps and an ephemeral browser session UUID. They are not anonymous. Cloudflare stores them for Ascent’s product/reliability analysis; raw loads/reps/measurements, notes, name/email, phone-health payloads and advertising identifiers are excluded. See the exact emitting event inventory and withdrawal behavior.

​

Health-permission telemetry and native first-party diagnostics are disabled in the reviewed configuration. A consent choice is separate from training settings, marketing, phone permissions and website cookies. Turning off optional analytics removes stored owned usage events and clears available queues when withdrawal is observed; a concurrent in-flight request and controlled backups require the follow-up described in the general notice. Necessary security/service records and real Crew/workout records are separate.

Retention for health-related information

Training/body/generated context remains until the relevant record/account is removed; optional live usage events have a 90-day cleanup rule and are also removed on withdrawal/account deletion. Minimal suppression/closure/source evidence remains only while needed to prevent recovery/reimport, with quarterly minimization review. Operator CSVs, encrypted archives and rights tickets follow the distinct seven-day, 30-day and 12-month operating schedules; migration archives receive removal review 90 days after a verified switch. These are category rules, not a verified universal processor-backup deadline. Read the full retention schedule and hold criteria.

​

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.

​

Applicable state rights and complaint routes

​

The final supported-state list is a launch decision. The provisions below describe the rules when the relevant law covers the service and your request; they do not represent admission to every state.

​

Washington, where applicable

​

You may confirm/access consumer health data, obtain required recipient/affiliate information, withdraw collection/sharing consent and request deletion. Requests must be complied with within 45 days of receipt; authentication does not reset that clock. One additional 45-day extension is allowed when reasonably necessary, with timely notice and reason during the initial period. Appeals receive a written response within 45 days of receipt. A denied appeal includes a complaint route to the Washington Attorney General.

​

Applicable downstream recipients must be notified and honor deletion. A backup/archive delay is allowed only to enable restoration and is capped at six months after authentication; it is not Ascent’s ordinary retention period. Washington rights, appeals and deletion rules; Washington Attorney General complaints.

​

Nevada, where applicable

​

You may request confirmation, the required third-party list, cessation of collection/sharing/sale and deletion. General responses are due without undue delay and within 45 days after authentication, with one reasonably necessary additional 45 days and timely notice/reason. Deletion has a separate 30-day requirement after authentication; notified downstream recipients must delete within 30 days after notification.

​

Appeals receive a written response within 45 days after receipt; a refusal includes the Nevada Attorney General’s contact. The restoration-only backup/archive allowance is capped at two years after authentication. That statutory outer allowance is not a promise to keep your records for two years. Nevada consumer health rights; Nevada Attorney General contact and complaint instructions.

​

For other applicable jurisdictions, we identify the relevant deadline and complaint route in the response. Our two-business-day acknowledgment and 30-calendar-day working targets do not replace these legal duties.

​

Account & data requests · General privacy notice · Privacy contact