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

# Data residency

IDlayr operates two independent data regions:

| Region | API host prefix     |
| ------ | ------------------- |
| EU     | `eu.api.idlayr.com` |
| US     | `us.api.idlayr.com` |

A workspace is provisioned in one region during onboarding. All API calls for that workspace must be made against the workspace's region. The token endpoint, product endpoints, and callback delivery all run from the same region.

## Choosing a region

The choice is driven by:

* **Where your end users are.** Latency to the carrier-facing infrastructure matters for Secure SNA and Discovery.
* **Where your data must be processed.** GDPR (EU) or US-jurisdictional requirements may constrain the choice.
* **Where your existing IDlayr workspace already lives** — multi-region workspaces are not currently supported.

Moves between regions are not automatic. If you need to change region post-onboarding, contact IDlayr support to plan a migration.

## What's stored where

The verification check itself is processed entirely within the region. Identifying information about the request (workspace, project, MSISDN, timestamps, results) is stored in the region's data centre. Personally identifiable values are not replicated cross-region.

Specifics of what each product retains are on the product page's **Data handling** section.


---

# 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.idlayr.com/get-started/concepts/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.