Data residency.
TeamSync supports data residency at the regional level, with per-tenancy + per-class control where required by jurisdiction or contract.
| Region | Data residency options |
|---|---|
| US (commercial) | AWS, Azure, GCP, OCI |
| US (government) | AWS GovCloud, Azure Government, GCC High, Google Cloud for Government, OCI Gov |
| EU | Per Member State; multi-country EU residency available |
| UK | UK-only residency available |
| Canada | Canadian-resident residency available |
| APAC | Australia, Japan, Singapore, India, Hong Kong (per data centre availability) |
| Mainland China | Onshore option per partner; PIPL-aligned |
| MEA | UAE + Saudi data residency available |
| LATAM | Brazil-onshore + others per data-centre availability |
Per-class residency.
For specific data classes (e.g., regulated personal data, classified content, source-of-record contracts), per-class residency policies are configurable.
Cross-border transfer mechanisms.
For workflows requiring cross-border movement, appropriate safeguards are applied per region: SCCs (EU), UK IDTA, EU-US Data Privacy Framework, ASEAN MCCs, etc.
Government cloud authorisations.
| Cloud | Status |
|---|---|
| AWS GovCloud | Operating per FedRAMP High |
| Azure Government / GCC High | Operating per FedRAMP High |
| Google Cloud for Government | Operating per FedRAMP High |
| Oracle Government Cloud | Operating per FedRAMP High |
Customer-controlled key custody.
Per-tenancy envelope encryption supports customer-controlled key custody for tenancies requiring sovereignty. See Crypto-shred pillar.