​

Data Residency Overview

“Where does my data live?” has a different answer per channel on Orbit. Voice is the one channel where you pin a resident region directly; everything else — email, SMS, WhatsApp, RCS, and the audit trail — is covered by the platform geography Devotel publishes in its legal materials, plus the location guarantees that apply when a data-subject request is exported. This page is the map: which surface answers which channel’s residency question, and what belongs in a residency-aware tenant checklist.

---

​

Which control answers which channel

Pick the right surface before you write residency into a register or a contract answer. Using the voice-region pin as the answer for every channel is the common mistake — it covers voice data and nothing else. For messaging channels there is no tenant-side region pin. The residency answer lives with the Devotel platform and the subprocessors it engages, and it is published — with data-residency notes per entry — alongside the SOC 2 reports and downloadable agreements in the Trust Center.

---

​

How to read the subprocessor registry

The registry names every third party that processes platform data and states, per entry, what it processes and where. Read it before you fill in a security questionnaire or your own Art. 30 register. (The Legal index keeps the map of which document binds which party if you need the contract context around the registry.)

• What the registry gives you — the vendor name, the data classes it touches, its processing location, and the agreement that covers it. That is the residency answer for email, SMS, WhatsApp, and RCS — there is no per-workspace toggle that changes it, and none is offered as one.
• What it does not give you — a control you can flip. The note not a tenant setting in the table above is deliberate: residency on messaging channels is set by where the platform runs, which is a procurement-side question, not an ops-side switch.
• What to do with it in your own records — record the registry entry as the residency basis for the channel in your Art. 30 register, next to the channels it covers. If a buyer asks for a channel-level residency answer for messaging, point at the registry entry, not at a dashboard toggle.

When a contract requires messaging residency beyond what the registry describes, raise it with Devotel before signing — the registry is the published answer, and anything narrower is a commercial conversation, not a configuration step.

---

​

What resident region the controls actually cover

The distinction matters most at the audit-evidence and questionnaire boundaries you are answering. The Voice data residency page — and the dashboard region pin it documents — covers exactly three voice data classes: call recordings, voicemail, and live media for calls in progress. Each resident region runs its own media servers, live call-state, and recording storage, and the platform routes nothing from an eu-pinned workspace through the us region (nor the reverse). Everything else on Orbit — message bodies and metadata for email, SMS, WhatsApp, and RCS, plus your audit logs and security events — is under the subprocessor-registry answer above. When a residency question arrives, don’t point it at the voice-region page unless the data being asked about is one of the three voice data classes; pointing at it for messaging or audit data answers a question with the wrong control.

---

​

The DSAR export’s residency scope

When an access or portability request runs, the exported payload — the per-table rows behind tables_exported on a completed request — is packaged in storage whose location and link shape are fixed at export time. That scope has two consequences:

• The scope can’t be widened after the fact. If a residency reading of your tenant is part of the export decision, it needs to be settled before the export is produced, not argued about once the link is issued.
• Playback-style links are short-lived. Like recording playback, the export link is a temporary signed artifact, not a durable copy of the data. Whatever residency interpretation you rely on, treat the link as a one-hour-shaped pointer rather than a new residence for the data.

The precedent is the reasoning on the voice page: a stored artifact carries its region with it, and fetching it from a different geography doesn’t relocate it. The same shape applies to DSAR exports. For the intake, verification, and fulfilment mechanics of a request, see DSAR. For how the export fits the wider GDPR sequence, see Assembling a GDPR Posture End to End.

---

​

Tenant checklist for a residency-aware posture

Residency is a set of per-channel answers plus record-keeping decisions. Work this checklist before you certify a workspace’s residency posture to a buyer or a supervisory authority.

---

​

Related