What data residency covers
Your account has one region. That region determines where your call recordings, transcripts, post-call analysis fields, and contact records are stored at rest. Setting it is a decision you make once, at signup.
The platform offers an EU data residency option. If you process personal data belonging to EU residents, GDPR expects that data to generally stay in the EU, and the region setting is how you satisfy that expectation. See compliance for the wider GDPR obligations that residency alone does not discharge.
What lives in your region
| Data | Stored in your account region |
|---|---|
| Call audio recordings | Yes |
| Transcripts | Yes |
| Post-call analysis fields | Yes |
| Contact records in audiences | Yes |
| Call metadata (timestamps, caller ID) | Yes |
Retention rules apply on top of residency. Recordings default to 90 days and are configurable up to 7 years. Deletion at the end of the retention period is permanent with no recovery. See retention.
Choosing your region
You choose the region during signup. This is a dashboard action, not an API call. There is no endpoint that creates an account or sets its region, so do not plan an automated provisioning flow around one.
Once your workspace exists, the region it was created in is shown under Settings → Privacy → Regional data. Treat that panel as read-only confirmation of what you picked, not as a switch.
Region is not something you flip later
The most common mistake is signing up in the default region, running calls for a few weeks, and then discovering you have EU customers. At that point you have recordings, transcripts, and contact records already at rest in the wrong region.
Migrating existing data between regions is not a self-serve operation. There is no dashboard control and no API for it. If you are in this position, contact support and describe what you have stored and which region you need. Whether a migration is possible for your account, and on what terms, is not something this page can promise.
The practical consequence: decide your region before your first production deployment, not after. If you are unsure whether you will call into the EU, and you have any realistic chance of doing so, pick EU at signup.
What residency does not do
Data residency governs where data is stored. It does not govern:
- Who you may call. Calling a number in a country does not require your account to be in that region, and having an EU region does not make cold outbound marketing to EU consumers lawful. The ePrivacy Directive still requires prior opt-in. See compliance.
- Carrier routing. Voice traffic traverses carrier networks to reach the called party wherever they are. Your region choice does not confine call signaling or media paths. If you need control over the carrier path, that is a telephony question. See byoc-sip and telephony-overview.
- Your own systems. If you send call data outward through webhooks or an integration, it lands wherever your endpoint or your CRM lives. A webhook from an EU-region account to a receiver hosted elsewhere moves the data out of the EU. That transfer is yours to justify, not the platform's. If residency matters to you, host your webhook receiver in the same region and check where your integration vendors store data.
- Consent and disclosure. Recording disclosure requirements come from the jurisdiction of the call, not your storage region. See recording-consent.
Reducing what you store
Residency is one control. Storing less is another, and the two compose.
- Disable recording per Finn under Call Settings, or globally under Settings → Compliance.
- Enable PII redaction under Settings → Compliance → PII Redaction. It strips items such as SSNs and full credit card numbers from transcripts. It does not touch the audio. If a call captured something sensitive in speech, redaction leaves it in the recording, and you have to delete or trim that recording yourself.
- Shorten your retention window so data ages out sooner. See retention.
Right-to-delete requests are handled through the dashboard and the API. GDPR gives you 30 days to comply, so do not treat a deletion request as a background task.
Regions available
The context for this page establishes an EU data residency option and a default non-EU region for accounts created without one. The full list of available regions, and any per-region feature differences, is not settled here. Confirm the current options with support before committing to an architecture that depends on a specific region existing.