> 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/glbnxt-platform/how-does-platform-handle-audit-logging-and-compliance-reporting.md).

# How does Platform handle audit logging and compliance reporting?

GLBNXT Platform maintains comprehensive audit logs across all activity within your environment. Every user action, model interaction, API call, configuration change, and access event is recorded, giving your security and compliance teams a complete and tamper-evident record of how the platform is being used across your organisation.

Logs capture the details that matter for compliance purposes, including who did what, when, from where, and with what result. This level of visibility is essential for organisations operating under GDPR, NIS2, or internal governance frameworks that require demonstrable oversight of AI usage and data access.

All audit data is stored within your sovereign environment and is never shared with external parties. Retention periods are configurable to align with your legal and regulatory obligations, and access to log data is governed by the same role-based access controls that apply across the rest of the platform.

For compliance reporting, audit logs can be exported and integrated with your existing security information and event management tools, making it straightforward to incorporate GLBNXT activity data into broader organisational reporting workflows. This avoids the need to manage a separate compliance process specifically for your AI environment.

If your organisation is subject to regulatory audits or internal certification requirements, your GLBNXT account team can provide supporting documentation and work with your compliance team to ensure the audit logging configuration meets your specific obligations.


---

# 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/glbnxt-platform/how-does-platform-handle-audit-logging-and-compliance-reporting.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.
