> 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/infrastructure/data-hosting-and-residency.md).

# Data Hosting & Residency

## AWS Regions

| Region           | Location           | Role              |
| ---------------- | ------------------ | ----------------- |
| **eu-central-1** | Frankfurt, Germany | Active region     |
| **eu-north-1**   | Stockholm, Sweden  | Active region     |
| **eu-west-1**    | Dublin, Ireland    | Disaster recovery |

Frankfurt and Stockholm operate in an active/active configuration with automatic data replication. If one region experiences a disruption, traffic fails over to the other. Dublin serves as an additional disaster recovery region.

## Data Residency

* ilert stores all customer data in the AWS regions above, all in the EU
* Some sub-processors process data outside the EU, for example in the United States; see [Sub-processors](/trust-center/legal/subprocessors.md)
* No customer data is transferred to non-EU jurisdictions without appropriate safeguards (Standard Contractual Clauses, EU-U.S. Data Privacy Framework)
* Migration to alternative European providers is possible within 6–8 weeks if legally required

## Data Center Certifications

ilert's infrastructure runs on AWS data centers holding ISO/IEC 27001, SOC 1/2/3, and PCI DSS Level 1 certifications. Full list at [AWS Compliance Programs](https://aws.amazon.com/compliance/programs/).

## Backup Infrastructure

* Daily backups stored in separate EU locations
* AES-256 encryption on all backup data
* Backups are deleted after 30 days
* Integrity and restoration tests every 90 days
* Backups are managed by ilert's operations team; customers can export data via API

## Additional Services

ilert operates its data warehouse on ClickHouse, self-hosted within the AWS regions listed above. No separate data-warehousing provider is engaged.

For the complete list of providers, see [Sub-processors](/trust-center/legal/subprocessors.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.ilert.com/trust-center/infrastructure/data-hosting-and-residency.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.