Privacy

Local records and backups

Workouts, meals, photos, body measurements, self-reported recovery, profiles and plans, learning, self-checks and saved plan proposals are stored locally. The website uses the current browser’s local database; the native app uses private files on the device. There is currently no account or automatic cloud sync.

Meal photos are compressed and redrawn locally, with embedded metadata removed before saving. Original file names and paths are not retained. Photos are included in record exports and local backups.

Local records remain until you delete or clear them. Normal imports and resets retain the previous original data, and historical backups must be deleted separately. Deleting a current record does not delete its copies in older backups.

The current native app excludes its managed private records, cached health imports and pending Watch commands from automatic system backup. The app cannot guarantee exclusion or deletion of other browser or system backups, or files you export, download or save elsewhere. Keep exported files securely yourself.

Website connections and preferences

Opening the website, loading pages or checking AI availability requires network connections. The infrastructure providing the website and service processes information needed to establish those connections. This does not mean your local workout logs are uploaded. The website saves your language preference.

Hosting and operational services may retain connection or operational logs; clearing the app cannot delete those infrastructure logs. This notice does not promise a website without logs or describe local storage as having no network processing. Contact us below about the current deployment.

Optional AI: preview, then consent

When AI is not enabled, personal records are not sent to an AI provider. If the service is enabled, the interface shows its availability. Each request requires a preview of the actual information being sent and explicit consent. Changed information or scope requires a new review; consent does not automatically carry over to another request.

Depending on the purpose selected, a request may include plans, workout sets and repetitions, load and effort, your present recollection of past pain, activity duration and distance, self-reported sleep and recovery, meal groups and portions with optional food descriptions, equipment and scheduling preferences, your request text and safety answers. The preview for that request is authoritative.

Current requests exclude meal photos, raw Apple Health imports, complete body-measurement records and general record notes. Plan and record identifiers use request-specific aliases, but times, time zones, free text and health content may still identify a person. Aliases do not make a request anonymous.

The app’s operating service receives the request first, then sends the selected text to OpenAI to generate an answer. Read-only explanations remain in the current page’s memory and do not enter plan-proposal history; you can copy or download them. Only plan proposals you explicitly save enter local proposal history.

Canceling or withdrawing a request stops this page from accepting the result and attempts to abort the request. It cannot retrieve information already sent. Deleting a local proposal or clearing the app cannot delete copies already sent to a server.

OpenAI processing and retention

OpenAI’s public API policy says API data is not used for model training by default unless the operator opts in to sharing it. Default safety and abuse-monitoring logs may contain inputs and outputs and may be retained for up to 30 days, or longer in exceptional circumstances. Some models may retain prompt caches for up to 24 hours.

This service does not ask OpenAI to save response objects for later retrieval, but that does not mean zero retention or immediate remote deletion. Account-level settings and exceptions affect actual processing. This notice does not assert that the service has zero-retention eligibility or that all account-level data settings have been verified.

Read OpenAI API data controls

Apple Health, Watch and system permissions

With your permission, iPhone reads steps and body weight and writes completed workouts after an explicit action. Health imports and manual logs remain separate and are not automatically added together. An empty health result does not necessarily mean no activity or denied read permission.

Watch can display heart rate for the current workout and send record commands; iPhone performs the record writes. While Watch is offline, one pending command may remain until reconnection checks the new state or you discard it. Old input cannot write back into newly cleared records.

You can revoke health permissions in system settings. Revocation does not automatically delete copies already imported into the app. Clearing the app does not revoke system permissions, delete original Apple Health records or remove workouts already scheduled in the system.

Deletion, full clearing and external copies

Use Settings and Data to export records, manage recovery backups or explicitly confirm full clearing. Full clearing removes app-managed records, embedded photos, profiles, proposals, historical backups and native cached health imports in the current environment. It also discards old drafts and AI answers on open pages. A normal reset retains recovery backups and has a different scope.

Clearing applies to app-managed data in the current browser or device; it is not a remote wipe. It does not delete downloaded or separately saved files, data in other browsers or devices, original Apple Health records, system permissions, scheduled system workouts or information retained by providers. Manage external copies separately.

Open Settings and Data

Privacy questions and contact

For questions about the current service configuration, access, deletion or the scope of this notice, contact: [email protected]

View Support