Privacy Policy — CIFAR Technologies gmail-mcp-server
This policy covers CIFAR Technologies gmail-mcp-server, an internal OAuth client operated by CIFAR Technologies Ltd. that connects authenticated AI agents to Gmail accounts authorized by the operator. It is not a product offered to third parties.
1. Who this policy applies to
CIFAR Technologies gmail-mcp-server is a Model Context Protocol (MCP) server operated by CIFAR Technologies Ltd. ("CIFAR," "we," "us"). The only Gmail accounts the server can access are those explicitly authorized via Google OAuth by a CIFAR operator. There are no end users outside CIFAR.
2. What data we access
When an operator grants the server access to a Gmail account, Google issues an OAuth refresh token scoped to https://www.googleapis.com/auth/gmail.modify. Using that token, the server may:
- Read message metadata, subjects, bodies, and attachments in the authorized account.
- List and modify labels, mark messages as read or unread, and archive messages.
- Send new messages and create drafts from the authorized account.
The server does not access contacts, calendar, Drive, photos, or any non-Gmail Google service. It holds no Google password — only the OAuth refresh token, which you can revoke at any time (see section 6).
3. How we use that data
Access is used exclusively to fulfil tool calls made by AI agents authenticated to the server via Microsoft Entra ID. Typical tool calls include search_emails, read_email, send_email, and modify_labels. CIFAR does not analyse, aggregate, profile, or monetise message content; the server is operational infrastructure, not a data product.
4. How we store data
- OAuth credentials. Google client_id, client_secret, and refresh tokens are stored as Azure Container Apps secrets. They are encrypted at rest and are not exposed in plaintext environment variables, logs, or source control.
- Message content. Message data fetched from Gmail is returned to the calling agent for the duration of the tool call and is not persisted by the server. The server maintains no database, cache, or log of message content.
- Request logs. The server logs tool-call metadata (timestamp, authenticated caller identity, tool name) for diagnostic and audit purposes. Logs do not contain message content, addresses, or subjects.
5. How we share data
We do not share Gmail data with any third party. Data leaves the server only:
- Back to Google (via the Gmail API) when fulfilling a request.
- To the authenticated AI agent that issued the tool call, over a TLS-secured MCP session.
We do not sell, advertise against, or secondarily process any Gmail data.
6. How to revoke access
You can revoke the server's access to any Gmail account at any time:
- Visit myaccount.google.com/permissions.
- Locate CIFAR Technologies gmail-mcp-server (or the Google OAuth client name) under "Third-party apps with account access."
- Click Remove Access.
Revocation takes effect immediately. Subsequent tool calls from the server against that account will fail with an invalid_grant error until the account is re-authorized.
7. Security
The server is deployed as a private Azure Container App protected by Microsoft Entra ID OAuth 2.1 (client-credentials grant with an access_as_agent application role). Every calling agent has its own Entra identity and credentials; there is no shared long-lived password. Credentials and secrets are stored in Azure's managed secret store. Transport is TLS 1.2+ throughout.
8. Children
CIFAR Technologies gmail-mcp-server is internal infrastructure and is not directed at children. It is not accessible to anyone other than CIFAR operators.
9. Changes to this policy
If this policy materially changes, the "Last updated" date below will be revised. Because the server has a small number of internal operators, there is no separate notification channel.
10. Contact
Questions about this policy or the server's data practices can be directed to info@cifar.tech.