> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/security-and-trust.md).

# Security and trust

Overview of Ubiquity’s approach to security.

Security and reliability are core to how Ubiquity is designed and operated.

This page provides a high-level overview of our approach. For full and up-to-date details, refer to our Security page on the Ubiquity website.

### Our approach

We build and operate Ubiquity with a security-first mindset, covering infrastructure, application design, and day-to-day operations.

This includes:

* Protecting data in transit and at rest
* Enforcing strong authentication and access controls
* Monitoring systems for performance, reliability, and security risks
* Regularly updating and patching infrastructure
* Designing features with security and risk management in mind

***

### Compliance and standards

Ubiquity follows recognised security practices and frameworks to ensure customer data is handled appropriately and securely.

***

### Availability and reliability

We design the platform to be stable and resilient, with monitoring and processes in place to quickly identify and respond to issues.

***

### Learn more

For detailed information about our security practices, infrastructure, and policies, see:

<https://www.ubiquity.co.nz/security>

This is the source of truth and is kept up to date as our platform evolves.


---

# 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.ubiquity.co.nz/security-and-trust.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.
