Deleting your Cadence Lift data

Cadence Lift works without an account; optional Communities use a separate account. Most workout data exists only on your device, so you control its deletion directly. Optional Coach processing, community content, historical hosted links, health-store records, and old iCloud archives have separate lifecycles described below.

Request community account deletion without the app

To request deletion without reinstalling the app, email [email protected] with the subject Cadence Lift community account deletion. Say that you want your community account and associated shared content deleted. Include your display name and community name if known so we can identify the account. Do not email a recovery code, device-linking code, or web sign-in code. We will reply within 7 days with the verification steps and any organizer ownership steps needed before deletion. The retention details below still apply.

1. Delete Cadence data on your device

• Android: uninstall Cadence, or open Settings → Apps → Cadence → Storage and choose Clear storage.
• iPhone: delete Cadence from the Home Screen or App Library.
• Individual Coach chats: delete them from the in-app Chats list without deleting the rest of the app.

This removes the local workout database, templates, body measurements, reminders, preferences, Coach profile and chats, and the ordinary local installation identifier. Export a JSON backup first if you want to keep a user-owned copy.

2. Community accounts and shared content

In Communities, you can remove your own messages, posts, comments, shared workouts and shared cardio workouts at any time. Deleting a post removes its discussion. Leaving or being removed from a group removes your messages, posts, comments, kudos and shared workouts from that group. Turning off participation does not delete content already shared. Organizers must transfer ownership or delete their group before leaving it.

A web link to a post expires after seven days or when the shared content expires, whichever is sooner. You can revoke your own links sooner, and deleting the post or turning off the related sharing choice invalidates them. Revoking a link cannot remove copies other people saved.

To sign out a web browser, open Account & devices in Communities and use Web sign-ins to sign out one browser or all of them. Signing out the phone that approved a browser also signs that browser out. Browser sessions otherwise end after at most 30 days, or 14 days without use.

After leaving all groups, withdrawing joining requests, and dismissing unavailable memberships, choose Delete community account in Communities. This removes active credentials and the membership index and signs out every browser, while keeping local workouts. Minimal identifiers, deletion-retry credential hashes and operation-ordering records remain without automatic expiry to prevent identity reuse and unsafe retries. Messages, posts, comments, shared workouts and shared cardio workouts otherwise expire after 90 days; groups retain at most 500 messages, 500 text posts, 500 shared workouts and 500 shared cardio workouts. Reports to an organizer expire after 90 days. Reports directly to Cadence stay open until reviewed; their details expire 90 days after resolution or a follow-up. If Cadence has paused a group, the case and group IDs remain until the pause is lifted.

Signing out or uninstalling does not delete community memberships or server-held content. Other members may have saved copies that Cadence cannot remove. Keep your private recovery code to regain access before deleting an account; never email that code, a device linking code, or a web sign-in code.

3. Delete health-store records

Deleting Cadence does not automatically delete records already written to Apple Health or Health Connect. Remove those records in the applicable health app and revoke Cadence's permission there if you no longer want it to read or write supported data.

4. AI Coach copies

Deleting a local chat removes the device copy. Cloudflare is instructed not to store raw Coach request or response text; it keeps operational metadata. Coach messages go to Anthropic's Claude API. If Claude cannot answer, Cadence does not send the request to another AI provider. Anthropic deletes the prompt and reply within 30 days by default. Content its safety systems flag may be kept for up to 2 years and safety classification scores for up to 7 years; longer retention may apply when required by law.

Cadence does not currently have an established mechanism to locate or delete Anthropic's copy early. The in-app Support ID is not forwarded to Claude and cannot identify that copy. It expires under Anthropic's policy. We will not claim that emailing support can erase provider-held content when we cannot prove that action.

Earlier Coach requests processed by Google's Gemini before the Claude-only change remain subject to its prior retention policy: Google may keep that content for up to 55 days for abuse monitoring. This change does not delete those earlier copies, and Cadence cannot locate or delete them early using your Support ID.

5. LightPath-controlled technical records

Installation-ID and IP rate-limit counters expire within their hour or day window. App Attest public-key and counter records may persist to verify later requests. If you voluntarily email support, include the Support ID from Settings → Contact when asking about LightPath-controlled support or installation-ID rate records. The Support ID cannot locate Anthropic's Coach copy or a separate App Attest key record.

6. Historical hosted workout links

Cadence 1.2 cannot create new hosted workout links. A link created by an earlier build remains accessible to anyone who has it until automatic expiry: about 30 days after its last view and no later than 90 days after creation. You may email the exact URL to support for investigation, but do not send other private workout data unnecessarily.

7. Legacy iCloud archive — iPhone only

Cadence 1.2's migration screen is read-only: it can recover an archive made by Cadence 1.1.x, restore it locally, and let you export JSON, but it does not create, replace, or delete the private CloudKit record. The record remains in the user's private Apple database while LightPath obtains and follows Apple's guidance for cleanup and removal of the temporary recovery bridge.

8. Contact

For questions or an action involving records LightPath actually controls, email [email protected]. Include the Cadence Support ID only when relevant. We may need additional information to identify the exact record and will explain when a requested action is technically unavailable or belongs to Apple, Google, or another provider. We reply within 7 days and complete any action we can take within 30 days.

For the complete inventory, see the Cadence Lift Privacy Policy.