Data handling
Privacy Policy
Effective 9 November 2026. This policy covers ghealth, an independent personal-use command-line tool maintained by Dhruv Kelawala, and this informational website.
What the tool accesses
With your permission, ghealth reads your Google Health identity and the health records available under these three scopes:
- Sleep:
googlehealth.sleep.readonly. - Health metrics and measurements:
googlehealth.health_metrics_and_measurements.readonly. - Activity and fitness:
googlehealth.activity_and_fitness.readonly.
These permissions support sleep sessions and stages, HRV, resting heart rate, steps, heart-rate samples and exercise. Availability depends on your account, device, consent and Google’s processing. ghealth does not request permission to change or delete your Google Health records.
How data is used and stored
The CLI uses records to maintain a local history and calculate summaries and trends. Records and collection metadata are stored in an AES-256-GCM encrypted file on your Mac. OAuth credentials, account binding and the encryption key are held in macOS Keychain. Client configuration stays on your machine. Encryption at rest does not protect an already compromised user account or information deliberately exported in plaintext.
Sharing and assistant integrations
The CLI contacts Google for authorisation and read requests. It does not automatically upload your health records to the developer, this website, an analytics service or an AI provider. ghealth does not sell health data, use it for advertising, or use it to train AI models.
You may choose to export data or connect ghealth output to other software, including an assistant. Exported files and command output can contain private health data. If you or an integration sends output to a remote service or model provider, that recipient receives it under its own policies. Keep the amount disclosed to the minimum you have chosen to share.
Retention, revocation and deletion
Local records remain until you remove them; there is no automatic retention-deletion schedule. Re-syncing a date range replaces successful records for that range, while failed requests can retain previous records marked stale or unavailable. Backups and exports may hold additional copies.
You can revoke access from your Google Account’s third-party connections or use ghealth auth logout --revoke. ghealth auth logout removes the CLI’s local OAuth session but intentionally retains the encrypted cache and its key. To erase the local history, remove the tool’s state directory and its matching cache-key item in macOS Keychain; remove any exports and backups separately. Contact the maintainer for help identifying the correct local items. The developer cannot remotely erase files on your machine.
This website
This is a static informational site. It has no health upload form, account system, advertising trackers or analytics scripts. Its hosting and network providers may process ordinary web-request information, such as IP address, user agent, request time and requested URL, to deliver and secure the site under their own policies. Do not send health records or credentials by email.
Google API data commitments
ghealth’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. Health information is used only for the user-facing personal summaries and integrations you authorise, not for advertising, data brokerage or AI-model training.
Contact and changes
For privacy questions, contact Dhruv Kelawala. Changes to this policy will be posted here with an updated effective date. Material changes to data use require appropriate notice and consent before they take effect.