> 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/security-and-data-sovereignity/where-are-glbnxt-servers-located.md).

# Where are GLBNXT servers located?

GLBNXT own servers are located within the European Union. All compute, storage, and data processing takes place on EU-based infrastructure, ensuring that your data remains within European jurisdiction at every stage and is subject to European data protection law rather than the legal frameworks of other regions.

This is not a regional option you need to select or an additional feature to request. European data residency is the default and only way GLBNXT operates. It is built into the architecture of the platform from the ground up, which means there is no risk of your data being inadvertently routed or replicated outside of EU boundaries.

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

Organisations that require complete control over their infrastructure location can also opt for a private deployment, where GLBNXT Platform is installed within your own facilities or dedicated cloud environment. In that scenario, the servers are wherever you choose them to be, within the boundaries you control.


---

# 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/security-and-data-sovereignity/where-are-glbnxt-servers-located.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.
