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

# Data Residency

Learn what ComplyCube stores for KYC, AML, and identity verification, and review available data residency options.

### Overview

ComplyCube supports data residency for KYC, AML, and identity verification workflows across multiple regions.

{% hint style="info" %}
Data residency configurations apply to both processing and data at rest within the supported region you select.
{% endhint %}

{% hint style="info" %}
For more information about data handling, processing, and security documentation, visit the [ComplyCube Trust Center](https://trust.complycube.com).
{% endhint %}

### View your data hosting region

View your data hosting region on the [Data Governance page](https://portal.complycube.com/policies) in the ComplyCube Portal.

<figure><img src="https://2950143584-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fsw26JqCBnT6AEIbxAYyk%2Fuploads%2FAj2BPgqIJrIvSd6NUZ0T%2Fdata_hosting_region.png?alt=media&amp;token=c25bc3b8-8734-4147-878d-84b723af93c2" alt=""><figcaption><p>Data Governance page showing a hosted region.</p></figcaption></figure>

### What data ComplyCube stores

ComplyCube stores the following data categories as part of identity verification and compliance workflows:

<table data-header-hidden="false" data-header-sticky><thead><tr><th>Data type</th><th>Description</th></tr></thead><tbody><tr><td>Customer personally identifiable information</td><td>Customer data collected from user input, documents, and verification workflows, such as name, date of birth, address, and document details.</td></tr><tr><td>Business information</td><td>Business and company data used for account management, KYB workflows, and related compliance checks where applicable.</td></tr><tr><td>Biometric data</td><td>Selfie images, video frames, and liveness signals used to confirm user presence and prevent spoofing.</td></tr><tr><td>Verification data</td><td>Data generated during verification workflows, including check inputs, results, and related decisioning signals.</td></tr><tr><td>API logs</td><td>Request and response data used for platform operations, monitoring, and troubleshooting.</td></tr></tbody></table>

### Available data residency options

ComplyCube offers data residency in the following locations. For accounts registered in these locations, the **corresponding region is used by default**.

| Area         | Available locations                                                     |
| ------------ | ----------------------------------------------------------------------- |
| Europe       | <p>🇪🇺 European Union</p><p>🇬🇧 United Kingdom</p>                    |
| Americas     | <p>🇺🇸 United States<br>🇨🇦 Canada<br>🇧🇷 Brazil</p>                 |
| Asia Pacific | <p>🇦🇺 Australia<br>🇸🇬 Singapore<br>🇭🇰 Hong Kong<br>🇮🇳 India</p> |
| Middle East  | <p>🇦🇪 United Arab Emirates<br>🇸🇦 Saudi Arabia<br>🇶🇦 Qatar</p>     |

For accounts registered outside the listed locations, data hosting **defaults to the EU**.

{% hint style="info" %}
**Custom data residency** arrangements are available to **Enterprise customers** based on their data residency and processing requirements.
{% endhint %}

For **sub-processors**, **certifications**, and **security documentation**, visit the [ComplyCube Trust Center](https://trust.complycube.com).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.complycube.com/documentation/trust-and-compliance/data-residency.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.