Compliance & privacy

Configure data residency

Last updated 2026-05-05

Overview

Data residency pins ingestion, processing, and specific destination routes to a geographic boundary (for example EU-only). Configure it during workspace provisioning or migration projects where DPAs demand fixed regions.

Steps

In Settings → Data residency, pick the primary region; note any destinations that cannot be satisfied in-region.
Update DNS / SDK endpoints to the regional hostname your contract requires.
Document subprocessors and cross-border flows in your ROPA.

{
  "primary_region": "eu-central-1",
  "allowed_destination_regions": ["EU"],
  "block_non_compliant_destinations": true
}

Re-run consent and mapping reviews—some vendors require US reconcilers even when data lands in EU buckets.

Troubleshooting

Blocked activations list the exact policy—either disable the destination or request an exception workflow.
Historical backfills may need re-export from the old region before cutover—plan read-only periods accordingly.
Mixed-mode workspaces (legacy US + new EU) should split to avoid accidental cross-region joins.