Developer portal
Data residency
Regional hosting guidance for organizations with US or EU data location requirements.
Last updated: 2026-06-09
Residency model
Qtangl supports a default US deployment profile and an EU profile for enterprise agreements that require regional processing controls. Residency commitments are defined contractually and reflected in deployment architecture.
US vs EU residency matrix
| Data category | US profile | EU profile | Notes |
|---|---|---|---|
| Tenant metadata | Stored and processed in US region. | Stored and processed in EU region. | Includes organization settings, identity mappings, and routing metadata. |
| Scan findings | US-at-rest by default. | EU-at-rest in contracted EU deployment. | Used by remediation, reporting, and trend analytics pipelines. |
| Evidence bundles | US object storage. | EU object storage where configured. | Customer export destinations can be region-aligned. |
| Webhook payloads | Emitted from US control plane. | Emitted from EU control plane. | Destination endpoints are customer-controlled and may be cross-region. |
| Support artifacts | Case data handled in US-centric workflow. | EU-handling process by agreement. | Minimize sensitive payload data in support attachments. |
Cross-region controls
- Cross-region transfer requirements are managed through contract and technical guardrails.
- Data export and integration destinations remain under customer configuration control.
- Retention and deletion requirements can be aligned to regional legal obligations.
Found an issue? Report documentation feedback