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, attachment names, types and sizes, custom label names and identifiers, message label/inbox status, and existing filter identifiers, criteria and actions. The connector does not provide attachment downloads.

This data is used to find and understand requested email, prepare responses, create and verify unsent drafts, and organise explicitly selected messages. The connector sends a draft’s recipients, subject and body to Gmail when asked to save it. For organisation tasks, it sends requested custom label names or message and label identifiers to Gmail, then reads the resulting state to check the change. Draft edits replace the content of one unsent draft; draft deletion removes only the selected unsent draft. Filter creation sends the approved matching criteria and actions to Gmail. Filters can add one custom label, skip the inbox or mark future matching mail as read. Deleting a filter stops its future action but does not reverse changes to messages.

Personal Calendar and Tasks

Only the owner’s personal Google account can grant Calendar and Tasks access. Calendar data includes owned-calendar names and identifiers, event titles, descriptions, dates, time zones, locations, recurrence rules, guest details and availability. Task data includes list names, task titles, notes, dates, completion state and hierarchy identifiers. This information is sent to Claude to carry out the requested scheduling work.

Approved changes send the selected event or task data to Google. Calendar invitations, updates and cancellations can send emails to guests; a request to suppress updates is not a guarantee that Google will send no email. Recurring changes explicitly distinguish one occurrence from the whole series. The connector does not create or delete calendars, alter sharing permissions or create/delete task lists.

The personal account additionally requests calendar.events.owned, calendar.calendarlist.readonly, calendar.freebusy and tasks. The other three accounts retain Gmail-only access. Read/write tool annotations support the owner’s approval settings in Claude.

Private local scheduling records store request identifiers, target identifiers, the requested fields and operation outcomes to prevent duplicate writes and check interrupted requests. They can contain event or task content, including guest addresses. Status checks do not resend changes. A task creation whose returned ID is lost may require manual inspection.

Calendar events, invitations, tasks and information already sent to Google or Claude are not removed by revoking connector access. They must be managed separately in those services. Scheduling records remain locally until the owner removes them. No separate scheduled background processing is enabled by adding these tools.

Google permissions

The connector requests Gmail modify access (gmail.modify) to read messages, create, edit and delete unsent drafts, create and apply custom labels, and archive or return selected messages to the inbox. It also requests basic Gmail settings access (gmail.settings.basic) to list, create and delete filters. Google’s permission grants broader abilities, including sending and moving messages to Trash. Neil Mail’s own tools and request restrictions permit only its stated features; they do not implement Gmail sending, received/sent-message deletion, trashing, forwarding or settings changes other than the stated filters. The owner reviews and sends drafts in Gmail. Previously connected accounts can keep their existing mail access and must renew consent before using filters. Google may retain the earlier read and compose grants; the connector records the actual granted scopes.

Where data goes

The connector runs on the owner’s Linux computer and communicates with Google to obtain access, read messages, manage unsent drafts, organise selected messages and manage approved filters. Filters run in Gmail on future matching messages even when the connector is disconnected.

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; the connector can delete explicitly selected unsent drafts. Filters remain active until deleted in Gmail or through the connector. 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 Google API access but does not remove existing Gmail drafts, filters, local draft records or information already included in Claude tasks. Existing Gmail filters continue to run after connector access is revoked. 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 neil@snapplesltd.uk.

This website

These information pages contain no mailbox sign-in, forms, analytics scripts or advertising. They do not receive Gmail messages or connector credentials. Cloudflare hosts these pages and may process ordinary web-request information, such as IP addresses and browser details, to deliver and protect them. Cloudflare also masks displayed contact email addresses and supplies a script to reveal them in the browser.

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.