> 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/privacy-policy.md).

# Privacy policy

Learn how your data is handled and protected.

Ubiquity is committed to protecting your data and handling personal information responsibly and securely.

This page provides a high-level overview of how we approach privacy. Our full Privacy Policy, including detailed information about how we collect, use, store, and protect data, is maintained on our website.

***

### How we approach privacy

We design and operate Ubiquity with security and privacy in mind. This includes:

* Protecting data in transit and at rest
* Applying access controls to ensure only authorised users can access data
* Monitoring and maintaining our systems to meet security and compliance requirements
* Supporting customers in meeting their own privacy and compliance obligations

***

### Where to find the full policy

For complete and up-to-date information, please refer to our full Privacy Policy:

<https://www.ubiquity.co.nz/privacy-policy>


---

# 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/privacy-policy.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.
