Skip to contentSkip to content
Security & privacy

Regional data placement and residency migrations

Pin your workspace data to a specific geographic region, inspect primary storage versus subprocessor coverage, and schedule regional database migrations.

Last updated

Organizations operating under GDPR, DIFC/ADGM, or regional enterprise compliance policies often need explicit control over where customer conversations, attachments, and backups reside. Frosvo provides workspace-level regional data placement under Settings → Data & privacy → Regional data placement.

Supported placement regions and coverage matrix

Every workspace is assigned to an active placement region:

  • Europe (Frankfurt — EU Central) under EU / GDPR jurisdiction.
  • United States (Virginia — US East) under US jurisdiction.
  • Middle East (Dubai / Riyadh — ME Central) under UAE / KSA regional jurisdiction.
  • Asia Pacific (Mumbai / Singapore — AP South) under APAC jurisdiction.

For each region, the residency card displays an explicit coverage matrix showing that primary database tables, uploaded files, and encrypted workspace exports reside in the selected region, alongside the exact regional routing used for AI model inference, outbound email relays, and mobile push gateways.

Enforcing strict region pins and subprocessor controls

Workspace owners can configure three residency policy switches:

  1. Enforce strict region pin on API requests: verifies the X-Frosvo-Region header when present and rejects mismatched regional writes.
  2. Allow cross-region AI inference: controls whether the AI assistant may call model endpoints outside your primary storage region when a regional model endpoint is unavailable.
  3. Allow cross-region email relay fallback: controls whether outbound email notifications may fail over to a secondary regional relay.

These controls complement connection health monitoring and customer-owned integration gateways.

Scheduling or executing a regional migration

If your organization relocates or updates its compliance posture, you can move your workspace to another region from the same card. Choose the target region and either Schedule next window (which queues a tracked ResidencyMigration record for your maintenance window) or Migrate now to switch active placement immediately with a full audit log trail.

Frequently asked questions

What is the difference between primary storage residency and subprocessor coverage?

Primary storage covers your database rows, attachments, and encrypted workspace exports, whereas subprocessors cover external AI model inference, email relays, and push notification gateways.

How does strict region pinning work on API requests?

When strict region pinning is enabled, requests carrying an X-Frosvo-Region header that does not match your workspace placement are refused before mutating data.