How Personal Mail MCP handles data. In force as of 26 September 2026.
Personal Mail MCP ("the application") is a single-operator tool that runs in two forms under the control of its operator: a local program on the operator's own computer, and a hosted component running on Cloudflare Workers under the operator's own Cloudflare account. This policy describes how both forms handle the data of the individual who controls the application (the "operator"). The application has no other users.
With the operator's explicit Google authorization, the application accesses the operator's own data in the following Google services:
It accesses only the Google Account that the operator has personally authorized. It never accesses any other person's account, and the hosted component refuses sign-in from any Google Account other than the operator's.
Data is retrieved from Google's APIs only in response to the operator's own requests, passed to the AI assistant the operator uses (Claude, by Anthropic) for the sole purpose of answering the operator's own questions or drafting the operator's own replies, events, or files, and then discarded. The application maintains no database and no archive of email, calendar, or file content.
The local component stores authentication material on the operator's own computer, in a directory with owner-only file permissions:
The hosted component stores OAuth credentials in Cloudflare Workers KV, under the operator's own Cloudflare account. Access and refresh tokens are stored only as hashes, and the underlying Google credentials are stored encrypted. Neither component stores any email, calendar, or file content. Attachments are written to disk by the local component only when the operator explicitly asks for one to be downloaded. Nothing else is retained.
The application shares data only as necessary to provide the operator's own requested features, with these recipients:
googleapis.com.There is no analytics, no telemetry, no error reporting service, no advertising, and no other third-party recipient of any kind. No data is sold or rented.
The application's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the features the operator requests; it is transferred only as necessary to provide those features (to the operator's AI assistant and to the hosting provider) or as required by law; it is never used for advertising; and the application does not use it to develop, improve, or train generalized AI or machine learning models.
Content retrieved from Google is not retained past the request that fetched it. A hosted sign-in grant expires automatically after 30 days without use. Stored credentials otherwise persist until the operator deletes them. The operator may revoke the application's access at any time at myaccount.google.com/permissions, which immediately and permanently invalidates all stored tokens, and by removing the connector from the AI assistant. Deleting the local component's configuration directory, or the hosted component's Cloudflare Workers KV storage, erases every trace of its stored credentials.
All connections use TLS. Local credentials are stored with owner-only file permissions. Hosted credentials are stored encrypted, with access and refresh tokens stored only as hashes, and the hosted component requires Google sign-in restricted to the operator's own account. Because the application runs under the operator's own accounts, its security is bounded by the security of the operator's computer, Google Account, and Cloudflare account.
The application is not directed at children and is not made available to the public.
Any change to this policy will be published on this page with an updated date.
Questions about this policy may be sent to gmailMCP@bsq.info.