Privacy policy

1. Scope of this policy

This policy applies to GymOS Local Health Reader, a private, single-user health and fitness application. The application is not offered for public registration and does not operate an advertising or data-broker service.

The application uses Google OAuth to access selected Google Health and Fitbit information only after the authorised user grants permission. All permissions requested by GymOS are read-only.

2. Information accessed

Depending on the records available in the connected account and the permissions granted, GymOS may access activity and fitness records; exercise sessions and routes; heart rate and heart-rate variability; oxygen saturation; respiration; temperature; glucose; ECG records; irregular-rhythm notifications; sleep; nutrition and hydration; weight and other body measurements; fitness estimates; profile information; settings, units and paired-device information.

GymOS also records technical provenance needed to maintain an auditable import, such as source identifiers, retrieval times, file sizes and cryptographic hashes. It does not request permission to write to, modify or delete data in Google Health.

3. Why the information is used

Google Health information is used only to provide and improve the authorised user’s private health and fitness features. These include longitudinal training and recovery review, sleep analysis, nutrition reconciliation, body-measurement trends, personal journalling, source verification and the preparation of private reports.

GymOS is not a medical device and does not use the information to diagnose, treat or prevent a medical condition. Its outputs are personal information-management and fitness-analysis aids.

4. Storage and security

The primary imported archive and derived reports are stored in access-controlled local storage operated for the sole authorised user. OAuth credentials are held separately in the macOS Keychain. Access permissions are restricted to the local owner account, and data is not placed in the public website.

When the user asks for AI-assisted analysis, selected records, excerpts or derived summaries may be processed through OpenAI’s Codex or ChatGPT services. Those interactions are governed by the terms, privacy policy and data controls applicable to the user’s own OpenAI account. The complete raw archive is not intentionally published or made available through this website.

The public pages at this domain contain no Google Health records and do not provide a route for visitors to sign in. Reasonable technical and organisational controls are used to protect locally held information from unauthorised access, alteration, loss or disclosure.

5. Sharing, transfers and advertising

GymOS does not sell Google Health information. It does not share that information with advertisers, data brokers, information resellers or credit providers, and it does not use the information for advertising, retargeting or profiling.

OpenAI is the only routine external processor used by GymOS, and only selected information needed for the user-requested conversational analysis is sent to its Codex or ChatGPT services. No other routine third-party transfer is part of GymOS. Any additional transfer would occur only if required by law, necessary to address a security incident, or explicitly authorised by the user to provide a clearly disclosed feature.

6. Retention and deletion

Imported source records are retained locally while they remain useful for the authorised user’s longitudinal history, auditability and personal analysis. Derived outputs may be rebuilt from retained sources.

The authorised user may request deletion of imported Google Health data and associated derived outputs at any time. Deletion is performed from the local archive and working system, subject only to preserving a temporary verified recovery copy where needed to prevent accidental loss during the deletion process. Any such recovery copy is then removed when verification is complete.

7. Managing or revoking access

The authorised user can review or revoke GymOS access from the third-party connections section of their Google Account. Revocation prevents future API collection but does not automatically erase records already imported into local storage.

To remove locally held information, the authorised user can contact the developer using the support contact shown on the Google OAuth consent screen. Because this is a private single-user application, the user may also direct deletion through the normal GymOS interface.

8. Google Health Limited Use

GymOS’s use and transfer of information received from the Google Health API and Developer Tools adheres to the Google Health API Developer and User Data Policy, including its Limited Use requirements.

9. Changes

If GymOS changes the categories of Google user data it accesses or uses that data for a new purpose, this policy will be updated before that new use begins and the user will be asked to consent where required. The effective date below identifies the current version.