Privacy

Written on 5 October 2026 · Publisher: Hypersimple.

Visiting the website

This informational website presents Hypermail and Hypermail MCP. It includes no trackers, cookies, forms, analytics or access to Gmail. The domain and hosting provider have not yet been selected. Once published, the hosting provider may process technical connection logs; their configuration and retention will depend on the selected service.

Using Hypermail MCP

Hypermail MCP is an open-source server running on a machine or infrastructure chosen by its operator. It processes the account address, permissions and tokens, messages, recipients, folders or labels and attachments needed for the requested tools: reading, searching, composing, sending and organizing.

For Gmail, the default scope https://www.googleapis.com/auth/gmail.modify is restricted. Access is not read-only: tools can send messages, create or edit drafts, archive, move, trash and change message states or labels. Review your agent’s actions before authorizing them.

Storage, recipients and data flow

Account credentials and tokens are encrypted at rest in the instance’s storage, on the operator’s machine or infrastructure — not necessarily on the end user’s machine. Debug logs may contain email addresses, identifiers and synchronization metadata.

The flow is: email provider → MCP instance → MCP client → optional AI provider. Hypersimple does not automatically gain access to a self-hosted installation. Processing and retention by the client, AI provider and operator depend on their policies and configurations. This website does not guarantee the absence of logging, training or international transfers by those third parties.

Google data and Limited Use

In covered uses, data obtained from Google must be used only for explicitly requested features, in accordance with the Google API Services User Data Policy, including its Limited Use requirements. Using that data for advertising, selling it or using it to train generalized AI models is prohibited in those uses.

These are usage rules for operators and clients to follow, not a technical control guaranteed by the software or a Google certification. Choose a client and AI provider compatible with these obligations before transmitting Google data.

Retention, removal and revocation

Stored accounts and permissions remain in the instance’s storage until removed by the operator. The remove_account tool removes an account from that instance. To revoke Google access, also use your Google account connections. Local removal and Google revocation are separate steps; do not assume that local removal alone revokes Google access.

Message copies in the AI client, downloaded attachments, backups and logs are not automatically deleted by remove_account. Deletion is the responsibility of the relevant systems and operators.

Contact

For questions and requests about data actually held by Hypersimple: mateo.tiedra@hypersimple.ch. For a third-party instance, also contact its operator and the relevant services.