Deleting your data

Deleting a site

Deleting a site deletes every event ever recorded for it, along with its visitor rollups, its share links and its settings.

1. Site settings → Delete site.

2. Confirm by typing the site's domain.

This cannot be undone and there is no recovery window. The rows are removed, not flagged as deleted. If you want the data, export it first — see Exporting your data.

Deleting a site frees the slot against your tier's site limit immediately.

Deleting your account

Deleting your account deletes your organisation, every site in it, every event in those sites, your team memberships and your API keys.

Cancel your subscription first, or the deletion cancels it as part of the same action. See Cancelling.

Invoices are retained for as long as tax law requires, separately from your analytics data. That retention is not something we can waive.

Deleting some of your data

Deleting a range of events is not available. Deletion is per site or per account.

If a site accumulated events you did not want — a staging deployment tracking into production, a bot flood — the options today are to delete the whole site, or to leave the rows and use filters and exclusions to keep them out of your view. Neither is satisfying and it is on the list.

Automatic deletion

You do not have to do anything for old data. Events are deleted when they pass your tier's retention window:

Pruning runs continuously in the background. See Data retention.

If you downgrade, the shorter window applies from that point, and events older than the new window are removed. Export first if you need them.

A visitor asking you to delete their data

Structurally, there is nothing to find — and that is in the visitor's favour.

There is no name, no email and no lookup table. The identifier is a hash:

• On the cookieless modes, the secret needed to reproduce it is deleted within 24 hours. The next day, no query can find that person's rows even in principle.

• On the cookie mode, matching would need the visitor's own ts_vid cookie value, which only they have. There is no way to get from an email address to it.

What the visitor can do themselves:

• Clear cookies for your site. On the default mode this severs the link entirely — future visits are a new visitor and the old rows are unreachable.

• Set the ignore flag on your origin, from their browser console: localStorage.truestat_ignore = "true". Nothing is sent from that browser from then on.

• Use an ad blocker, which stops the script loading.

What you can do: switch that site to a cookieless mode, or stop running the script. Neither retroactively deletes anything, and neither needs to — see GDPR for the fuller position.

If we delete your data

We do not delete a paying customer's data outside the retention schedule.

If your subscription lapses, your data is retained through the grace period described in Cancelling before anything is removed — you get a window to export or to resubscribe, not a surprise.