> 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/alerting/overview/data-retention.md).

# Data retention

How long ilert retains customer data, including alerts, logs, configuration data, and the timelines that apply when an account is deleted.

This page describes how long ilert retains customer data. It covers two categories: **master data** (configuration such as services, escalation policies, and users) and **moving data** (event-shaped records such as alerts and logs). Account deletion timelines are described at the end of the page.

## Master data

ilert keeps personal data as long as required to provide the online services you have requested or registered for and comply with applicable laws. This includes configuration data such as services, escalation policies, users, integrations, and schedules. Master data is not subject to the moving data retention periods below and is only removed when you delete it or when your account is deleted.

## Moving data retention

Retention is measured from the time each record is created. When a record's retention period ends, the record is removed from the live system and cannot be recovered through the product.

{% hint style="info" %}
To keep records for longer than the periods below, copy them into your own storage: read them through the [ilert API](/developer-docs/rest-api/api-reference.md), or have a [Webhook alert action](/integrations/outbound-integrations/webhook.md) post alerts to an endpoint of yours as they are created and updated.
{% endhint %}

| Data type                                     | Retention |
| --------------------------------------------- | --------- |
| Alerts & notifications                        | 18 months |
| Alert source logs (event data & correlations) | 18 months |
| Webhook logs                                  | 18 months |
| Call flow logs                                | 6 years   |
| Call flow log details                         | 18 months |
| Event flow logs                               | 2 years   |
| Event flow log details                        | 18 months |
| Incidents & incident timeline                 | 6 years   |
| Conversations & chat messages                 | 6 years   |
| Maintenance windows                           | 6 years   |
| Audit logs                                    | 6 years   |
| Reports                                       | 10 years  |

{% hint style="info" %}
These are target periods. ilert is still rolling out the rotation that enforces them across the platform, so some records may currently be kept for longer than listed.
{% endhint %}

## Account deletion

If you request deletion of your account, all your account data — both configuration and moving data — is removed from the live system within 30 days (this is unrelated to the retentions mentioned above).

## Backups

Backups have their own retention cycle, separate from the periods above. Data deleted from the live system continues to exist in backups until those backups rotate out, after which it is no longer retained.


---

# 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/alerting/overview/data-retention.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.