Data residency (EU)
European hosting, GDPR positioning, and data boundaries.
MailingCore is designed and operated as a European email platform. Customer data and processing are positioned for EU-based teams that need GDPR-aligned tooling without operating their own mail infrastructure.
What stays in Europe
| Data | Location / control |
|---|---|
| Account, tenant, contacts | MailingCore database (EU-hosted infrastructure) |
| Templates, campaigns, logs | Same tenant-scoped storage |
| API traffic | api.mailingcore.com (EU deployment) |
| Email transport | AWS SES or SMTP — region configured per deployment |
Exact AWS regions depend on your environment (staging vs production). Confirm current regions with your account representative or deployment documentation.
GDPR by design
Built-in capabilities relevant to compliance:
- Consent and unsubscribe — hosted unsubscribe pages,
{{unsubscribeUrl}}, suppression list - Right to erasure — DELETE contact by external ID
- Data minimization — store only what you sync via API (
externalId, attributes you choose) - Audit trail — dashboard audit log for administrative actions (plan-dependent)
MailingCore provides technical measures; you remain the data controller for your end users. Maintain your privacy policy, lawful basis, and DPA with subprocessors (AWS, Stripe, etc.).
Subprocessors
Typical subprocessors include:
- AWS — email delivery (SES), infrastructure
- Stripe — billing and subscriptions
- Redis / queue workers — async delivery (within same deployment boundary)
Request an up-to-date subprocessor list from support for your DPA package.