Data Residency & Trust
Last updated: August 2026
1. Where your data lives today
All customer data on the Cevoriq platform is stored and processed in the United States (US East (Virginia) — us-east-1). We say this plainly because it is the truth a security review needs first: Cevoriq operates a single region today, and no tenant's data is stored outside it.
2. Our region strategy: regions, not countries
Like other enterprise platforms (ServiceNow, Salesforce, Atlassian), Cevoriq offers regions, not per-country infrastructure. A region is a full data plane — its own database and file storage — and countries map onto regions: a German organization is served by an EU region, a UK organization by a UK or EU region. Most data-protection regimes (including UK and EU GDPR) do not require in-country storage; they require lawful handling, which a region plus the appropriate contractual mechanisms (adequacy, Standard Contractual Clauses, a Data Processing Agreement) satisfies.
New regions open on committed customer demand, not on a calendar. We deliberately do not publish dates: a region becomes available when a customer contract requires it and the full regional stack has been provisioned and verified. Until then it is listed below as planned — visible direction, no false promise.
3. Region availability
| Region | Identifier | Status |
|---|---|---|
| 🇺🇸 US East (Virginia) | us-east-1 | Available |
| 🇺🇸 US West (Oregon) | us-west-2 | Planned — opens on committed demand |
| 🇪🇺 EU West (Ireland) | eu-west-1 | Planned — opens on committed demand |
| 🇪🇺 EU Central (Frankfurt) | eu-central-1 | Planned — opens on committed demand |
| 🇬🇧 UK (London) | eu-west-2 | Planned — opens on committed demand |
| 🇸🇬 Asia Pacific (Singapore) | ap-southeast-1 | Planned — opens on committed demand |
| 🇯🇵 Japan (Tokyo) | ap-northeast-1 | Planned — opens on committed demand |
| 🇮🇳 India (Mumbai) | ap-south-1 | Planned — opens on committed demand |
| 🇦🇺 Australia (Sydney) | ap-southeast-2 | Planned — opens on committed demand |
| 🇧🇷 Brazil (São Paulo) | sa-east-1 | Planned — opens on committed demand |
4. What is stored in your region, and what is global
No enterprise platform keeps literally everything in-region, and any vendor who claims to should be asked for their scope table. This is ours. The global column is not a policy exception — it is structurally incapable of holding your business data: the platform's control plane carries only identity, routing facts, entitlements, and pre-aggregated numbers, and its schemas have no fields that could hold a contract, an asset record, or a document.
| Data class | Examples | Where it lives |
|---|---|---|
| Organization business data | Assets, incidents, orders, contracts, customers, shipments, the unit ledger | Your region |
| Documents & files | Contract documents, purchase-order attachments | Your region (storage location recorded on every file at write time) |
| Identity | Name, email, sign-in (via Clerk, our identity provider) | Global |
| Platform registry | Organization name and region assignment, module entitlements, subscription facts | Global |
| Consolidated reporting metrics | Pre-aggregated, whitelisted numbers only (counts and totals) — computed live, never stored; structurally unable to carry a person, serial number, or address | Global (in transit only; nothing retained) |
| Platform-published documents | Material Cevoriq publishes to organizations (e.g. group master agreements), declared non-resident at upload | Global, by declaration |
5. Storage residency vs. processing residency
Selecting a region governs where your data is stored at rest. Application compute may run outside your region — the same posture as most major SaaS platforms, whose support and operations are global. If your organization requires strict processing residency (data never leaving the region even transiently), raise it with us during contracting: it is a materially different commitment and we will tell you honestly whether we can meet it, rather than let a region label imply it.
6. Encryption
- In transit: all traffic is encrypted with TLS.
- At rest: our database and file-storage providers encrypt all data at rest; integration credentials are additionally encrypted at the application layer before storage.
- Customer-managed keys (BYOK): planned as a paid option for organizations that need to hold their own encryption keys — the ability to revoke a key and render data unreadable to the platform. Like regions, this opens on committed demand; ask during contracting.
7. Retention and deletion
We do not currently advertise automated retention-based deletion, because we will not expose a retention setting before its enforcement exists. Deletion requests are honored through the erasure workflow in Settings, subject to legal holds. When automated retention enforcement ships, this page, the product, and the privacy policy will change together.
8. Questions
Security reviews and residency questionnaires are welcome: privacy@cevoriq.com. If a claim on this page and the product ever disagree, the product is the truth and we would like to know.