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

# Data Residency and Compliance

### Data Residency

We do not store any data from third party ERP systems, and this includes within our logs and cached data. We act as a pass-through layer, connecting you with Your Customer's data. However, given that data must pass through our systems when it is being served via API.1, we recognise that there is a requirement to be bound by EU data regulations.

We ensure that all services that we use are hosted in regions located within the EU.

You can find out more about what this means at the following resources:

### Azure

* EU Data Boundary: <https://learn.microsoft.com/en-us/privacy/eudb/eu-data-boundary-learn>
* Customer Success Stories: <https://customers.microsoft.com/en-us/search?sq=&ff=story_industry_friendlyname%26%3EBanking%20and%20Capital%20Markets%26%26story_product_categories%26%3EAzure%26%26story_country_region%26%3EEurope&p=8&so=story_publish_date%20desc>

### Auth0

* Security: <https://auth0.com/security>
* Data Privacy: <https://auth0.com/explore/data-privacy/>


---

# 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.zwapgrid.com/security/data-residency-and-compliance.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.