Ascend V2 stores workouts on your device. Account creation, sign-in, and workout cloud backup are unavailable in this release. This policy explains what stays on your device, data from accounts made in earlier builds, optional tips processed by Apple and RevenueCat, the Apple Health data Ascend can read with your permission, and limited crash diagnostics. For rules on using the app itself, including exercise and injury disclaimers, see the terms of use.
Accounts made in earlier builds
V2 has no account creation or sign-in. If you made an account in an earlier development or test build, Supabase may still hold your account user ID, email address and profile display name when provided, and account records needed to process deletion. Disabling sign-in does not delete those records. Account sign-in alone did not upload or restore workouts, plans, or settings. Data created in earlier builds that enabled cloud backup may still exist separately; contact support about it.
V2 cannot delete an earlier account in the app because sign-in is unavailable. Follow the account deletion instructions to request deletion through support. Deleting an account does not erase workout data stored on your device.
Optional tips and purchases
You may send a repeatable, one-time tip through Apple's in-app purchase system. Tips are optional, require no Ascend account, and unlock no feature or entitlement. Apple determines and displays the localized price and processes payment. Ascend does not receive your payment-card or bank details.
RevenueCat handles purchase validation and transaction history for Ascend. Its purchase processing can include the tip product identifier, transaction identifier, purchase date, storefront and currency information, and app/device information needed to operate its SDK. RevenueCat assigns an anonymous customer identifier in V2. Earlier signed-in tip records may include an account ID. A local tip record can also hold product and transaction identifiers. Account deletion does not itself remove Apple's or RevenueCat's transaction records.
Data stored on your device
Your workout plans, workout sessions, completed sets, weights, reps, exercise history, goals, settings, and workout profile preferences are stored locally. This release has no workout cloud backup and does not upload full workout records. If PostHog is configured and sharing is enabled, limited workout activity events and counts can leave the device as described below. Earlier account profile data, purchase records, and diagnostics are separate categories of data.
If you use the companion Apple Watch app, current workout state can pass directly between your paired iPhone and Apple Watch through Apple's device-connectivity service. We do not receive it. Deleting Ascend removes its locally stored app data, subject to operating-system backup behavior.
Health and fitness data
On iOS, Ascend requests read access to exactly six Apple Health data types:
- Step count
- Heart rate
- Active energy burned (active calories)
- Walking and running distance
- Cycling distance
- Swimming distance
Access is off by default. Ascend asks only after you enable health metrics and Apple displays its permission prompt. Steps, heart rate, and active calories appear in activity summaries. Distance readings are used only to suggest a total after a matching walking, running, cycling, or swimming session; you can accept, replace, or ignore that suggestion.
Apple Health readings remain on your devices. Ascend reads them on demand and does not upload them to us, Sentry, or any analytics provider. If you accept a suggested step or distance total, that value remains in device-only activity history. Ascend requests no write access and writes nothing to Apple Health.
You can revoke access at any time in the iPhone Health app or in iOS Settings, or by turning health metrics off inside Ascend.
Crash diagnostics
Ascend uses Sentry to find JavaScript runtime crashes and serious data-loss failures. Native fatal-crash capture is disabled because those reports cannot pass through Ascend's JavaScript privacy filter. Sharing is off by default and controlled by More → Privacy → Share anonymous usage data. Turning that switch off stops new reports.
- A report can contain error type, code stack frames, whether the error was handled, app version and build, operating-system version, device model and architecture, and fixed diagnostic tags such as the affected screen or storage operation.
Before a Sentry error event is sent, Ascend rebuilds it from an allowlist. Error messages, breadcrumbs, console output, request URLs and bodies, headers, cookies, account or user context, screenshots, view hierarchies, local variables, attachments, and arbitrary extra fields are removed. Workout content, sets, reps, weights, exercise names, notes, goals, profile values, and Apple Health readings are not allowed into the transmitted event. Email addresses and credentials are also excluded.
Ascend includes optional PostHog product analytics. PostHog starts only if a production build contains a PostHog API key, and events are sent only when you turn on the same sharing switch. If enabled, PostHog can receive a pseudonymous SDK identifier, app use events (such as app opens, workout starts and completions, set logging, and tip completion), and limited event properties such as workout category, counts, duration, and tip product ID. Ascend does not identify a PostHog user with your account ID, name, or email, and its event filter excludes free-text workout content, Apple Health readings, and transaction IDs. The repository's production build profile does not set a PostHog key; the exact distributed build configuration must be checked separately. Ascend does not use an advertising identifier, cross-app tracking, session replay, or screen recording.
What we do not do
- We do not sell or rent your data.
- We do not share your data with advertisers, and there is no advertising in the app.
- We do not use advertising or attribution SDKs, and the diagnostics described above are not used for advertising.
- We do not build advertising profiles or track you across other apps and websites.
- We do not send full workout records or Apple Health readings to Sentry or PostHog. If PostHog is enabled, limited workout activity events and counts may be sent as described above.
- Account creation, sign-in, and workout cloud backup are unavailable in V2.
- We do not make tips unlock Premium or any other app feature.
Who processes your data
Apple processes optional in-app payments. Supabase may retain accounts created in earlier builds; V2 does not create or sign in to accounts. RevenueCat validates and records purchase transactions and uses an anonymous customer ID in V2. Earlier signed-in purchases may remain associated with an account. Sentry processes limited crash diagnostics while the sharing switch is on and a Sentry destination is configured. PostHog can process the limited anonymous usage events described above only if configured and you turn on that switch. We require service providers to protect data consistently with this policy and applicable law. Apple Health readings are not sent to either service.
Your choices and rights
- Delete an earlier account. Follow the support request instructions. V2 has no in-app account deletion control. Deletion does not erase local workouts or Apple and RevenueCat transaction records.
- Turn off sharing. Go to More → Privacy → Share anonymous usage data. New Sentry reports and, if PostHog is configured, new product-analytics events stop.
- Revoke Apple Health access. Use the iPhone Health app or iOS Settings, or turn health metrics off inside Ascend.
- Erase local workouts. More → Profile → Danger zone → Erase workouts on this device permanently removes local workouts and settings.
- Skip optional tips. Tips are never required. Consumed tips do not provide ongoing access to restore. Refund requests are handled under Apple's purchase rules.
- Ask about purchase records. Contact us for support. Apple and RevenueCat retain transaction records under their own legal and operational requirements.
- Ask about diagnostic data. Contact us using the details below. Diagnostic reports are not tied to an Ascend account, so we may be unable to identify a particular report as yours.
Depending on where you live, you may have additional rights over your personal data, such as access, correction, deletion, and portability. Contact us to exercise them.
Security
Workout data is processed locally. Apple Health readings remain on your devices. Optional purchases use Apple's payment sheet and RevenueCat's encrypted receipt-validation connection; Ascend does not handle payment-card details. Crash diagnostics use encrypted connections after Ascend's allowlist removes sensitive fields. No method is 100% secure.
Data retention
Local workout and preference data remains until you erase it in Ascend, reset the app, or remove the app, subject to operating-system backup behavior. Earlier account profile data remains until deletion is completed. A minimal Supabase deletion-request record, including the former account ID, request ID, provider, status, and timestamps, can remain after account deletion for retry and audit purposes. Sentry reports and, if enabled, PostHog events follow their configured retention periods. Apple and RevenueCat retain purchase records under their legal, fraud-prevention, refund, accounting, and operational requirements. Contact us for current operational retention details or an earlier deletion request, although anonymous diagnostic reports may not be identifiable as yours.
Children
Ascend is not directed at children under 13, and we do not knowingly collect their personal data. If you believe a child's information reached our crash diagnostics, contact us.
Changes to this policy
If this policy changes materially, the updated version will be published here with a new date, and the change will be noted in the app release notes.
Contact
Questions or requests: ksil.apps@gmail.com. You can also visit our support page.