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

# Welcome

ilert is a German incident management platform founded in 2011. ilert GmbH is headquartered in Cologne, Germany, holds ISO 27001:2022 certification, and hosts customer data in AWS data centers in the European Union.

This Trust Center is the central resource for security, compliance, and legal documentation.

{% hint style="success" %}
**System status:** [status.ilert.com](https://status.ilert.com) — current uptime and incident history.
{% endhint %}

***

## Quick Access

The following documents are most frequently requested during security reviews:

| Document                  | Access                                                                                                                                                          |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ISO 27001 Certificate     | [View details](/trust-center/compliance/iso-27001.md) or request copy via [sales@ilert.com](mailto:sales@ilert.com?subject=ISO%2027001%20certificate%20request) |
| Penetration Test Report   | Available under NDA — [sales@ilert.com](mailto:sales@ilert.com?subject=ilert%20pentest%20report)                                                                |
| Data Processing Agreement | [View DPA](/trust-center/legal/data-processing-agreement.md)                                                                                                    |
| Sub-processor List        | [View list](/trust-center/legal/subprocessors.md)                                                                                                               |
| Terms and Conditions      | [View ToS](/trust-center/legal/terms-and-conditions.md)                                                                                                         |

***

## Sections

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Security</strong></td><td>Controls, penetration testing, vulnerability disclosure</td><td><a href="/trust-center/security/security.md">Security Overview</a></td></tr><tr><td><strong>Compliance</strong></td><td>ISO 27001, GDPR, DORA, NIS2</td><td><a href="/trust-center/compliance/compliance.md">Compliance Overview</a></td></tr><tr><td><strong>Infrastructure</strong></td><td>Data hosting, residency, availability, DR</td><td><a href="/trust-center/infrastructure/infrastructure.md">Infrastructure Overview</a></td></tr><tr><td><strong>Legal</strong></td><td>Terms, privacy policies, DPA, DORA documents</td><td><a href="/trust-center/legal/legal.md">Legal Overview</a></td></tr><tr><td><strong>FAQ</strong></td><td>Security, compliance, and procurement questions</td><td><a href="/trust-center/faq.md">FAQ</a></td></tr></tbody></table>

***

## At a Glance

|                    |                                                                          |
| ------------------ | ------------------------------------------------------------------------ |
| **Headquarters**   | Cologne, Germany                                                         |
| **Certification**  | ISO/IEC 27001:2022                                                       |
| **Data hosting**   | AWS — Frankfurt + Stockholm (active/active), Dublin (DR)                 |
| **Data residency** | EU; some sub-processors outside the EU                                   |
| **SLA**            | 99.9% (up to 99.99% Enterprise)                                          |
| **RTO / RPO**      | ≤ 60 min / ≤ 15 min                                                      |
| **Encryption**     | TLS 1.2+ in transit, AES-256 at rest                                     |
| **Sub-processors** | [9 providers](/trust-center/legal/subprocessors.md), all EU or with SCCs |

***

## Contact

| Topic                                        | Email                  |
| -------------------------------------------- | ---------------------- |
| Security questions                           | <security@ilert.com>   |
| Compliance & audit requests                  | <compliance@ilert.com> |
| Legal & contracts                            | <support@ilert.com>    |
| Document requests (ISO cert, pentest report) | <sales@ilert.com>      |

*Last updated: March 2026*


---

# 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/readme.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.