> For the complete documentation index, see [llms.txt](https://legal.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legal.dispel.com/security-and-data-protection/compliance/data-residency.md).

# Data Residency

Data residency refers to the geographic location where customer data is processed and stored.

### Overview <a href="#h_d11371f5e0" id="h_d11371f5e0"></a>

Data residency refers to the geographic location where customer data is processed and stored. At Dispel, we prioritize transparency and control, allowing customers to manage their data locations based on their specific requirements. This guide explains how data residency works across different Dispel deployment models:

* [Dispel SaaS](#h_d723768bf3)
* [Customer Cloud](#h_c4e8126fb7), and&#x20;
* [On-Premise deployments](#h_c4e8126fb7)

### Dispel SaaS Data Residency <a href="#h_d723768bf3" id="h_d723768bf3"></a>

For customers utilizing Dispel SaaS, all data processing occurs through Dispel-managed infrastructure. Our sub-processors are located in the United States, as listed in our official [Sub-Processor List](/privacy/sub-processor-list.md). The governance of data protection under Dispel SaaS follows the [Dispel Data Protection Addendum](/privacy/data-subject-consent-form.md), ensuring compliance with industry standards and security best practices.

Key Points:

* Dispel SaaS leverages U.S.-based sub-processors.
* Data protection is governed by Dispel’s Data Protection Addendum.
* Customers can control their data routing preferences through available geographic deployment options.

### Customer Cloud & On-Premise Deployments <a href="#h_c4e8126fb7" id="h_c4e8126fb7"></a>

For Customer Cloud and On-Premise deployments, Dispel does not act as a sub-processor. Instead, the customer maintains full responsibility for data storage, processing, and compliance. This means that all data residency decisions, infrastructure management, and legal obligations fall under the customer's direct control.

Key Points:

* Dispel is not a sub-processor in these environments.
* The customer assumes full responsibility for data security and residency.
* Customers manage their own infrastructure, compliance, and access control.

{% hint style="info" %}
Learn more about [Shared Responsibility](/security-and-data-protection/shared-security-model/shared-responsibilities.md) on the Dispel Zero Trust Engine.
{% endhint %}

***

### Customer-Controlled Data Routing <a href="#h_3d5f4579de" id="h_3d5f4579de"></a>

During daily operations, Dispel allows customers to control where their data routes based on the geographic locations they select for their deployments. Data residency is primarily determined by the following factors:

<details>

<summary>Region Selection</summary>

* Customers choose a primary geographic region for their SD-WAN deployment.
* This decision influences where network services are hosted.
* Data does not reside in the network (with the exception of security information and enforcement rules), but will transit through those geographies.

</details>

<details>

<summary>Virtual Desktop Geolocation</summary>

* The Virtual Desktop location is configurable via the Dispel dashboard.
* Users can select from available data center locations to optimize performance and compliance needs.
* Data during the session is stored at these locations.

</details>

<details>

<summary>Wicket Deployment Location</summary>

* A Wicket serves as an access gateway and its geographic location affects routing policies.
* Customers determine where to deploy Wickets based on security and latency preferences.
* Data does not reside in the Wicket (with the exception of security information and enforcement rules), but will transit through these locations.

</details>

### Managing Data Residency in Dispel <a href="#h_31372b91d5" id="h_31372b91d5"></a>

To configure data residency settings:

1. Log into your Dispel Dashboard.
2. Navigate to Regions > Select or modify the Region for your environment.
3. Navigate to Stacks > Configure the Virtual Desktop location as needed.
4. Ensure Wicket deployments align with your data residency and access policies.

By selecting the appropriate geographic regions for these components, customers can effectively manage data residency, latency, and compliance needs.

***

## Summary

* Dispel SaaS deployments use U.S.-based sub-processors and follow Dispel’s Data Protection Addendum.
* Customer Cloud & On-Premise deployments place full data responsibility on the customer, with Dispel not acting as a sub-processor.
* Customers have control over data routing based on Region, Virtual Desktop, and Wicket deployment locations.
* Geolocation settings are configurable via the Dispel Dashboard.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://legal.dispel.com/security-and-data-protection/compliance/data-residency.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.