---
slug: aufbewahrung
title: "How long is data retained?"
category: datenschutz
locale: en
updated: 2026-10-13
keywords: ["retention","period","deletion","180 days"]
questions: ["Which retention periods apply and can I change them?","Deletion periods","Retention","How long is raw data kept?","What happens to old data when I move to a smaller plan?","Why are old impressions missing from the raw data?","Why are old impressions temporarily missing from a report?","Does my changed retention period still apply after a backup is restored?","How long are backups kept?","How long are webhook deliveries kept?"]
url: https://bench.metrunio.com/en/help/aufbewahrung
---

# How long is data retained?

**Which retention periods apply and can I change them?**

Raw events are retained for 180 days by default, 90 days on the free Start plan; the period is configurable per tenant up to the plan’s limit and enforced automatically. Journeys, touchpoints and conversions share the period of the raw events they were derived from and are deleted with them, or earlier if a deletion is requested. If a change of plan lowers the limit below the configured period, we announce the reduction 30 days in advance.

| Data | Default | Control |
| --- | --- | --- |
| Raw events | 180 days, 90 on Start | configurable per tenant up to the plan’s limit, enforced by the worker |
| Queue entries (done) | 24 hours | automatic cleanup |
| Sessions and tokens | until expiry | automatic cleanup |
| Raw events of delivered ads (impression, viewability) | at most 180 days | with a longer period, removed from the measurement database afterwards; reports keep counting them from the analytics mirror until the period ends. The mirror carries no direct identifiers but can be linked back through record keys and is therefore not anonymous |
| Journeys, touchpoints, conversions | same as raw events | deleted by the worker with the raw-event period; earlier on a privacy request |
| Reach measured without consent | same as raw events | deleted by the worker; listed individually only from five views per source |
| Change log, including sign-ins | 180 days per entry | deleted by the worker; at the latest with the account |
| Answers to the post-purchase question | same as raw events | attached to the raw event and deleted with it |
| Matching data for attribution via the checkout | at most 24 hours | no longer used after that and deleted in regular operation, even without attribution; in backups until they expire |
| Webhook deliveries | content at most 24 hours, log 30 days | content goes once delivered or abandoned |
| Database backups | at most the last 14 daily ones, around two weeks | expire; not searched for individual records |
| Residual copies held by the cloud provider | at most 180 days after deletion | under the provider’s contract; we restore nothing from them |

## After moving to a smaller plan

If the new plan does not cover the configured period (for example 180 days after the trial ends on Start with 90), we do not shorten it right away. The admins receive an email with the day of the reduction, 30 days in advance, and the same appears under “Plan & usage”. Until then everything stays; after that we delete what is older than the new period. Choosing a plan with longer retention beforehand keeps everything.

Delivered ads are the exception in the other direction. After 180 days their raw rows no longer contribute anything: a viewable impression can reach an order or lead at most 30 days after delivery, and journeys and models read the contact, not the raw row. If you retain data for longer, we therefore remove those raw rows from the measurement database after 180 days. The contact stays in every journey, and your reports then come from the analytics mirror, which keeps the deliveries until your period ends. It can lag up to six minutes behind the measurement. If the analytics mirror ever falls more than 15 minutes behind, your reports are calculated from the measurement database until it catches up. During that time, deliveries older than 180 days are missing there. Reports covering the last 180 days stay correct throughout.

The period also covers the analytics mirror: whatever expires in the database is carried over there. Backups expire on their own cycle and are not searched to remove individual records. Residual copies held by the cloud provider are a separate matter: it removes what we have deleted under its contract at the latest after 180 days; we cannot restore anything from them. If a backup is restored, a run checks the restored data against the suppression list and deletes again what is suppressed. If you changed your retention period after the backup was taken, your change still applies: every change is also written to a journal outside the database, and we set the period from it again before the first deletion run. You don’t need to set it again.

> **Legal note:** Which period suits your purpose is for you as the controller to decide. A shorter period reduces the amount of data but also limits how far back you can report.

## Also asked

- Deletion periods
- Retention
- How long is raw data kept?
- What happens to old data when I move to a smaller plan?
- Why are old impressions missing from the raw data?
- Why are old impressions temporarily missing from a report?
- Does my changed retention period still apply after a backup is restored?
- How long are backups kept?
- How long are webhook deliveries kept?

## Related

- https://bench.metrunio.com/en/help/was-wird-gespeichert
- https://bench.metrunio.com/en/help/betroffenenrechte
- https://bench.metrunio.com/en/help/audit-log
- https://bench.metrunio.com/en/help/tarife