When somebody asks you to erase what you hold about them, erase it here.
What can be erased
Erasure applies to a person you identified yourself — the user id you sent with identify, described in Custom events.
An anonymous visitor cannot be picked out after the day they visited: under the stateless path they were counted by a keyed hash under a salt that has since been replaced, and there is nothing left to match on. That is not a limitation of this screen; it is the point of counting that way.
Request an erasure
- Open the project's Settings page and its Data & privacy tab.
- Choose Erase a person, and give the person key exactly as you sent it — 1 to 256 characters. DataVisitors never asks for, and never stores, an email address for this.
- Confirm. The request is queued immediately, and the tab lists it with its status.
A person's own profile on the People page reaches the same request.
Only somebody who can manage projects in the workspace may ask. An erasure already queued or running for the same person is refused rather than duplicated.
Deletion is never plan-gated, and it does not depend on whether the project's individual-level views are switched on. The right to be forgotten is not a feature of a plan.
What happens next
The analytics service's worker answers the request: it deletes the person's events, the rollup rows built from them, and their traits. It then writes the tombstone and blanks the key on its way out, so a finished row is a receipt rather than a copy of what you asked to remove.
| On the finished row | What it is |
|---|---|
| Status | pending, running, then done. |
| Requested by | The team member who asked, and when. |
| Person | A 16-character hash of the key — enough to match a later question to this receipt, never enough to recover the identifier. |
This application keeps the same hash in its own audit trail and activity log, and never the key.
pending
running
done
Erasure cannot be undone
Every event carrying that identifier is removed, in every range, and the charts are recalculated without them. There is no restore. Read the key back to yourself before you confirm it.
What this screen cannot do
A project cannot be deleted or paused from its settings, so neither control is drawn there. Erasure is per person, by key. If a whole project's data has to go, ask support — and until then, note that retention already removes events on the plan's schedule, described in Data and hosting.