Privacy policy

Current pilot and intended use

The current pilot uses the owner's authorization to make read-only Google Health requests for sleep data. It checks access and response structure. Health responses are processed in Google Apps Script.

The pilot does not currently write health records to a Sheet or perform scheduled syncing. Planned private Sheet syncing may include sleep, activity, heart rate, and weight when present. Those additional categories and features are not yet working.

Data and authorization storage

Sleep responses can contain health measurements, record identifiers, timestamps, and source metadata. The current pilot processes those responses in the Google-hosted runtime to check access and schema; it does not publish them on this website.

The pilot stores OAuth credentials and authorization tokens in the owner's Google Apps Script UserProperties and uses the corresponding UserCache for authorization handling. These are separate from this public site's files.

If private Sheet syncing is implemented later, health records would be stored in the owner's private Google Sheet. That storage is planned, not current pilot behavior.

Operational diagnostics

The pilot records limited operational diagnostics such as request status, record or page counts, and checks of whether expected fields and types exist. Its diagnostic output excludes health measurements, record identifiers, raw health responses, and credentials.

Google services may maintain their own operational records. This policy does not promise zero logging or a fixed retention period for those services.

Access and service providers

The project is intended for its one owner, not for collecting data from other users. Health access and processing use Google Health and Google Apps Script. A future private Sheet would also use Google services.

The public informational site does not receive health responses or authorization tokens. It has no login, health-data submission form, tracking script, or external asset dependency.

Stopping access and removing copies

The owner can stop running the pilot and revoke the app's authorization through their Google Account's connected-app settings. Revocation stops future authorized access; it does not delete existing copies of data.

Any retained credentials, diagnostic records, or future Sheet copies require separate review and removal in the relevant service. There is no automatic deletion interface or promised fixed retention period for this pilot. No health records have been imported into a Sheet by the current pilot.

Website hosting is separate

This static informational site is intended for GitHub Pages. Its source files are public. GitHub may process visitor metadata, such as IP addresses and request information, when serving the site, under the GitHub Privacy Statement.

Website visitor processing is distinct from the Google-hosted health pilot. Visiting this site does not grant access to a Google Health account.

Questions and updates

Non-sensitive privacy questions can be raised in the project issue tracker. This policy will need to be reviewed as the project changes.

Warning: issues are public. Never post health data, account information, credentials, tokens, or private document links.