Consumer Health Data Privacy Policy

Scope and categories

This separate notice covers Cheetah Run consumer health data where applicable, including Washington and Nevada. Read it with our general Privacy Policy. Account-linked fitness settings, training goals and progress, workout title and date, duration, distance, pace, completion, activity type, normalized route shape and related fitness inferences can be personal or consumer health data. They are not anonymous merely because a name is absent. We do not guarantee that a route shape cannot identify a familiar route. Optional pairing may record another person's device name.

Sources and purposes

Sources are information you enter and measurements produced on your device when you request workouts and optional features. The current iPhone app uses location during a run and its immediate summary; its saved workout format contains normalized x/y geometry, not latitude/longitude. It does not import your existing Apple Health records. We use necessary information to provide the account, training plan, recording, progress and sync services you request, operate security, and fulfill separately approved assistant requests. Current core plans are rule-based; fitness guidance is not diagnosis or treatment.

Sharing categories and recipients

Our infrastructure processors are Supabase (authentication/database in our US project, us-east-1) and Amazon Web Services (app/connector request processing in ap-northeast-2, South Korea). They process the data to provide these services on our behalf. We do not sell consumer health data, use it for third-party advertising, or provide it to external assistants for our own model training.

If you separately approve a named external assistant connection, that recipient can read your requested training schedule, progress and workout-history/statistics summaries. The connector does not provide email, profile name, GPS route points or a partner's name through its training tools. A provider may separately ask for identity OAuth scopes; those are shown during its authorization flow. Its own terms govern copies it receives. There are no corporate affiliates receiving consumer health data in the current app data flow. Apple Health receives completed workouts only if you grant permission; optional nearby pairing exchanges information with the person you choose to run with.

Consent, withdrawal and rights

Necessary processing is used to provide the services you request; this is not a blanket exemption from privacy law. Assistant sharing requires a separate approval. Device permissions and the app's safety acknowledgement are not consent to every optional health-data use or a waiver of rights. We will request appropriate permission before a new optional purpose or recipient requires it.

Cheetah Run works without an external assistant. Grok connection is optional; review the training information and purpose before approving. Its received copies are governed by the Grok privacy policy; use its privacy request portal or contact us for deletion help. We handle deletion from our systems and required follow-up notifications under applicable law. We cannot directly erase a recipient's systems or guarantee that disconnecting automatically deletes received copies. The availability of a request portal is not confirmation of receipt or deletion for a specific request. Your legal rights and our obligations remain.

At info@cheetahrun.xyz, request confirmation of collection or sharing, access/a copy, correction, deletion, or withdrawal of consent for future optional collection or sharing. Specify the request and account used, but do not send medical documents or your password. We may use proportionate verification and will explain any denial. Applicable state rights and response periods apply. To appeal a denial, reply with “Privacy appeal”; we will review it and provide a written outcome. You may contact your state's attorney general or regulator, including the Washington Attorney General or Nevada Attorney General.

Turn off optional device permissions in iOS Settings; disconnect an assistant in that assistant or on our connector management website. Revocation stops future API access, not copies already received. Request deletion of those copies from that recipient, or contact us for help identifying it and forwarding a request where applicable. To stop account-based recording/sync, stop using those services or use Me → Delete account in the latest app. Deleting the app alone does not delete the account. Health workouts already saved in Apple Health are managed there. Necessary legal retention and backup limitations are described in our general policy; withdrawal alone does not retroactively erase retained records.

Security and health-law boundaries

We use authenticated access, encrypted network connections and KMS-protected encryption of synced fitness contents. Login-to-random-data identity mapping is held separately in AWS; the server can decrypt authorized requests, so this is not end-to-end encryption or anonymity. Updated app builds also encrypt account caches and pending uploads with device-only keys; older builds must be updated. Unsynced records require the original device key. Minimal deletion controls prevent backup restoration from resurrecting deleted contents; provider and recipient copies may remain subject to their retention. See the general policy for details. Security measures reduce risk but do not promise perfect security. Cheetah Run is a consumer fitness service, not a medical provider; this does not exclude its data from consumer-health privacy protections. HIPAA applicability depends on the service and relationships involved, not a disclaimer. We do not claim HIPAA certification.