> For the complete documentation index, see [llms.txt](https://docs.glbnxt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glbnxt.com/faq/general/where-is-my-data-stored.md).

# Where is my data stored?

Your data is stored exclusively on GLBNXT own infrastructure and European infrastructure. GLBNXT operates within EU-based data centres, ensuring that your information never leaves European jurisdiction during storage, processing, or transit. This is not a configuration option or an add-on feature; it is the default and only way GLBNXT operates.

For organisations with specific residency requirements, such as data that must remain within a particular country or region, GLBNXT can accommodate those needs as part of your deployment setup. Your account team will work with you during onboarding to ensure your configuration aligns with your legal and regulatory obligations.

If your organisation requires a private or dedicated deployment, GLBNXT Platform supports installation within your own cloud environment or on-premise infrastructure, giving you complete control over exactly where your data resides and who can access it. Details on deployment options are covered in the Platform documentation.


---

# 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.glbnxt.com/faq/general/where-is-my-data-stored.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.
