> 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

### 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 %}

### 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 the following data residency options for customers with regional storage or processing requirements:

<table data-header-hidden="false" data-header-sticky data-search="false"><thead><tr><th>Region</th><th>Description</th><th>Availability</th></tr></thead><tbody><tr><td><span data-gb-custom-inline data-tag="emoji" data-code="1f1ea-1f1fa">🇪🇺</span> EU</td><td>Default for EU registrations.</td><td>All customers</td></tr><tr><td>🇺🇸 United States</td><td>Default for US registrations.</td><td>All customers</td></tr><tr><td>🇬🇧 United Kingdom</td><td>Default for UK registrations.</td><td>All customers</td></tr><tr><td><span data-gb-custom-inline data-tag="emoji" data-code="1f1e8-1f1e6">🇨🇦</span> Canada</td><td>Data stored within Canada.</td><td>Growth plan and beyond</td></tr><tr><td>🇦🇪 United Arab Emirates</td><td>Data stored within the UAE.</td><td>Growth plan and beyond</td></tr><tr><td>🇸🇬 Singapore</td><td>Data stored within Singapore.</td><td>Growth plan and beyond</td></tr><tr><td>🇦🇺 Australia</td><td>Data stored within Australia.</td><td>Growth plan and beyond</td></tr><tr><td>🇧🇷 Brazil</td><td>Data stored within Brazil.</td><td>Growth plan and beyond</td></tr><tr><td>🌍 Custom</td><td>Data stored within needs.</td><td>Enterprise plans</td></tr></tbody></table>

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 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://docs.complycube.com/documentation/trust-and-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.