QEHSUnited States
GAus-east-1 / us-west-2
- Primary
- AWS us-east-1 (N. Virginia)
- DR
- AWS us-west-2 (Oregon)
- Regulatory fit
- HIPAA (BAA available), CCPA, SOX, FedRAMP Moderate (inherited controls).
Trust Center
Data residency
Pick where your tenant lives at creation time. Customer content, backups, and search indices stay pinned to that region. We never silently migrate data — a region change is a scheduled, consent-required operation.
European Union
GAeu-central-1 / eu-west-1
- Primary
- AWS eu-central-1 (Frankfurt)
- DR
- AWS eu-west-1 (Dublin)
- Regulatory fit
- GDPR, SCCs (EU 2021/914), EU Data Act alignment, Schrems II supplementary measures documented.
United Kingdom
GAeu-west-2
- Primary
- AWS eu-west-2 (London)
- DR
- AWS eu-west-1 (Dublin)
- Regulatory fit
- UK GDPR, IDTA, DPF (UK extension), NCSC Cloud Security Principles.
Australia
GAap-southeast-2
- Primary
- AWS ap-southeast-2 (Sydney)
- DR
- AWS ap-southeast-4 (Melbourne)
- Regulatory fit
- Australian Privacy Principles, CPS 234, IRAP PROTECTED (in progress).
Canada
GAca-central-1
- Primary
- AWS ca-central-1 (Montréal)
- DR
- AWS ca-west-1 (Calgary)
- Regulatory fit
- PIPEDA, Québec Law 25, provincial data-residency statutes.
United Arab Emirates
Enterpriseme-central-1
- Primary
- AWS me-central-1 (UAE)
- DR
- AWS me-south-1 (Bahrain)
- Regulatory fit
- UAE PDPL, ADGM, DIFC DP Law. Enterprise-plan feature.
What stays in-region
- • Customer content — records, attachments, audit trails, search indices.
- • Database backups and WAL archives.
- • Object-storage buckets and CDN origin.
- • Worker queues and scheduled-job state.
What may cross regions
- • Authenticated support access — documented, time-boxed, logged.
- • Aggregate, de-identified telemetry used for product health (opt-out on Enterprise).
- • Billing metadata (Stripe, US). Separate sub-processor relationship.
Full detail is in the Data Processing Addendum and the Trust Center. Sub-processors listed at /trust/subprocessors.