Data Residency

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

Default Region

By default, account data and the inference pipeline run in United States infrastructure. This includes:

• Developer accounts and API key hashes
• Audit logs
• Usage records
• The inference engine that processes uploaded RGB tensors

All infrastructure uses encryption at rest and in transit. No health data is retained — uploaded RGB tensors 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:

Region	Use Case
EU	GDPR / EEA compliance, EU data sovereignty
APAC	APAC data sovereignty

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 inference 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