Privacy and data use

This is a prelaunch description of this service’s actual data handling. The operator must review final privacy, retention and verification disclosures before general public publication. This page is not evidence of Google approval.

Data accessed

Basic Google sign-in requests verified identity, email and profile. Optional account linking requests additional permissions for mail and settings, Drive files and sharing, Calendar, Tasks, contacts or administrator verification. Actual access depends on the connected account’s granted scopes and entitlements.

Use and sharing

Google data is used to execute actions and return reports requested by your authorized MCP client. Results travel to that selected agent client, which has its own privacy practices. Authorized changes go to the relevant Google API. An email or domain suffix by itself cannot grant access to another account.

Data stored

The service stores verified identity/account metadata, encrypted Google authorization grants, hashed rotating agent tokens, selected connection policy, change/activity records and, when needed, temporary paged tool results. Secure, HttpOnly, SameSite cookies maintain your browser session. Neither account credentials nor other users’ mailboxes appear on public pages.

Control, deletion and retention limits

From your account portal you can revoke agent access or disconnect a linked Google account locally. This does not itself prove provider-side Google grant revocation. You can independently remove Google’s authorization in your Google Account security settings. A recoverable deletion request is available, but an irreversible deletion or particular retention deadline is not yet promised. Audit/recovery records may require separate handling. See deletion details.

Questions

See support for the operator contact. Final retention periods and the public policy need operator review before launch.