Deleting a person, deleting a workspace, and retention
Updated
Delete one person
Use this when someone asks you to erase their data.
- Open Privacy review and scroll to 5. Delete a person.
- Under Find by, choose Email, Phone or Patient / contact id.
- Enter the value and click Delete person.
Only owners and admins can do this. Kalman hashes the value the same way it does when data comes in, uses the hash to find the person, and never stores the value.
This removes:
- the person's visitor records, visits (sessions) and events
- the raw data those events came from (for a webhook that carried several events at once, the whole raw copy)
- anything not yet sent to an ad platform
- their rows in web analytics
Deliveries that were already sent stay in the log as a record, but their contents are removed. The page shows what was deleted, with counts only. If no one matches, it says so.
Kalman can't recall data that has already been sent to Meta or another ad platform. To have it removed there, request deletion from that platform directly.
Delete a workspace
- Go to Settings → Workspaces and open the workspace.
- Under Delete workspace, click Delete workspace.
- Type the workspace name to confirm, then click Delete workspace.
Only the workspace owner can do this. A main workspace that still has additional workspaces can't be deleted: delete those first.
As soon as you delete the workspace:
- its sources and ad destinations are switched off
- the stored ad platform access token is removed
- anything waiting to be sent is cancelled
- the tag and webhooks stop accepting data for it
After a 30-day grace period, Kalman removes every row of the workspace's data, table by table, including web analytics.
Retention
| What | How long Kalman keeps it | Can it change? |
|---|---|---|
| Raw copies of incoming webhooks, including caught samples | 30 days | Set by Kalman for every workspace |
| Visitors' IP addresses | 30 days, then cleared from the visitor record | Set by Kalman for every workspace |
| The body of each delivery sent to an ad platform | 90 days; the delivery's status and time stay with the event | No |
| Events, sessions, deliveries and visitors (with hashed emails and phones and the browser user agent) | Until deleted, unless your workspace has a retention window | Yes: a per-workspace retention window, set by Kalman on request |
| Web analytics rows | 25 months | No |
| A deleted workspace's data | 30 days after deletion | No |
| A canceled workspace's data | Kept, unless an account-wide window is set | Set by Kalman |
| Free preview workspaces | 14 days | No |
| Website scans | 30 days (public reports), 180 days (workspace scans), 90 days (agency bulk scans) | No |
"PHI deleted after 30 days" is true only of the raw webhook copies and IP addresses. Events and the hashed identifiers on them stay until deleted, as above.
The bottom of 5. Delete a person shows whether a retention window applies to your workspace. When one does, older events, sessions and visitors are deleted daily.
What Kalman never stores
Emails and phone numbers are hashed when data comes in, so Kalman stores only the hashes, not the raw values. Nothing you type into the delete form is kept.
Related articles
- Privacy controls: paths, query parameters and sensitive termsMask sensitive pages, decide which query parameters the tag keeps, apply a platform preset, and get a weekly summary of what Kalman held back.
- Consent and Global Privacy ControlChoose opt-in or opt-out, honour Global Privacy Control, and pick where consent comes from: your CMP, your own banner, or the Kalman banner.
- The Event log, deliveries and the data-flow recordSee every event Kalman received, exactly what it sent to Meta and why anything was held back, and download a data-flow record.
- Team members, roles and sign-in securityInvite teammates, understand owner, admin and member roles, and protect your login with two-factor authentication or a passkey.
Support
Still stuck? Log in and open a request.
We answer in writing within one business day.
Open a request