# Data retention

> How long Kymo keeps event rows, what happens when you delete a site, and why the visitor hash means there is no long-lived identity to retain.

Canonical: https://kymo.in/docs/reference/data-retention
Last updated: 2026-07-21

## How long rows are kept

Event rows are retained so your historical charts keep working. There is no automatic expiry that deletes old events on a schedule.

What does not persist is identity. The visitor hash is derived fresh each day and rotates at UTC midnight (see [Cookieless identity](https://kymo.in/docs/concepts/cookieless)), so even though a pageview row is kept, the hash on it cannot be tied to a person or connected to any other day's rows.

## Deleting a site

Deleting a site removes its data. When you delete a site from your account, Kymo cascade-deletes every row tied to that domain — events and the derived AI-visibility tables — not just the site record.

This is deliberate. Domains change hands. Cascade-deleting means if a domain is later registered by a different account, the previous owner's traffic can never appear under the new owner's dashboard.

## Excluding versus deleting

Excluding your own traffic (via `?kymo=ignore` or a per-site excluded IP) prevents new events from being stored. It does not remove events already recorded. To remove data, delete the site.

There is no fixed retention window today — Kymo does not purge events on a schedule. Rows are kept until you delete the site.