Data Residency

Where Circadify processes your data.

Circadify offers data residency options to meet regulatory and organizational requirements.

Default Region

By default, account data and measurement processing run in United States infrastructure. This includes:

• Developer accounts and API key hashes
• Audit logs
• Usage records
• The service that processes SDK-prepared measurement payloads

All infrastructure uses encryption at rest and in transit. No health data is retained — measurement payloads are processed and discarded; vital sign results are returned to the client and not stored.

Enterprise Regions

Enterprise customers can request infrastructure in additional regions to meet data residency requirements. Available on request:

Specific data-center locations within each region are confirmed at contract time. To configure a non-default region, contact sales@circadify.com.

Cross-Region Processing

By default, account data and measurement processing for a given developer run within a single region. No cross-region data transfer occurs unless an enterprise customer has explicitly requested multi-region infrastructure.

Compliance Implications

• GDPR — Enterprise customers requiring data to remain within the EEA can request EU-resident infrastructure.
• Data sovereignty — Select a region within your jurisdiction to meet local data residency laws.
• Default (US) — Suitable for US-based customers and use cases without specific residency requirements.

Region Changes

If you need to change your data residency region, contact support@circadify.com. New scans will be routed to the new region. Because no health data is retained, no per-scan migration is needed.

Next Steps

• Compliance — Regulatory compliance details
• Retention — What is retained, and for how long