null

Personal Google MCP - Privacy Policy

Personal Google MCP - Privacy Policy

Effective November 14, 2026.

Personal Google MCP (the "App") is a private connector used only by its owner, Jonathan Raabe, to work with his own Google account through an AI assistant. It is not a public service and has no other users.

Data the App accesses

When the owner signs in with Google and grants permission, the App can access, in that account only: Gmail messages and labels, Google Drive files and folders, Google Calendar events, Google Tasks, Google Docs, Google Sheets and Google Contacts. The App also reads the account's email address to confirm that the signed-in person is the owner.

How the data is used

Data is accessed only when the owner asks the AI assistant to perform a task, and is used only to carry out that task and show the result to the owner. The App does not use Google user data for advertising, does not sell it, and does not transfer it to anyone, except to the AI assistant the owner is using, as needed to complete the owner's request, or where required by law.

Storage and security

The App does not keep a database of Google data. Google data is fetched on demand and is not retained after a request completes. The Google refresh token that lets the App keep working is encrypted (AES-GCM) inside the sign-in tokens issued to the owner's AI assistant and is not stored on the App's servers. Encryption keys and the Google OAuth client credentials are held in Google Cloud Secret Manager. The App runs on Google Cloud Run.

Google API Services User Data Policy

The App's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. No human reads the owner's Google data, other than the owner.

Sharing

Google data is not shared with third parties. It is sent only to the owner's own AI assistant session in response to the owner's requests.

Retention and deletion

Because the App stores no Google data, there is nothing to delete on the App's side. The owner can revoke the App's access at any time at myaccount.google.com/permissions, and can stop all sign-ins by removing the owner's address from the App's allow-list.

Changes

If this policy changes, the updated version will be posted on this page with a new effective date.

Contact

Jonathan Raabe, jonraabe@aromis.co