Where call data is stored
Each kind of data a call creates, where it is stored, which key encrypts it and how long it is kept. Calls run in Sydney and backups go to Melbourne.
Data inventory
Your key means a KMS key you hold, or grant to the call plane.
| Data | Stored in | Encrypted under | Kept for | Leaves Australia |
|---|---|---|---|---|
| Live call audio | Not stored; streams between Telnyx, the call worker and Deepgram in Sydney | TLS in transit | The length of the call | No |
| Recordings | S3 in the call plane account, Sydney | Your key | 30 days, or longer if an agent is set to | No |
| Transcripts and call records | Aurora in the call plane account, Sydney | Your key | Your retention window | No |
| Stored secrets for your tools | Encrypted in the row that owns them | Your key, bound to the workspace and row | Until you delete them | No |
| Agent configuration | The control plane, with a copy of each published version in the call plane | A customer-managed KMS key | While the agent exists | No |
| Knowledge base documents and search index | S3 and Aurora in the call plane account, indexed by Titan Text Embeddings in Sydney | Your key | Until you delete them | No |
| Model prompts and replies | Not stored by the platform; processed by Bedrock in Sydney and Melbourne | TLS in transit | Bedrock invocation logging is off | No |
| Logs, metrics and traces | CloudWatch in the call plane account | CloudWatch encryption | 14 days | Alarm names only |
| Backups | A separate account in Melbourne | A separate key in Melbourne | 7 daily copies | No |
| Usage counts | The control plane, for billing | A customer-managed KMS key | For billing records | No |
| Call detail records at the carrier | Telnyx, stored in Australia under its data locality setting | Telnyx | Telnyx's retention | Numbers and call IDs pass its US API |
| Speech service metadata | Deepgram's billing records | Deepgram | Deepgram's retention | Billing metadata only, never audio |
This table covers enterprise deployments. The shared platform's providers and regions are listed on the security page.
Data that leaves Australia
- Telnyx's call control API runs in the United States. Commands to answer, transfer and end a call carry caller numbers and call IDs, and call audio stays in Sydney.
- Deepgram keeps operational metadata and billing records in the United States. Audio and transcripts are processed in Sydney and not stored.
- Alarm names leave the account to page our on-call engineers, with no call data.
- A voice from ElevenLabs, Cartesia or Fish Audio sends the text it speaks to the United States. No agent uses one unless you pick it.
Retention and deletion
Retention window
Transcripts and call records are deleted by a daily job once they pass the window you set.
Recordings
Recordings are kept for 30 days unless an agent is set to keep them longer.
Redaction
Card, Tax File, Medicare and US Social Security numbers are masked before a transcript line is saved.
Key revocation
Revoking your KMS key makes the database, recordings and stored secrets unreadable.
Model calls
Claude on Amazon Bedrock
- Regions
- Sydney and Melbourne
- Route
- Bedrock's Australian profile
- Trains on your data
- No
- Invocation logging
- Off
- Offshore failover
- None
When Bedrock fails
The agent tells the caller it cannot help right now and forwards them to your fallback number. No call fails over to a model outside Australia, because the direct Anthropic API has no Australian region.
Security questionnaires
We answer security questionnaires in writing and take your team through the architecture on a call. Send yours to hello@verticalai.com.au.