> 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/why-does-data-centre-location-alone-not-guarantee-data-sovereignty.md).

# Why does data centre location alone not guarantee data sovereignty?

Because sovereignty is determined by legal jurisdiction over the provider, not the physical location of the servers. The US CLOUD Act, enacted in 2018, grants US law enforcement the authority to compel any US headquartered company to hand over data in its possession or control, regardless of where that data is stored. A US provider running servers in Frankfurt or Amsterdam is still legally obligated to comply with a US government data access request, even if doing so directly conflicts with GDPR Article 48, which prohibits transfers of personal data to third country authorities without a proper legal basis under EU law.

This is not a theoretical risk. The CJEU's Schrems II ruling invalidated the EU US Privacy Shield on precisely this basis, and the European Data Protection Board has confirmed that service providers subject to EU law cannot legally disclose personal data to US authorities based on CLOUD Act requests alone.

GLBNXT resolves this conflict structurally by working exclusively with vendors headquartered in Europe and operating under European legal jurisdiction. No component of the platform is subject to the CLOUD Act or any equivalent extraterritorial legislation. Data access requests can only be made through European legal channels with full judicial oversight. This means organisations using GLBNXT do not inherit the compliance risk that comes with any dependency on a US controlled provider, and European data protection law applies without conflict from foreign legislation.


---

# 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/why-does-data-centre-location-alone-not-guarantee-data-sovereignty.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.
