Data residency

What residency pins

User content, context-graph data, and run traces are stored at rest in the region selected at workspace creation. Backups stay in region. Region migration exists but only as an explicit, customer-initiated, logged operation — data does not move regions as a side effect of anything.

What stays global

• ↳Account metadata and billing records — these live in our primary region (US).
• ↳Aggregate, de-identified operational telemetry.
• ↳Model inference, unless region-pinned routing is enabled — pinning constrains the available model pool, and the trade-off is the customer's to make.
• ↳Support access during an incident, which crosses regions under SCC cover and lands in the audit log.

Verification

Enterprise customers can request their workspace's storage-region configuration and the audit-log entries for any cross-region access. The claim is checkable on demand; that is the difference between residency and a residency-shaped paragraph.