Privacy policy

Data accessed and why

After Google authorisation, the connector checks the account’s email address and can search and retrieve messages. Retrieved data can include sender and recipient details, subject lines, dates, message text, message and thread identifiers, and attachment names, types and sizes. The connector does not provide attachment downloads.

This data is used to find and understand requested email, prepare responses, create unsent drafts and check that a draft was saved correctly. The connector sends a draft’s recipients, subject and body to Gmail when asked to save it.

Google permissions

The connector requests Gmail read access (gmail.readonly) and draft access (gmail.compose). Google’s compose permission also permits sending at the account-authorisation level. Neil Mail’s own tools and request restrictions permit reading and creating drafts; they do not implement sending or deleting messages. The owner reviews and sends drafts in Gmail.

Where data goes

The connector runs on the owner’s Linux computer and communicates with Google to obtain access, read messages and save drafts.

Information returned by its tools, including message content when a message is read, is shared with Anthropic’s Claude service to carry out the requested email task. It may therefore be retained in Claude conversations or task records. Google and Anthropic handle data under their respective terms, policies and the owner’s account settings. Email processing is not confined to the local computer.

The connector itself does not sell mailbox data, use it for advertising or operate a model-training service.

Local storage and retention

Google authorisation credentials and refresh tokens are stored in a private directory on the owner’s Linux computer, with access limited by operating-system file permissions. These tokens allow the connector to continue accessing accounts until Google access expires or is revoked. The connector does not request or store Google passwords.

A local draft record keeps the account address, request and message identifiers, status, verification time where available, and hashes of the draft request and content. This helps prevent duplicate saves and check saved drafts. These records do not contain copies of draft bodies. The connector has no automatic deletion period for its local tokens or draft records; the owner must remove them when they are no longer needed.

Messages and saved drafts remain in Gmail until managed there. Copies of information in Claude are managed separately through Claude’s conversation and account controls.

Revoking access and removing data

The owner can revoke Neil Mail’s access through Google Account connections. Revoking access prevents future authorised Gmail access but does not remove existing Gmail drafts, local draft records or information already included in Claude tasks. Those must be managed separately in their respective locations.

For help removing the connector’s local credentials or records, or for a privacy enquiry, contact [email protected].

This website

These information pages contain no mailbox sign-in, forms, analytics scripts or advertising. They do not receive Gmail messages or connector credentials. A hosting provider may process ordinary web-request information, such as IP addresses and browser details, to deliver and protect the pages.

Changes

This policy will be updated if the connector’s data handling changes. Any materially different use of Gmail data requires the owner’s consent before that use begins.