Privacy policy
Last updated: 25 October 2026
HealthOS is a personal macOS application that helps its owner view activity, sleep and everyday wellbeing records. This policy explains how the application and this public information website handle data.
1. Who is responsible
HealthOS is operated as a personal-use project by the developer reachable at lecreati@gmail.com. The application is not a Google or Fitbit product.
2. Google data the application accesses
With the account owner’s consent, HealthOS requests the following read-only Google Health permissions. Availability depends on the connected account and device. It does not write changes to Google Health.
| Permission | Purpose |
|---|---|
| Activity and fitness | Display recorded steps, distance, energy, active time and workouts. |
| Health metrics and measurements | Display available measurements, including weight, heart rate and overnight signals. |
| Sleep | Display sleep sessions, duration and stages where provided. |
| Profile | Check that the authorised account is linked to Google Health. |
The application also stores information entered or confirmed by its owner, such as nutrition targets, meals, weight and practice sessions. Manual practice confirmations are kept separate from wearable workouts. Previously imported records may remain in the owner’s local history after an integration is disabled.
3. How the information is used
Records are used to display personal history, trends and tracking views, maintain the local database and create the owner’s backups and exports. Missing measurements are not presented as measured zeros. HealthOS is not intended for diagnosis or treatment.
Google user data is not sold, used for advertising, used to build advertising profiles, or used to train general-purpose AI or machine-learning models. HealthOS’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
4. Storage and services
The current macOS build stores its working database, OAuth token files, local backups and exports on the owner’s Mac. Access to local files is limited by the Mac account’s file permissions. The owner is responsible for the security of the device and any copies they create.
A local export may be made available to the owner’s Lucy OS workspace. This does not publish the data on this website. Google Drive and Google Sheets storage is being configured as a separate, owner-authorised integration; it is not automatically enabled by visiting this site or by granting Google Health access.
The current installation has automatic Notion import disabled. Disabling an integration does not automatically erase records that were already imported.
5. Sharing
Google handles account sign-in, consent and the authorised API requests under its own policies. HealthOS does not publish the owner’s health history or share it with advertisers. An export to a cloud service requires the owner’s instruction and must use the account and destination the owner selects. The final cloud integration’s data flow will be documented before it is enabled.
HealthOS does not include an automatic transfer of Google Health records to a cloud AI provider. The owner’s separate use of an assistant or export service is subject to the access they grant to that service.
6. Retention and deletion
Local records are kept until the owner removes them. The owner can revoke Google access through Google Account third-party connections. Revocation stops future authorised access; it does not delete copies already stored on the Mac.
To remove stored records, the owner must remove the relevant local database, exports and backups. Each backup or export is a separate copy. Any copies the owner later saves to Drive must also be deleted there, including from its trash where permanent deletion is intended. See Data controls or contact the developer for assistance.
7. This public website
This is an informational website. It has no health-data upload, account sign-in, app download, contact form or advertising integration. It does not receive Google Health records or OAuth tokens. Fonts and brand images are served with the website; it does not load a third-party analytics or tracking script.
Cloudflare hosts this site and may process technical connection information, such as IP addresses, request times, requested URLs and browser information, to deliver and protect the service under its privacy policy. Contacting support by email sends the information you choose to include to the developer’s mailbox. Please do not email health records or credentials.
8. Changes and contact
This policy will be updated when the application’s data practices change. The date at the top identifies the current version. For access, deletion, privacy or support questions, contact lecreati@gmail.com.