A few days ago I asked about GDPR + NIS2 constraints while building a multilingual voice agent on Retell. The team responded and clarified a few things.
What I understood so far:
-
No training on customer call data
-
Subprocessor changes → 15 days notice + 10-day objection window
-
Breach notification within 5 business days
-
Data retention is configurable (can disable storage)
-
SCCs are available if needed
So overall, from a GDPR standpoint, this looks workable.
Where I’m stuck and need help:
Right now I’m building this system for an EU-based client that falls under NIS2, so the bar is higher than standard GDPR compliance. The requirement from their side is very clear: all data — processing, storage, and any related flow — needs to stay in the EU. This isn’t a “we’ll manage it contractually” situation. If the infrastructure itself is not EU-hosted, they won’t approve the deployment.
The issue I’m facing is that I can’t find a clear, reliable answer on whether Retell actually supports this. The documentation talks about compliance in a general sense, and SCCs help bridge legal gaps, but they don’t solve the core requirement here, which is physical/data residency. I’ve also come across a few mentions of EU hosting or enterprise setups, but nothing concrete enough that I can take back to the client with confidence.
At this point, everything else in the system works fine — the product fits, the workflow is solid, and we’re ready to move forward. This one piece is the only blocker, and without a clear answer, I can’t decide whether to continue with Retell or switch to something else before going deeper into implementation.
What I need clarity on:
-
Does Retell currently support full EU data residency (not just via SCCs, but actual EU-hosted infrastructure)?
-
If yes, how can I access or enable it?
-
If not, is this something that’s planned in the near future?
-
If it’s not supported, what alternatives are people using for strict EU/NIS2 requirements?
Please answer these questions.
Thankyou.