Data Residency

Data residency is about answering the question: "Where, geographically, do the bytes that represent my customers' calls actually live?" For some teams the answer doesn't matter. For others — healthcare, finance, government, EU/India consumer data — it's a hard constraint.

This page explains the default residency profile of Bolti's managed cloud, what categories of data go where, and the levers you have to change that.

The four classes of data Bolti stores

Class	What it is	Where it lives in Bolti
Application data	Agents, tools, members, phone-number assignments, billing records, call metadata.	PostgreSQL database.
Call recordings	Compressed audio (and optionally video) of every call.	S3-compatible object storage with signed playback URLs.
Call transcripts	The text of what was said during each call, with timestamps and speaker labels.	PostgreSQL (referenced from call records).
In-flight call audio	Live audio streamed during an active call between caller, agent, and providers.	Realtime audio service memory + UDP/SIP transit. Not persisted at this layer.

Different deployment options route each of these to different physical locations.

Default residency in Bolti's managed cloud

Bolti's managed cloud runs on E2E Networks infrastructure in India. The default data flow:

Class	Region	Provider
Application data (Postgres)	India (ap-south)	AWS RDS PostgreSQL
Call recordings (object storage)	India	E2E Object Storage
Call transcripts (Postgres)	India	AWS RDS PostgreSQL
In-flight call audio	India	Realtime audio service on India hosts
DNS, edge, observability	India + Cloudflare global edge	Cloudflare DNS, E2E observability node

Every component you can point at as Bolti runs in India by default. This is the right fit for India-resident customer data and for teams who want a single, predictable jurisdiction.

Where data leaves the region (and what to do about it)

There are two places where Bolti by default sends data to providers outside your chosen region:

1. Provider calls during a live conversation

The STT, LLM, and TTS providers your agent is configured with are separate companies with their own infrastructure. When your agent processes a call, audio chunks are sent to the STT provider, transcripts to the LLM provider, and reply text to the TTS provider — each of which may be hosted in the US, EU, or wherever that vendor's nearest endpoint is.

If your residency requirement says "this data must never physically leave India", you have to constrain the provider list. Concretely:

• STT — pick a provider with an India region (some Bolti-supported STT vendors have one; check with your account team for the current list).
• LLM — use a vendor with India-region endpoints, or a self-hosted LLM via Custom LLMs.
• TTS — same as STT — choose a vendor with the right region, or for Indian-language voices use SarvamAI (India-based).

2. Telephony

If you use Bolti-managed phone numbers, the carrier route is determined by the number's country. If you bring your own carrier or SIP trunk (SIP Trunking), routing follows your provider — which is often what you want for full residency control.

Configurable regions for managed cloud

For customers with specific residency needs, Bolti's managed cloud can run in additional regions on request. Currently available:

Region	Best for
India (default)	India consumer data, RBI-regulated workloads, fastest path to launch
EU (Frankfurt)	GDPR-driven workloads, EU-resident customer data
US (East)	US customer data, low-latency US telephony

Adding a region means provisioning a parallel deployment with the database, object storage, and realtime stack co-located in that region. This is an enterprise plan feature — talk to your account team to enable.

Full residency control via on-prem

For the strictest requirements — government, regulated finance, healthcare — the answer is to run Bolti in your own environment. Then you pick the cloud, the region, the providers, and the carrier; Bolti just provides the software.

See On-Prem Deployment for the full architecture and engagement model. The two most common shapes:

• Full on-prem — every component (Postgres, object storage, realtime audio service, agent worker) inside your VPC. STT/LLM/TTS providers also self-hosted or vendor-locked to your region.
• Realtime on-prem, control plane managed — the audio path stays in your infrastructure (so call audio never leaves your network), and the dashboard/API/billing stay in Bolti's cloud in a region you choose.

Cross-border transfers and contractual cover

For enterprise contracts, Bolti can sign:

• Data Processing Agreements aligning with GDPR (Bolti as processor)
• Standard Contractual Clauses (SCCs) covering EU → other-region transfers when applicable
• Business Associate Agreements (BAA) for HIPAA workloads on US deployments
• DPDP Act addenda for India-resident personal data

Reach out via hello@bolti.co.in to start the paperwork. We can usually turn around a signed DPA within 1–2 weeks of legal review.

Quick chooser

Your situation	Recommended setup
India consumer data, want to launch fast	Managed cloud in India (default). Pick India-friendly providers.
EU consumer data, GDPR	Managed cloud in EU + DPA + SCCs where required
US healthcare, HIPAA	Managed cloud in US + BAA + carefully-vetted provider list
Government / strictly-regulated	On-prem in your environment. Self-hosted LLM. BYO telephony.
Hybrid: audio on-prem, control plane managed	Realtime on-prem, control plane in Bolti cloud (your region)

Related

• On-Prem Deployment — full self-hosted architecture
• PII Data Protection — what data is sent to LLMs and how to mask it
• Understanding Providers — picking providers by region
• Custom LLMs — point at a self-hosted or region-locked LLM