> 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/video-and-kilo-lens.md).

# Video and privacy

Prepare the privacy, access and security checks needed before a Kilo Lens deployment records real people.

Before a camera deployment records real people, obtain confirmation that the proposed service is ready for that use. Explain the site, cameras, purpose, people affected, who will have access and how long the information is needed. Complete the applicable privacy and security assessment before starting.

Your organisation must establish the lawful purpose, provide the required information to affected people and control access at the site. Collect only the footage and other information needed for that purpose. Discuss proposed analytics and external processing separately.

Contact **info \[at] kiloiot.de** (replace `[at]` with `@`) with the deployment description. Arrange an appropriate route if supporting material is needed; keep footage out of the initial ordinary message.

General product information does not approve a particular camera deployment. Read [Privacy and data protection](/privacy-and-data-protection.md) and [Shared security responsibilities](/shared-responsibility.md) alongside the product instructions.


---

# 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/video-and-kilo-lens.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.