> ## Documentation Index
> Fetch the complete documentation index at: https://docs.movoice.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Data residency

# Data residency

For customers with strict data sovereignty requirements, Movoice AI provides **Data Residency** options.

## What is Data Residency?

It is the physical and geographic location where an organization's data is stored. Some industries (like Banking or Healthcare) or entire regions (like the EU or India) require that certain types of data never leave their borders.

## Our Approach

### 1. Multi-Region Deployment

Enterprise customers can choose where their dedicated instances are hosted. Our platform supports deployment in:

* **India** (Mumbai/Delhi)
* **United States** (East/West)
* **European Union** (Frankfurt/Ireland)
* **Southeast Asia** (Singapore)

### 2. Component Isolation

You can specify which layers of the stack should remain resident:

* **Data Storage**: Only stores logs and recordings in the chosen region.
* **Compute**: Voice processing happens in the chosen region.
* **Complete Isolation**: The entire stack, including the API, is isolated to a specific region.

### 3. Compliance Mapping

We help you map your deployment to local requirements such as **DPDP** (India), **GDPR** (Europe), or **PIPEDA** (Canada).

## Getting Started

To configure a residency-specific instance, please reach out to our [Enterprise Solutions Team](mailto:enterprise@movoice.ai).