Effective October 2, 2026
Privacy policy
This policy describes the personal deployment called Fitbit MCP Local and this informational website. The service is operated by its account owner for personal use and is not open for public registration.
Information accessed and purpose
After the owner authorizes access with Google, the connector can read the profile, settings, activity and fitness, sleep, nutrition, and health metrics and measurements covered by that authorization. Availability depends on the account and connected devices. Information is used to answer the owner's requests, generate summaries, and provide personal wellness context.
Storage and security
OAuth client configuration and access and refresh tokens are stored on the owner's private server with owner-only file permissions. Tokens authorize API requests and are not returned as MCP tool results. The remote connector requires authentication and exposes selected read-only tools.
The current deployment has its optional health-response cache disabled. User-entered wellness preferences may be stored locally by the connector. Requests necessarily process data in memory; operational systems may retain diagnostic metadata. The owner should avoid putting health records or credentials in diagnostic logs or source repositories.
Sharing and service providers
Google supplies the authorized health data. Cloudflare provides the hosting and connection infrastructure used by this deployment and may process requests and operational metadata. When the owner uses an AI client, requested health information and summaries are delivered to that client and its provider. Its own privacy settings, retention rules, and terms also apply; this connector cannot delete copies retained by those providers.
The operator does not sell Google user data or use it for advertising. Use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. The connector does not itself train machine-learning models on health data.
Website visitors
These public pages contain no health records, account forms, advertising, or application analytics scripts. The hosting provider may process IP addresses, request details, and security logs to deliver and protect the site.
Retention, revocation, and deletion
Authorization tokens are retained on the private server until replaced or removed. The owner can revoke this app's access through Google Account connections and remove local connector credentials and any stored preferences or cached data. Revocation prevents subsequent authorized retrieval but does not delete the original records held by Google or copies already shared with an AI provider. Those copies must be managed through the respective provider.
Contact and changes
The account owner administers this personal deployment. Anyone explicitly invited to use it should direct access or deletion questions to the operator through the same private channel used to arrange access. This policy will be updated if the deployment's data practices change.