This covers Claude Email, a personal tool that connects my own Google accounts to Claude. It is not a product, it has no users other than me, and it runs entirely on my own machine.
Claude Email is a local program I run on my own computer. It lets Claude read and draft email in Google accounts that I personally own and have explicitly authorized. It is not offered to the public, has no sign-up, and hosts nothing.
There is no server. No data is transmitted to or stored on holderbein.dev or any infrastructure I operate. This page exists because Google requires a published privacy policy before an OAuth app can leave testing mode.
With my authorization, the tool requests these Google permissions:
It cannot send, reply to, or forward email. Those capabilities are removed at the tool layer, not merely left unused — the underlying server is configured so that no send, reply, or forward function is ever exposed to Claude.
Message bodies, calendar entries, and file contents are fetched on demand and held in memory only for the length of a request. They are never written to disk, indexed, or retained.
The tool does keep a debug log on my machine. It records operational metadata — which account a request used, search queries, and the subject lines of drafts it creates — but not message bodies. That log is local, permission-restricted, and never leaves the machine.
Content I ask about — an email I want summarized, a thread I want a reply drafted for — is sent to Anthropic’s Claude models to produce that answer. That is the purpose of the tool, and it is governed by Anthropic’s privacy policy.
OAuth tokens are stored in a permission-restricted directory on my own machine and are used solely to re-authenticate to Google. They are never transmitted anywhere else.
Claude Email’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Access can be withdrawn at any time from Google Account permissions. Revoking immediately invalidates the stored tokens, after which the tool can access nothing.
Questions about this policy can go to benjamin.holderbein@gmail.com.