> 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/eu-data-act.md).

# EU Data Act

{% hint style="info" %}
🇩🇪 [Diese Seite auf Deutsch lesen (EU Data Act)](https://docs.ilert.com/trust-center/deutsche-versionen/eu-data-act.md)
{% endhint %}

{% hint style="info" %}
**Version 1.0 · valid from 9 November 2026** · [Versions and changes](https://docs.ilert.com/trust-center/legal/versions/eu-data-act.md)
{% endhint %}

This page gives the information that the EU Data Act (Regulation (EU) 2023/2854) requires from providers of data processing services such as ilert (Articles 26, 28 and 29). The [Terms of Service](https://docs.ilert.com/trust-center/legal/terms-and-conditions.md) govern; this page summarises their Clause 18.

## Switching to another provider

Customers with their registered office or an establishment in the European Union can switch to another provider or to their own IT infrastructure, or have their data erased, at any time, whatever the agreed term (Clauses 18.6 and 18.7):

1. **Switching Notice:** the customer notifies ilert in text form, for example to <support@ilert.com>, whether it wishes to switch or to have its data erased, and for a switch to another provider gives the details of that provider needed for the switch. The notice period is two months from receipt. A renewal that would begin after receipt does not take place.
2. **Transition Period:** for a switch, the Transition Period begins at the end of the notice period. ilert continues the service under the contract for up to 30 calendar days, extendable once by the customer, and assists the customer and the third parties it authorises with the switch (Clause 18.3).
3. **End of the contract:** the contract ends when the switch is complete, which the customer confirms; if the customer has not reported by the end of the Transition Period that the switch has failed, it counts as complete then. If the switch fails, the contract continues. If the customer only wants its data erased, the contract ends at the end of the notice period. ilert confirms the end of the contract in text form.
4. **Retrieval Period:** for 30 calendar days after the end of the contract, the customer can export its data free of charge (Clause 18.4).
5. **Erasure:** ilert then erases all customer data, including backups, no later than 90 days after the end of the contract or of a Transition Period after it, and confirms the erasure in text form (Clause 18.5). On request, ilert erases the data at the end of the contract, without a Retrieval Period, within the periods in Annex II of the Data Processing Agreement. Data that ilert is legally obliged to retain is erased when that obligation ends.

All customers, wherever they are established, can use the Transition Period (except in free trials), the Retrieval Period and the erasure when their contract ends.

## Export methods and data formats

* Customers export their data themselves through the ilert REST API, in JSON, during the Transition Period and the Retrieval Period; on request, ilert carries out the export (Clause 18.4). The export covers all data available through the API.
* Exportable data is all customer data, including the configuration of the account and the history of alerts, incidents and calls. Excluded are only ilert's internal system logs and operating metrics, where their export would put ilert's trade secrets at risk and the exclusion does not impede or delay a switch.
* The [API reference](https://api.ilert.com/api-docs/) describes the API's resources with their data structures and formats, and can be downloaded as an OpenAPI specification. It also gives the API's rate limits.
* Known restriction: phone numbers that ilert provides for call routing cannot be ported to the customer or to another provider, unless the law requires it (Clause 13.4).

## Fees

* **Service fees:** the prices on [www.ilert.com/pricing](https://www.ilert.com/pricing) or those agreed in the individual contract. Plans with a term of one or more years cost less than monthly plans. The fees are payable until the end of the contract, including during the Transition Period.
* **Switching charges:** none. The switch, ilert's assistance with it and the data export are free of charge (Clause 18.8).
* **Early termination fee:** if a contract with a fixed term ends early because the customer switches or has its data erased, the customer pays the agreed fees in full for the rest of the contract year in which the contract ends, and 80% of the agreed fees for the rest of the term after that year. Fees for additional users and quotas (Clause 11.7) are not included. Fees paid in advance for the time after the end of the contract are credited against the fee, and ilert refunds any excess. The customer may prove that ilert has suffered no loss or a substantially lower loss (Clause 18.7).

## Jurisdiction of the infrastructure

* ilert GmbH is a German company, based in Cologne.
* ilert's platform stores customer data at Amazon Web Services EMEA SARL (Luxembourg), in the AWS regions Frankfurt (Germany) and Stockholm (Sweden). This infrastructure is subject to EU law and to the law of Germany and Sweden. Amazon Web Services EMEA SARL belongs to the Amazon group, whose parent company is in the United States, so US authorities can address requests to Amazon under US law.
* Sub-processors that provide individual functions, such as the delivery of notifications and AI features, process data in the countries named in the [sub-processor list](https://docs.ilert.com/trust-center/legal/subprocessors.md) and on [Access from Outside the EU/EEA](https://docs.ilert.com/trust-center/legal/subprocessors/access-from-outside-the-eu-eea.md).

## Measures against unlawful government access

**Technical**

* ilert's platform stores customer data in the AWS regions Frankfurt and Stockholm.
* Data is encrypted in transit with TLS 1.2 or higher, and at rest with AES-256, with keys managed in AWS Key Management Service.

**Organisational**

In addition to the Terms of Service, ilert commits to the following:

* ilert discloses customer data to an authority only where it is legally obliged to and the disclosure is lawful under EU law and the law of the member state concerned.
* A decision of a court or an authority outside the EU does not by itself oblige ilert to disclose data. ilert checks every such request for its legal basis and for a conflict with EU law or the law of the member state concerned. For non-personal data held in the EU, ilert complies only if the request is based on an international agreement, such as a mutual legal assistance treaty, or meets the conditions of Article 32(3) of the Data Act. ilert does not comply with a request that would create such a conflict, and uses the legal remedies available against it.
* ilert discloses only the minimum amount of data permissible. It informs the customer of a request before complying with it. Only where the request serves law enforcement purposes may ilert wait, for as long as this is necessary to keep the law enforcement effective (Article 32(4) and (5) of the Data Act).

**Contractual**

* Sub-processors outside the EU/EEA that process personal data under the EU Standard Contractual Clauses must, under their Clause 15, notify requests from public authorities, review their legality and challenge them where there are grounds to do so.
* Amazon states that it discloses customer information in response to government demands only where a legally valid and binding order requires it, and that it notifies customers before disclosing content, unless this is prohibited ([Amazon information requests](https://aws.amazon.com/compliance/amazon-information-requests/)).


---

# 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/eu-data-act.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.
