> 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/processing-agreements.md).

# Data Processing Agreement

How to set up a GDPR data processing agreement (DPA) with Kilo: controller and processor roles, what to send, scope.

Yes, on request. Kilo prepares a data processing agreement (DPA) for your specific service, and it is signed once completed; this page explains it but is not the agreement itself. If your organization uses Kilo to handle personal data, ask for one before that data goes in. It is completed for your actual service: the features you use, the people and data involved, and the providers that handle it. A general privacy notice or a security statement does not replace it.

## Who is the controller and who is the processor?

* **Your organization is usually the controller.** It decides why personal data is collected and how it is used, for example an employer deciding to track staff locations. It needs its own lawful purpose and must inform the people concerned.
* **Kilo may act as your processor** for the agreed service. It handles that data on your instructions, under the agreement.
* **Kilo is also a controller for its own purposes**, such as running your account, billing and protecting the service. The [Privacy Policy](https://kiloiot.io/privacy-policy/) covers those.

If you provide a service to another organization that is the real controller, say so; the agreement has to reflect that chain.

## What do I send to start a DPA?

Email **info \[at] kiloiot.de** (replace `[at]` with `@`) with:

1. Your legal organization name, and whether you act for another organization.
2. The Kilo features you will use, including the AI assistant and any integrations.
3. Whose data is involved, what data it is and why you need it, including any sensitive categories.
4. Where data must be stored and from where support may access it.
5. Your requirements for security, recovery, privacy requests and the end of the service.
6. Your contacts for privacy, contracts and security incidents.

Keep passwords, private keys, data exports, footage and identity documents out of that first email.

## What does the agreement cover?

What is processed and why, your instructions, confidentiality, security measures, other providers that handle the data, help with privacy requests and data breaches, audit rights, and what happens to the data when the service ends. Check the actual parties, schedules and terms before you sign. A protection the law requires can't be waived by agreeing to go without it.

## Which other providers handle the data?

That depends on the features you use. The AI assistant sends requests to a model provider, alerts go through notification providers, and the platform runs on Hetzner. A provider that processes data for Kilo on your behalf is a **subprocessor**; the agreement needs to name the ones that apply to your service and how new ones are approved. The examples above are not a complete list of subprocessors. See [Where Is Kilo Hosted?](https://docs.kiloiot.io/trust-security-compliance/infrastructure-and-subprocessors.md)

If data leaves the European Economic Area, the transfer needs its own legal safeguard. An EU server, an encrypted connection or a provider's name doesn't settle that by itself.

## What happens with privacy requests and breaches?

* If someone asks your organization for their data or its deletion, tell Kilo what you need and when; keep the date you received the request and the result. See [How Does Kilo Handle Personal Data?](https://docs.kiloiot.io/trust-security-compliance/privacy-and-data-protection.md)
* Under GDPR, Kilo must tell you without undue delay after it becomes aware of a personal-data breach affecting your data. Your own duty to inform the authority and the people affected is separate.
* To report a suspected security problem, see [How Do I Report a Kilo Security Vulnerability?](https://docs.kiloiot.io/trust-security-compliance/incident-response-and-vulnerability-reporting.md)

## What happens to the data when the service ends?

You choose whether your personal data is returned or deleted, including copies at other providers and in backups, unless EU or member-state law requires it to be kept. Agree this before the end comes. Cancelling a subscription or closing a login is not the same thing; see [How Do I Export My Data or Leave Kilo?](https://docs.kiloiot.io/trust-security-compliance/data-export-deletion-and-switching.md)


---

# 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/processing-agreements.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.
