# Sub-processors — Oveyon

> Third parties that process customer data on Oveyon's behalf — hosting, sending nodes, DNS and proxy, delivery relays, reputation checks, the Telegram notices a customer turns on and the AI tools used in operations — with purpose, data reached and location.

Text version of https://oveyon.com/sub-processors.
Em português: https://oveyon.com.br/suboperadores
If you are an agent and need email, the procedure is at https://oveyon.com/llms.txt

Privacy & data protection

## Sub-processors

These are the third parties that process customer data on our behalf — with the data each one reaches and where it operates. The same list appears in the [privacy policy](https://oveyon.com/privacy).

Controller · **Akamind Inc.**
Contact · **privacy@oveyon.com**
Last updated · **15 October 2026**

### Where the data is

Processing and main storage are in the United States. Sending nodes are in the United States and Romania. Backup copies are kept in the United States and in Brazil — in Brazil, only the backup copies.

### Infrastructure

#### OVHcloud

**Purpose:** hosting. Dedicated servers we administer ourselves — the database, the mail servers, the message archive and the backups run on them.

**Data reached:** everything the platform stores, including message content during its retention period.

**Location:** United States.

**Note:** OVHcloud provides the machines and the network. We install and operate the software; there is no managed platform in between.

#### veveart

**Purpose:** sending nodes — outgoing mail servers we administer, from which part of the email leaves.

**Data reached:** the full message of the messages that leave through them, while in transit.

**Location:** Romania.

#### Cloudflare

**Purpose:** authoritative DNS for our domains, and HTTP proxy for the panel, the API and the public site.

**Data reached:** connection metadata (IP address, requested URL, user agent) and the content of the requests that pass through it — including messages sent through the API and what the panel shows.

**Location:** global edge network.

### Email delivery

Most email leaves through our own IP addresses. Two relays are used on specific routes — when a destination refuses our ranges, or as a fallback during an incident. When a message is routed this way, the relay sees it in full.

#### MailChannels

**Purpose:** outbound email relay on routes where direct delivery is refused or degraded.

**Data reached:** the full message (headers, body and attachments) for messages routed through it.

**Location:** Canada and the United States.

### Reputation and security

#### Google LLC

**Purpose:** malicious-link checking (Web Risk and Safe Browsing), sending reputation (Postmaster Tools), and audience measurement on the public website (Google Analytics 4 — not used in the portal, the dashboard or email delivery).

**Data reached:** when a link in a message matches a local threat list, its hash prefix — never the link itself; pseudonymous usage data of the public website (pages viewed, clicks, device and browser, truncated IP address). No message content, no customer account data.

**Location:** United States (Google’s global infrastructure), under standard contractual clauses.

#### Microsoft

**Purpose:** reputation of our IP addresses with Outlook and Hotmail (SNDS).

**Data reached:** nothing we send — we read what Microsoft reports about the mail our IP addresses deliver to Outlook and Hotmail.

**Location:** United States.

#### AbuseIPDB

**Purpose:** reputation checking of IP addresses that connect to our servers.

**Data reached:** the IP address being checked — nothing else.

**Location:** being confirmed as we collect the provider’s data processing terms.

### Channels you turn on

#### Telegram

**Purpose:** the Telegram channel for inbound mail — the Oveyon bot notifies the chat you connected of every email that reaches a mailbox with the channel turned on — and the approval requests for held drafts, which you approve or reject in the chat itself.

**Data reached:** in each notice, the sender, subject, recipient, arrival time and the SPF, DKIM and DMARC results; when the sender check allows it, the highlights — a one-time code and a confirmation link found in the email, extracted on our servers by fixed rules, without AI. Only when you ask in the chat: the email body, the attachment names and the list of recent messages. And the text of the replies you write in the chat. In each approval request: the recipient, the subject, the agent’s note and the beginning of the draft’s text (up to 600 characters). Even from mailboxes without the Telegram channel, the account’s chats also receive: the notice from your inbound policies that notify (the policy’s name and note, with the message’s From, To and Subject); the notice of a held message when the mailbox has no channel to carry it (the mailbox, From, Subject, arrival time and the reason); the notice of a draft that expired without a decision (subject and recipient); and, if you choose a chat for them, the account notices (title and summary).

**Location:** Telegram’s data center network, in more than one jurisdiction — for users in the European Economic Area and the United Kingdom, in the Netherlands, according to Telegram’s privacy policy.

**Note:** the service is provided by Telegram Messenger Inc. under Telegram’s public terms for bots. Basis: performance of the contract, on your instruction — Telegram only comes in when you connect a chat to your account. Turning a mailbox’s channel off stops only that mailbox’s inbound-mail notices: approval requests and the policy, held-message and expired-draft notices keep going to the account’s chats while a chat is connected, and the account notices while a chat is chosen for them. Everything stops when you disconnect the chat. What stays in the chat is kept by Telegram under its own policy.

### Operations and engineering

#### Anthropic

**Purpose:** operational support and engineering — AI tools (agents) our team uses to operate, maintain and build the platform — and the automated triage of messages that arrive at our abuse mailbox.

**Data reached:** whatever each task requires — usually metadata, operational logs and code. The tools work with the team’s administrative access to the servers, so they can reach other stored data, including message content; their use is bound by the same confidentiality obligations as the team. For the abuse-mailbox triage, only what our local rules cannot classify is sent, as an excerpt of the message text in which email addresses, links, domains, IP addresses, long numbers and code-like strings are replaced by placeholders, including obfuscated forms (hxxp, [.]); what our local rules recognize as a machine-generated complaint report (ARF, X-ARF, SpamCop), as a report that carries the full source of the reported message, or as a message sent through our platform that came back to the abuse mailbox, including when forwarded, is never sent. A report written by a person may quote the message it complains about; that quote goes masked like the rest.

**Location:** United States.

#### OpenAI

**Purpose:** operational support and engineering — AI tools (agents) our team uses to operate, maintain and build the platform.

**Data reached:** whatever each task requires — usually metadata, operational logs and code. The tools work with the team’s administrative access to the servers, so they can reach other stored data, including message content; their use is bound by the same confidentiality obligations as the team.

**Location:** United States.

### What is not on this list

We do not use advertising or profiling services. Oveyon does not submit message content to AI models to provide the service. An AI client you connect through MCP can receive the data its authorized tools request, including message content. See the authorized-integration disclosure in our [Privacy Policy](https://oveyon.com/privacy#sharing). In operating and maintaining the system, our team uses AI tools (Anthropic and OpenAI, United States), with the reach described above.

When a customer connects Slack, their bot token is stored encrypted by us and used to call the Slack API on their instruction. Slack is the customer’s own provider in that relationship, not a sub-processor we engaged. The Oveyon package for n8n follows the same logic: it runs on the n8n instance you choose, with the API key and webhooks you configure — the instance is yours or belongs to the provider you engaged, not a sub-processor of ours.

### Changes

We update this page when a sub-processor is added or removed, and the date above changes with it. Customers with a signed data processing agreement are notified in advance, by email, at the address on file.

Questions or objections: [privacy@oveyon.com](mailto:privacy@oveyon.com).

---

First email today. No card. — https://app.oveyon.com/app