Your data stays in Frankfurt.
Every byte a customer hands to the Cervana voice AI platform — call audio, transcripts, captured details, agent configuration, knowledge bases, voices, account data — is stored and processed in one place: the AWS region eu-central-1, Frankfurt am Main, Germany. This page says exactly what that means, what by its nature lies outside, and how you verify it without taking our word.
No replication, backup or offloading to any other region. No conversation content sent to third-party AI services: speech recognition, the language model and speech synthesis are Cervana's own models, running inside the same cluster. No transfer of personal data outside the EEA without the customer's prior written approval.
Last verified against the live production environment: 9 October 2026. A signed, bilingual (German/English) Data Residency and Processing Affirmation for your compliance file is available from sales@cervanaai.com.
What lies outside by nature
Phone calls reach Frankfurt through the public telephone network and a telephony carrier with European points of presence — or through your own carrier or PBX, connected by SIP trunk (see the SIP Interconnect guide). Card payments, where chosen, are handled on a PCI-certified payment provider's hosted page; Cervana never sees card data. Integrations you configure yourself — webhooks, MCP servers, your website fetched at call start — receive the data you assign to them, at the endpoints you choose. Production is administered by Cervana's founders only, under least-privilege access, multi-factor authentication and logging, without copying or exporting data out of the region.
Verify it yourself
1 · Independently, against Amazon's published IP ranges. Resolve our host names and look the addresses up in
https://ip-ranges.amazonaws.com/ip-ranges.json. Every prefix must carry eu-central-1.
$ dig +short api.cervanaai.com console.cervanaai.com sip.cervanaai.com
$ curl -s https://ip-ranges.amazonaws.com/ip-ranges.json -o ip-ranges.json
$ python3 - 63.184.104.253 35.158.59.1 3.76.164.6 52.58.87.94 <<'EOF'
import json, sys, ipaddress
ranges = json.load(open("ip-ranges.json"))["prefixes"]
for ip in sys.argv[1:]:
a = ipaddress.ip_address(ip)
print(ip, sorted({p["region"] for p in ranges if a in ipaddress.ip_network(p["ip_prefix"])}))
EOF
| Host name | Addresses (9 Oct 2026) | Region per ip-ranges.json |
|---|---|---|
api. / console. / docs.cervanaai.com | 63.184.104.253, 35.158.59.1 | eu-central-1 |
sip.cervanaai.com | 3.76.164.6, 52.58.87.94 | eu-central-1 |
| Media (RTP) | 52.58.87.94, 3.67.231.240 | eu-central-1 |
2 · Through the API. GET https://api.cervanaai.com/v1/residency needs no sign-in. It returns the
configured declaration and what the service observes at runtime — the region embedded in the host name of the database
it actually uses, and the region of its object-storage and e-mail clients. If they disagree, it answers "consistent": false.
Poll it from your compliance monitoring.
$ curl -s https://api.cervanaai.com/v1/residency | jq '.declaration.region, .observed, .consistent'
"eu-central-1"
{ "database_host_region": "eu-central-1", "object_storage_client_region": "eu-central-1", "mail_region": "eu-central-1" }
true
3 · In the console. Every recording download link is signed with AWS Signature Version 4; its
X-Amz-Credential parameter ends in …/eu-central-1/s3/aws4_request — the cryptographic scope names the
region the file is stored in.
4 · Documents and audit. AWS audit reports for the Frankfurt region are available through AWS Artifact on request, and the Data Processing Agreement grants a yearly audit right.
5 · Or run it yourself. The same platform ships as a Kubernetes package for your own data centre, fully air-gapped if you wish. Then nothing leaves your environment at all.