Where is my email data processed, and under which agreement?
The console and every shared node run in data centres inside the European Union, and no mail data is processed outside it. With your own node, mail submitted over SMTP, its queue and its logs stay on your infrastructure; messages submitted through the API are stored by the console to hand them to your node. Your organisation is the controller of the data in its messages and we are its processor, under the data processing agreement that is part of the terms.
API keys, SMTP credentials and node tokens are shown once and stored as hashes. Per-destination TLS policies decide how each message is encrypted in transit: opportunistic, required, or DANE-verified. The GDPR page below lists what is stored in each sending mode and for how long.
Compliance
Data stays in the jurisdiction you choose
With your own node, message bodies, recipients and logs never leave your infrastructure. Shared nodes run on EU infrastructure only, and every action in the console is attributable to a member and an API key.
GDPR
Processor agreement at onboarding. With your own node we process no message content at all.
EU hosting
Console and shared nodes hosted in the EU. No processing outside the Union.
Credentials shown once
API keys, SMTP credentials and node tokens are displayed a single time and stored hashed.
TLS by policy
Per-destination TLS policies decide how each message is encrypted in transit.
0
Message bodies stored by us when you run your own node
EU
Console and every shared node hosted inside the Union
3
DNS checks per domain: SPF, DKIM, DMARC
2
Ways to send: REST API and SMTP relay
Legal
Ready to send from where you decide?
Tell us about your domains and monthly volume. We set up your organisation and send an invitation, usually within one working day.