Your data stays scoped.

This personal MCP is operated by Emmett Shaughnessy for Emmett alone. It is not a public health application and does not make medical diagnoses.

What is stored

Google sign-in identity, Google Health consent status, encrypted OAuth tokens, explicit write audit records, persistent notification freshness metadata, and short-lived encrypted copies of exact Google Health API responses.

How it is used

Data is used only to answer authenticated MCP requests, perform explicit user-requested nutrition, hydration, or measurement writes, and report when Google says new data is available.

Retention and sharing

Cached health responses expire within their configured minutes and are physically cleaned up daily. Update pointers expire after seven days; webhook delivery records after 30 days. The server does not sell health data. Data returned to an authorized MCP client is then subject to that client's own terms and retention settings.

Control

A signed-in user can disconnect Google Health or permanently delete all Google Health domain data stored by this server from the account page. Those actions do not delete data held by Google, Fitbit, or an MCP client.

Return to account