health-mcp privacy policy
Last updated 17 October 2026.
Who this covers
health-mcp is a personal tool. Dave Pretty wrote it and is its only user, and it works only with his own Google account. This policy explains what it does with the data Google Health shares with it.
What data it accesses
With the account holder's consent, it gets read-only access to three kinds of Google Health data:
- Activity and fitness: exercise sessions, steps, distance, active zone minutes and VO2 max.
- Health metrics and measurements: heart rate, resting heart rate, heart rate variability, weight and body fat.
- Sleep: sleep sessions and sleep stages.
Separately, and with its own consent, it can add nutrition logs (meals and drinks) to the account holder's Google Health data. Each log holds a food name and portion, the time and meal, and estimated energy, carbohydrate, fat, protein, fibre and caffeine. It can change or delete only the logs it added itself, and it can't read nutrition data.
It can't write, change or delete any other Google Health data.
How the data is used
It's used only to answer the account holder's own questions about his training, activity and health, and to record the meals he chooses to log. It runs on his own computer. It isn't used for advertising, isn't sold, and isn't used for credit, lending, medical device or research purposes.
Who the data is shared with
Data goes straight from Google to the account holder's computer. There's no server or database behind health-mcp. If the account holder asks his AI assistant (Claude, made by Anthropic) a question, the data needed to answer it goes to that assistant as part of the conversation. That happens only at his request. Nutrition logs are sent to Google Health only when he logs a meal. The data isn't shared with anyone else.
Storage and security
The OAuth credentials (the client secret and two refresh tokens, one read-only and one for nutrition logging) are kept in the account holder's macOS Keychain. Access tokens are held only in memory. health-mcp doesn't keep its own copy of the health data it reads. All traffic to Google uses HTTPS.
Revoking access and deleting data
Access can be revoked at any time from the Google Account's third-party connections page, or by running the tool's logout commands, which revoke the tokens and remove them from the Keychain. Nutrition logs it added stay in Google Health until the account holder deletes them, which the tool's delete command can do. health-mcp holds no other user data, so there's nothing else to delete.
Google API policy
The use of information received from Google Health API and/or Developer Tools will adhere to the Google Health API Developer and User Data Policy, including the Limited Use requirements.
← health-mcp