Questions · Published 2026-09-27 · Updated 2026-09-28 · AgentiSend
Can I keep my email data in the EU?
Not today. The region eu is recorded on each sending domain, but all email, eu domains included, is sent from our US nodes, and all account data is stored in the United States. GET /domains/{id} returns the stored region.
Not today. POST /domains takes region, us (Oregon) or eu, default us, and the value is recorded per sending domain. No email leaves from the EU yet: every message, eu domains included, is sent from our US nodes in Hillsboro, Oregon, and the application and its database run there too, so the message history and account data for every domain, EU or not, are stored in the United States. The privacy page says it directly: "Today mail for both is sent from our US nodes, so the region changes neither where mail leaves from nor where anything is stored."
What region governs
region is set once, on POST /domains, whose summary is "Register a sending domain. Region is optional and defaults to us (Oregon); the stored value is returned." GET /domains/{id} returns it on every read. Domains and DNS says "EU sending is on the roadmap; eu domains move to it automatically when it ships, with nothing to change on your side." A PATCH /domains/{id} that tries to change it is refused with domain_field_immutable, whose catalogue message is "Name, region, and return-path cannot change on an existing domain." To record eu on a domain registered as us, add it again with region: "eu", publish the records, verify, and send from the new registration. A value outside us and eu is invalid_region: "Region must be one of us, eu."
curl -sS -X POST https://api.agentisend.com/domains \
-H "Authorization: Bearer $AGENTISEND_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"name":"example"}'201
{
"capabilities": {
"receiving": "enabled",
"sending": "enabled"
},
"click_tracking": false,
"created_at": "2026-09-04T09:14:00.000Z",
"dkim_selector": "example",
"id": "9c8f8f0e-3d1a-4d3f-9a1e-2b7c1a0f5e42",
"inbound_hold_mode": "monitor",
"inbound_policy": "open",
"inbound_refused_count": -9007199254740991,
"name": "example",
"object": "domain",
"open_tracking": false,
"provider_hints": {
"cloudflare": "example",
"godaddy": "example",
"namecheap": "example",
"route53": "example"
},
"recent_events": [],
"records": [],
"region": "us",
"return_path_subdomain": "example",
"status": "pending",
"tls_mode": "opportunistic",
"tracking_issues": [],
"tracking_subdomain": "example",
"verified_at": "2026-09-04T09:14:00.000Z",
"warnings": [],
"zone": "example"
}Where the data sits
The subprocessors page lists the infrastructure locations: Hillsboro, Oregon, United States for the application, the database and the mail transfer that sends customer mail today. The stored message, its events, the audit log and the account record are in the United States for every account. If your requirement is that message content never leave the EU, in transit or at rest, this product does not meet it today, and no field on POST /domains changes that.
The paperwork
The DPA says that customer data is processed and stored in the United States whichever region a domain records, and that the Standard Contractual Clauses apply where that is a transfer out of the EU, the EEA or the UK. The privacy page lists what is stored and for how long, and How long does AgentiSend keep my emails? covers the retention window. GET /account/export returns everything the account holds, so the data can be taken out at any time.