# Retention and deletion

Every website has a retention period, and every organisation a log retention period. Older data is deleted automatically, and you can export or delete everything whenever you choose.

## Retention period

Choose 90 days, 180 days, 395 days (the default, about 13 months) or 730 days in **Settings → Data retention and export**. The API accepts any whole number of days from 30 to 1,095.

| Data | Deleted |
| --- | --- |
| Visits, with their handoff tokens and journey links | Retention period after the visit |
| Install events, with their journey links | Retention period after the install was reported |
| Delivery records | Retention period after their last update |
| Reconstruction signals: network and browser hashes, OS family, time zone, language, architecture | Within about a minute after the reconstruction window ends; all of them when reconstruction is turned off or the organisation moves to Free |
| Logs | After the organisation’s log retention: 30 days by default, from 7 days up to the plan’s maximum (7 on Free, 30 on Standard, 90 on Enterprise). See [Logs](https://clitrail.com/docs/logs#retention). |
| Receipts in the browser | Stop matching after 30 days; the small file stays until the visitor clears site data or a newer visit to the page replaces it. |
| Dashboard sessions | After 7 days |

Deletion happens in the service's maintenance pass, which applies retention at most once an hour. Deduplication of each event type per installation lasts as long as the event is kept: once retention deletes it, a repeat report from the same installation counts as new.

## Export

**Download CSV** in **Settings** exports up to the 100,000 most recent install events, one row each, with the columns `received_at`, `event_type`, `resolution`, `method`, `confidence`, `channel`, `campaign`, `page_url`, `referrer`, `touches`, `destinations` (each destination with its delivery status), `install_path` and `unattributed_reason`. It is part of the paid plans (`plan_required` on Free); members and above can export. Logs have their own [export](https://clitrail.com/docs/logs#the-logs-tab). Cells that a spreadsheet could read as a formula are prefixed with `'`. Exports are recorded in the audit log.

## Delete a website

**Settings → Delete this website**, for admins and owners, asks for the website's name and then for a new sign-in (Google, or a new email link). It permanently removes the website's visits, handoff tokens, install events, journeys, deliveries, destinations with their credentials, and its audit log. The organisation’s activity keeps one line noting the deletion.

## Delete your account

**Account and security → Delete account** asks for a new sign-in (Google, or a new email link). Organisations only you belong to are deleted with their websites as above; you leave the others. Then your sessions, support requests and the account itself are deleted. See [Delete your account](https://clitrail.com/docs/account-security#delete-your-account).

> Note
> 
> Deletion cannot recall installs already delivered: data sent to GA4, an ad platform or your webhook stays there under that service's own retention.