Data Residency

Medera tenants are pinned to a region at creation and never cross region boundaries. Audio, video, transcripts, and PHI columns are stored and processed only in the selected region’s infrastructure.

​

What “never crosses” means

• Audio streams terminate inside the region
• Transcripts and PHI columns are stored only in the region’s database
• Backups stay in the region
• LLM inference runs against region-pinned model endpoints
• Audit log replication stays in-region
• Email and SMS (voice carrier) route through regional voice carrier infrastructure where available

​

Immutable selection

Region is chosen at tenant creation and is immutable. Migration between regions requires explicit export + re-onboard.

​

EU specifics

• AWS EU sub-processor list applies
• Sub-processors are EU-only (Medera reasoning EU endpoints, observability platform EU, error tracking EU, payment processor EU)
• Data Processing Addendum (DPA) under GDPR Art. 28

​

MENA specifics

• Customer VPC is the typical deployment for ME-South
• Sub-processor list is per-customer agreement
• Arabic (ar-SA) BH-tuned speech is GA in this region

​

Customer VPC

Enterprise tenants can run the Medera stack inside their own AWS or GCP VPC:

• Customer-managed encryption keys (CMK) for the KEK layer
• Customer-managed sub-processors
• Customer-controlled audit replication target

---

​

What’s next