> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/trust-center/legal/versions/data-processing-agreement.md).

# Data Processing Agreement – Versions

{% hint style="info" %}
🇩🇪 [Diese Seite auf Deutsch lesen (Auftragsverarbeitungsvertrag – Fassungen)](https://docs.ilert.com/trust-center/deutsche-versionen/fassungen/auftragsverarbeitungsvertrag.md)
{% endhint %}

A new version applies to agreements concluded from its publication date. For existing agreements, it applies from the date given in our notice of the change, unless the customer objects; until then, the previously agreed version applies.

| Version                                                                                            | Published         | Status                      |
| -------------------------------------------------------------------------------------------------- | ----------------- | --------------------------- |
| [2.1](https://docs.ilert.com/trust-center/legal/data-processing-agreement.md)                      | 9 November 2026   | Current version             |
| [1.1](https://docs.ilert.com/trust-center/legal/versions/data-processing-agreement/version-1-1.md) | 23 September 2026 | Replaced on 9 November 2026 |

## Changes in version 2.1

* **Annex II:** the processing per function, with the types of data and the data subjects. Erasure within 24 hours after the customer deletes data, from backups after 35 days at the latest, and of all data within 90 days after the contract or the transition period ends; ilert certifies the erasure.
* **ilert as controller:** contract contacts, contract and billing data, app usage data for stability and abuse prevention, support correspondence, and marketing emails to people who have consented are ilert's own processing, outside this agreement. Account data in support requests is still processed on the customer's behalf.
* **Annexes III and IV:** ilert may change the technical and organisational measures only without lowering the overall level of protection. If an objection to a new sub-processor can't be resolved, the customer can terminate the Main Contract or the affected part, with a pro-rata refund. Signed copies include both annexes as of the date of signature.
* **Editorial:** Clauses 1 to 10 match the official text of the standard contractual clauses word for word; Annexes I and II aligned in English and German. There was no published version 2.0.

## Changes in version 1.1

* Editorial corrections, with no change to rights or obligations.
* Version and date are shown. The brand is spelled "ilert" instead of "iLert".
* The processor's address is Bayenstr. 65, 50678 Köln.
* Two incomplete references to "Regulation (EU) 2016/679" completed (Clause 3(c), Clause 7.1(b)).
* Annex III links to the security controls on the Trust Center. Annex IV links to the sub-processor list on the Trust Center; its previous link no longer worked.
* German version: the typo "Organisatiorische" fixed. Annex IV links to the same sub-processor list as the English version.


---

# 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.ilert.com/trust-center/legal/versions/data-processing-agreement.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.
