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

# Trust and security

Find Kilo security guidance, assessment status, privacy contacts and the responsibilities for your deployment.

Kilo is the IoT platform operated by CHIRP USA LLC. Use these pages to prepare your deployment, understand our security assessment status and contact us about a problem. Hardware distribution by Kilo Electronics is a separate activity.

Start with the [Customer security guide](/customer-security-guide.md). It covers account access, credentials, integrations, AI use and changes when people leave.

| What you need                                            | Where to go                                                                          |
| -------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| Report unexpected access or a possible vulnerability     | [Report a security vulnerability](/incident-response-and-vulnerability-reporting.md) |
| Check what has been assessed                             | [Security assessment status](/compliance-status.md)                                  |
| Prepare account and device security                      | [Security controls](/security-controls.md)                                           |
| Ask about personal information                           | [Privacy and data protection](/privacy-and-data-protection.md)                       |
| Prepare a personal-data processing agreement             | [Processing agreements](/processing-agreements.md)                                   |
| Understand hosting and provider responsibilities         | [Infrastructure and providers](/infrastructure-and-subprocessors.md)                 |
| Identify data categories and available formats           | [Data and export formats](/data-and-export-formats.md)                               |
| Plan data return, deletion or moving service             | [Data export and switching](/data-export-deletion-and-switching.md)                  |
| Divide security tasks between Kilo and your organisation | [Shared security responsibilities](/shared-responsibility.md)                        |
| Prepare a camera deployment                              | [Video and privacy](/video-and-kilo-lens.md)                                         |

For security, privacy or service-arrangement enquiries, contact **info \[at] kiloiot.de** (replace `[at]` with `@`). Keep passwords, private keys, footage and unnecessary personal information out of the first message.


---

# 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.kiloiot.io/trust-security-compliance.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.