Skip to main content
DialNexa does not currently offer a dedicated India data residency region for user data. Call audio, transcripts, and post-call analysis are processed and stored in DialNexa’s infrastructure. There is no option to restrict data storage to India-based data centers at this time. This page will be updated if and when dedicated India data residency becomes available.

​
What This Means for Your Deployment

If your organization or your customers have contractual or regulatory requirements for India data localisation (for example, under RBI guidelines for financial services, or enterprise supplier contracts), DialNexa’s current infrastructure does not satisfy those requirements. For organizations with strict data localisation requirements, options to explore include:
  • On-premise deployment: DialNexa’s enterprise tier includes on-premise deployment options. Contact [email protected] for details.
  • Private cloud on Indian infrastructure: Deploying DialNexa on AWS Mumbai, Azure India Central, or Google Cloud Mumbai regions via an enterprise arrangement.

​
What Is Confirmed About Data Handling

  • Call audio and transcripts are processed in DialNexa’s infrastructure
  • Data in transit uses TLS encryption
  • Data at rest is encrypted
  • DialNexa acts as a data processor for call data; your organization is the data controller
For a Data Processing Agreement (DPA) or sub-processor list, contact [email protected].
Data residency refers to the requirement that data about Indian users and transactions be stored and processed within India’s geographic borders. DialNexa’s India region addresses this by ensuring that all call data - recordings, transcripts, post-call analysis - is stored and processed in data centers located in India, without being transferred abroad for processing.

​
Why Data Residency Matters

India’s regulatory landscape increasingly emphasizes data localisation:
  • DPDP Act (2023): India’s Digital Personal Data Protection Act requires certain categories of personal data to remain within India. The specific data categories subject to localisation are defined by implementing rules (being finalized).
  • RBI guidelines: Businesses in the financial services sector are required to store payment and transaction data exclusively in India.
  • SEBI and IRDAI: Securities and insurance regulators have their own data localisation requirements for regulated entities.
  • Contractual requirements: Many Indian enterprises have supplier contracts that require their data to remain within India, regardless of statutory requirements.
For voice AI deployments that process personal data (names, phone numbers, conversations), data residency is a practical compliance requirement for many Indian organizations.

​
What the India Region Covers

When the India region is selected for a workspace, the following data is stored and processed exclusively in DialNexa’s India-based infrastructure:
Data typeStored in IndiaProcessing location
Audio recordingsYesIndia (transcription processing)
TranscriptsYesIndia
Post-call analysis resultsYesIndia (LLM inference routed through India)
Tool call logsYesIndia
Call metadata (IDs, timestamps, durations)YesIndia
Agent configurationsYesIndia
What is NOT covered by India region:
Data typeNote
LLM inference for GPT modelsOpenAI API calls may be processed outside India. For full LLM data residency, use Azure OpenAI with India region, or Claude via Bedrock on AWS (India region).
TTS synthesisElevenLabs and Cartesia APIs process audio outside India.
Account/billing dataStored in DialNexa’s global billing infrastructure.
For full end-to-end data residency including LLM inference and TTS synthesis, contact [email protected] about Enterprise options including on-premise deployment or Azure OpenAI / AWS Bedrock integration with India region.

​
Enabling the India Region

The data region is set per workspace and cannot be changed after the workspace is created. Select the India region when creating the workspace.
1

Create a new workspace

In the dashboard, open the workspace switcher (top left) and click + Create New Workspace.
2

Select the India region

During workspace creation, in the Data Region dropdown, select India. This option routes all call data storage and processing to DialNexa’s India data center.
3

Complete workspace creation

Name the workspace and click Create. The region is locked after this point.
4

Verify the region

After creation, the workspace settings page shows the configured region. Confirm it shows India.
The data region is immutable after workspace creation. If you need to change the region for an existing workspace, you must create a new workspace with the correct region and migrate your agents and configuration to it. Call history and recordings from the old workspace cannot be migrated.

​
Migrating an Existing Workspace to India Region

If you currently operate on a non-India region workspace and need to move to India region:
  1. Create a new workspace with India region selected
  2. Recreate agents: Re-create all agent configurations in the new workspace (agent configs can be exported as JSON from the agent settings)
  3. Reassign phone numbers: Transfer phone numbers to the new workspace (for bring-your-own numbers, update the webhook configuration; for DialNexa-purchased numbers, contact support)
  4. Update API integrations: Update all API calls and webhook configurations to reference the new workspace’s resources
  5. Redirect traffic: Update any inbound call routing to point to the new workspace’s numbers
  6. Archive the old workspace: Once traffic is fully on the new workspace, archive the old one
Historical call data in the old workspace cannot be moved to the new workspace. It will remain accessible in the old workspace until its retention period expires or until you delete it.

​
Data at Rest and in Transit

At rest: All data stored in DialNexa’s India data center is encrypted using AES-256. Encryption keys are managed by DialNexa and are stored separately from the data. In transit: All data in transit between your system and DialNexa’s API uses TLS 1.3. Audio data between the caller’s device/carrier and DialNexa’s India servers is transmitted over encrypted SRTP (for VoIP) or encrypted PSTN signaling. Third-party services: When your agent uses external tools (your custom function endpoints), data is sent to your specified endpoint. Ensure your tool endpoints are also hosted in India if full data residency is required.

​
Compliance Documentation

If you need documentation of DialNexa’s India data residency for audit, procurement, or regulatory purposes:
  • Data Processing Agreement (DPA): Available from [email protected]. Documents DialNexa’s role as a data processor, the categories of data processed, and the technical safeguards in place.
  • Sub-processor list: DialNexa maintains a list of sub-processors (cloud infrastructure providers) used for India region deployments. Available on request.
  • SOC 2 report: DialNexa’s SOC 2 Type II report covers controls relevant to data security and availability. Available under NDA from [email protected].