> 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/what-happens-to-our-data-if-we-cancel-our-subscription.md).

# What happens to our data if we cancel our subscription?

If you cancel your GLBNXT subscription, your data belongs to you and you remain in control of what happens to it. Before your environment is decommissioned, you will have the opportunity to export your data in a structured format so that nothing is lost and your organisation retains everything it needs to transition smoothly.

Once the export period has passed and your environment is closed, your data is permanently and securely deleted from GLBNXT infrastructure. It is not retained, archived, or used in any form after your subscription ends. You will receive confirmation of deletion upon request, which can be used to satisfy your own internal data governance or compliance obligations.

The exact timeline for data export and deletion, as well as the formats available for export, will be outlined in your service agreement. If you have specific requirements around the offboarding process, such as certified deletion documentation or a supervised data handover, speak with your GLBNXT account team well in advance of any planned cancellation so that the process can be managed to your satisfaction.


---

# 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/what-happens-to-our-data-if-we-cancel-our-subscription.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.
