Data Residency
Circadify offers data residency options to meet regulatory and organizational requirements.
Default Region
Section titled “Default Region”All data is processed and stored in US East (Virginia) by default. This includes:
- Session data (ephemeral, 15-minute TTL)
- Developer accounts and API key hashes
- Audit logs
- Usage records
All infrastructure uses encryption at rest and in transit.
Enterprise Regions
Section titled “Enterprise Regions”Enterprise customers can request dedicated infrastructure in additional regions to meet data residency requirements. Available on request:
| Region | Location | Use Case |
|---|---|---|
| EU West | Frankfurt, Germany | GDPR / EEA compliance |
| EU North | Stockholm, Sweden | GDPR / Nordic data sovereignty |
| APAC | Sydney, Australia | APAC data sovereignty |
To configure a non-default region, contact sales@circadify.com. Enterprise region setup includes dedicated infrastructure provisioned in the requested region.
Cross-Region Processing
Section titled “Cross-Region Processing”By default, all data is processed and stored within a single region. No cross-region data transfer occurs unless an enterprise customer has explicitly configured multi-region infrastructure (e.g., for failover).
Compliance Implications
Section titled “Compliance Implications”- GDPR — Enterprise customers requiring data to remain within the EEA can request EU-based infrastructure.
- Data sovereignty — Select a region within your jurisdiction to meet local data residency laws.
- Default (US East) — Suitable for US-based customers and use cases without specific residency requirements.
Region Changes
Section titled “Region Changes”If you need to change your data residency region, contact support@circadify.com. New sessions will be routed to the new region. Existing session data is ephemeral (15-minute TTL) and does not require migration.
Next Steps
Section titled “Next Steps”- Compliance — Regulatory compliance details
- Retention — How long data is stored