> 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/dora-addendum.md).

# DORA Addendum

{% hint style="info" %}
🇩🇪 [Diese Seite auf Deutsch lesen (DORA‑Zusatzvereinbarung)](https://docs.ilert.com/trust-center/deutsche-versionen/dora-zusatzvereinbarung.md)
{% endhint %}

{% hint style="info" %}
**Version 2.0 · published 9 November 2026**\
Applies to agreements concluded from 9 November 2026. 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. [Versions and changes](https://docs.ilert.com/trust-center/legal/versions/dora-addendum.md)
{% endhint %}

(to ilert Terms & Conditions – [https://docs.ilert.com/trust-center/legal/terms-and-conditions](https://docs.ilert.com/trust-center/legal/terms-and-conditions.md))

**Last updated 2026‑11‑09 – UNSIGNED TEMPLATE**

> **Note:** Brackets \[…] indicate fields the Parties must complete on execution.

***

### Version History

| Date       | Version | Summary of Changes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| ---------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 2025-04-01 | v1.0    | Initial publication                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| 2025-10-30 | v1.1    | Clause 8.3 updated – cooperation with authorities (Arts. 30(2)(g) & 38 DORA)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| 2026-09-23 | v1.2    | Links to the ToS and the sub-processor list point to the ilert Trust Center                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| 2026-11-09 | v2.0    | Clause 2: this Addendum supplements the ToS in the version that applies between the Parties and prevails over it; liability under clause 14 of the ToS. Clause 3: definitions of Services, Firm Data, Applicable Law and Business Day; Major ICT Incident as in Art. 3(10) DORA; a Material Development must be reasonably likely to materially impair Vendor’s ability to deliver the Services. Clause 4.2: reference to remedies in Schedule A removed; notice without undue delay. Clause 4.3: the Parties may update Schedule A. Clause 6.2: preliminary and final report. Clause 6.5: training or exercises on reasonable request. Clause 7: transition period, retrieval and erasure under clauses 18.3 to 18.5 of the ToS; exit also on resolution or discontinuation of Vendor’s business. Clause 8: notice periods for audits, additional audits on reasonable suspicion of a material breach, no limits for competent authorities, copies of documentation, reference to Art. 30(2)(g) DORA only. Clause 9: notice without undue delay. Clause 10: termination of the Individual Contract. Schedule B: backups, sub-processor locations |

## 1 Parties

This DORA Addendum (“Addendum”) is entered into on **\[Date]** by and between:

* **\[Full legal name of Customer]** (“Firm”), and
* **ilert GmbH**, Bayenstr. 65, 50678 Cologne, Germany (“Vendor”).

The Firm and Vendor are each a “Party” and together the “Parties”.

## 2 Hierarchy & Incorporation

1. This Addendum supplements the **ilert Terms & Conditions (“ToS”)**, in the version that applies between the Parties, with the requirements of **Regulation (EU) 2022/2554 (“DORA”)**. The current and previous versions of the ToS are available at [https://docs.ilert.com/trust-center/legal/versions/terms-and-conditions](https://docs.ilert.com/trust-center/legal/versions/terms-and-conditions.md).
2. In the event of conflict, this Addendum prevails over the ToS. The Data Processing Agreement (“DPA”) remains unaffected.
3. All capitalised terms not defined herein have the meaning set forth in the ToS or in **Article 3 DORA**.
4. Liability under this Addendum is governed by clause 14 of the ToS.

## 3 Definitions *(excerpt)*

* **“Critical or Important Function”** – as in Art. 3(22) DORA.
* **“ICT Services”** – as in Art. 3(21) DORA.
* **“Major ICT Incident”** – an ICT‑related incident that meets the criteria of a major ICT‑related incident (Art. 3(10) and Art. 18 DORA).
* **“Permitted Location”** – the countries/regions listed in **Schedule B**.
* **“Service Levels”** – performance metrics in **Schedule A**.
* **“TLPT”** – a threat‑led penetration test under DORA Art. 26.
* **“Material Development”** – any circumstance reasonably likely to materially impair Vendor’s ability to deliver the Services (e.g. insolvency, acquisition, systemic outage).
* **“Services”** – the SaaS Services and Additional Services that Vendor provides to Firm under the Individual Contract and the ToS.
* **“Firm Data”** – all personal and non‑personal data that Firm or its Users provide to or create in the Services, including Customer Data.
* **“Applicable Law”** – the laws and regulations that apply to the respective Party, including DORA.
* **“Business Day”** – Monday to Friday, except public holidays in Cologne, Germany.

## 4 Service Standards

1. Vendor **shall meet or exceed** the Service Levels.
2. Failure to meet a Service Level obliges Vendor to:
   * **notify Firm without undue delay**,
   * implement a corrective action plan at no charge, and
   * report progress until restored.
3. The Parties shall review the Service Levels **annually** and may update Schedule A in writing.

## 5 Data Location & Sub‑processing

1. Vendor may subcontract the performance of ICT Services only in accordance with this Clause 5 and the DPA.
2. Vendor shall provide Services **only from Permitted Locations**.
3. Vendor shall give Firm 30 days’ prior written notice of any new or replacement sub‑processor or processing location. Firm may, on reasonable grounds, object in writing within that period; the Parties will collaborate in good faith to resolve the objection.

## 6 Security & Incident Handling

1. **Security Controls**: Vendor shall maintain an ISO 27001‑certified ISMS, enforce least‑privilege access, encrypt data in transit and at rest, and monitor compliance.
2. **Incident Notification**: Vendor shall inform Firm without undue delay and in any event within 4 hours of confirming a Major ICT Incident. The notice shall include known root cause, scope, impact, immediate mitigation, and next update timing. Vendor shall issue progress updates at least every 4 hours until the incident is resolved, deliver a written preliminary report within 5 Business Days of incident closure, and deliver a written final report with the root cause and the remediation measures within 20 Business Days of incident closure.
3. **Incident Assistance**: Vendor shall provide fee‑free assistance for investigation, forensics, regulator queries and final incident reports.
4. **Resilience Testing**: Vendor shall reasonably cooperate, at no additional cost, with Firm’s digital operational resilience testing, including TLPT and cyber table‑top exercises, and shall remediate resulting findings within mutually agreed timelines.
5. **Training & Awareness**: Vendor shall, on reasonable request, participate in Firm‑led ICT security awareness or operational‑resilience training or exercises where relevant to the Services.

## 7 Business Continuity & Exit

1. Vendor maintains BCP/DR with **RTO ≤ 60 min / RPO ≤ 15 min**; tests at least annually.
2. Upon termination, or upon Vendor’s insolvency, resolution or discontinuation of its business operations, Vendor shall:
   * continue providing the Services during the Transition Period under clause 18.3 of the ToS, if Firm requests it under that clause; and
   * grant Firm or its designee **step‑in rights** to systems holding Firm Data or supply a complete data export (JSON) within 5 Business Days of Firm’s request.
3. Clauses 18.4 and 18.5 of the ToS apply to the retrieval and erasure of Firm Data.

## 8 Audit & Regulatory Cooperation

1. Firm or its auditors may audit Vendor once per contract year (remote or on‑site). Additional audits following a Major ICT Incident or regulatory requirement, or on a reasonable suspicion that Vendor has materially breached this Addendum, are permitted. Firm shall give at least 10 Business Days’ notice of a remote audit and at least 30 days’ notice of an on‑site audit, unless a Major ICT Incident or a competent authority requires a shorter period. Competent authorities may audit Vendor without these limits on frequency and notice.
2. Vendor shall provide reasonable access to premises (physical or virtual), personnel, systems and documentation, and shall allow copies of relevant documentation to be taken.
3. Vendor shall fully cooperate with the supervisory, resolution, or other authorities competent for the Firm, including during TLPT observations, in the sense of Article 30(2)(g) DORA.

## 9 Material Developments

Vendor shall notify Firm in writing without undue delay of any Material Development that might materially impair Vendor’s ability to perform the Services or comply with Applicable Law.

## 10 Termination

Firm may terminate the Individual Contract and this Addendum with immediate effect if:

* instructed by a competent authority;
* Vendor materially breaches Applicable Law or this Addendum and fails to cure within 30 days;
* a Material Development or material weakness in Vendor’s ICT security jeopardises Firm’s operational resilience.

## 11 Confidentiality

Vendor shall keep all **Confidential Information** strictly confidential, disclose only to authorised persons under equivalent obligations, and comply with Applicable Law.

## Schedule A – Service Levels (aligned with ToS § 6)

| Metric                           | Target & Window                                                                                           | Definition          |
| -------------------------------- | --------------------------------------------------------------------------------------------------------- | ------------------- |
| **Notification Delivery**        | ≥ 99.9 % of First Responder Alerts delivered to telco / push provider **within 5 min** per calendar month | Mirrors ToS § 6.1.1 |
| **Web Application Availability** | ≥ 99.9 % uptime per calendar month                                                                        | Mirrors ToS § 6.1.2 |

*Exclusions*: Force Majeure & causes outside Vendor control (see ToS § 6.2).

## Schedule B – Permitted Locations & Sub‑processors

### 1 Vendor infrastructure

| Component       | Region                           | Processing | Storage |
| --------------- | -------------------------------- | ---------- | ------- |
| Active Region 1 | AWS **eu‑central‑1 (Frankfurt)** | ✓          | ✓       |
| Active Region 2 | AWS **eu‑north‑1 (Stockholm)**   | ✓          | ✓       |

Daily backups are stored in Frankfurt and Stockholm.

### 2 Authorised sub‑processors

The sub‑processors in the list at [https://docs.ilert.com/trust-center/legal/subprocessors](https://docs.ilert.com/trust-center/legal/subprocessors.md) (Annex IV of the DPA), including its page Access from Outside the EU/EEA, may process Firm Data for the services and in the locations stated there; these locations are Permitted Locations. Some of them are outside the EU/EEA, in particular in the United States; the list states the transfer mechanism for each. Where the list states that a sub‑processor is used only for a feature that can be switched off, Firm can avoid its processing by switching that feature off. Updates are subject to Clause 5.

## Schedule C – Update Commitment

Vendor shall review this Addendum at least annually and update it as necessary to remain compliant with DORA and related regulatory technical standards. Vendor shall provide Firm 30 days’ advance notice of any update; if Firm raises no objection within that period, the update will be deemed accepted.

***

## Signature Blocks

| Firm               | Vendor             |
| ------------------ | ------------------ |
| **\[Name, Title]** | **\[Name, Title]** |
| *Date:* \[‑‑‑]     | *Date:* \[‑‑‑]     |

***

© 2026 ilert GmbH – Template for customer execution; becomes binding only when signed.


---

# 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/dora-addendum.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.
