Use case

GDPR-compliant email for EU companies

When a customer's DPA review asks where the data actually lives, “Finland, all of it” is a one-sentence answer — not a sub-processor chain to diagram or a Standard Contractual Clauses assessment to commission.

Requirement How euromail meets it
Where data is processed API ingestion, Redis queues, the Rust SMTP engine, and PostgreSQL storage all run in Hetzner's Helsinki data center (hel1). No edge nodes or replicas outside the EU.
Sub-processors None outside the EU. EuroMail delivers directly to recipient mail servers from Finnish IPs — no Amazon SES, SendGrid, or Mailgun underneath.
Data Processing Agreement Included on every plan, including Free, and names Finland as the sole processing location under GDPR Article 28. Download it from the legal section whenever procurement needs it.
Schrems II / transatlantic transfer Nothing to assess — there's no transatlantic transfer, so no Standard Contractual Clauses, Transfer Impact Assessment, or supplementary measures are needed.
Right to erasure & portability Full account export/erase, or a single recipient's data scoped to one address for a data subject access request — both are API endpoints, not support tickets.
Why this matters for procurement

For B2B sellers, this simplifies vendor assessments and procurement reviews measurably: a legal or compliance team can confirm in minutes that all data stays within the EU, with no complex data-flow diagrams, no sub-processor chains to audit, and no transfer-mechanism evaluation to commission. It's the same reason teams switch away from providers whose "EU region" toggle sits on top of a US-headquartered parent company — see euromail vs Amazon SES for the concrete difference between an EU region and EU-only infrastructure.

Data subject rights

Export and erase, by API

Article 20 portability and Article 17 erasure are endpoints, not support tickets. Per-email export and erasure are rate limited to one request per minute per account and cover metadata, delivery events, and suppression/unsubscribe entries — without touching the rest of the account.

curl "https://api.euromail.dev/v1/gdpr/[email protected]" \
  -H "Authorization: Bearer em_live_..."

200 OK  { metadata, delivery events,
             suppression + unsubscribe entries }

Related

  • EU data residency

    Every component runs in Hetzner Helsinki (hel1) — no edge nodes or replicas outside the EU.

  • GDPR tooling

    Account and per-email export/erase endpoints for Articles 15, 17, and 20.

  • euromail vs Amazon SES

    Why "EU region" on a US-headquartered provider isn't the same as EU-only infrastructure.

Start sending free Read the data residency guide