Delete personal data

An erasure removes everything Voidhash holds that identifies a person, for example to honor a GDPR or CCPA deletion request, while their purchases and revenue stay recorded anonymously. You can request one from Studio, the API, the CLI or the MCP server. It cannot be undone.

What is deleted and what is kept

An erasure covers the person and every profile merged into them, such as the anonymous profile they used before signing in.

Kept records stay attached to an anonymous person ID, so renewals, refunds and cancellations of a subscription they still pay for keep being recorded. Afterwards the person no longer appears in Studio or the API. If your app identifies the same user ID again, Voidhash starts a new, empty person.

On a website, also call reset() in the visitor's browser so later events don't carry the erased distinct ID. See Privacy.

Request an erasure

You need permission to delete people in the project, which team admins and owners have.

curl https://api.voidhash.com/api/v1/projects/$VOIDHASH_PROJECT_ID/erasures \
  -H "Authorization: Bearer $VOIDHASH_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "distinctId": "user_123" }'

import { createVoidhashSdk } from "@voidhash/node";

const voidhash = createVoidhashSdk({ secretKey: process.env.VOIDHASH_SECRET_KEY! });

const erasure = await voidhash.persons.createErasure({
  payload: { distinctId: "user_123" },
});

voidhash person erase user_123

Put identifiers in the body, never in the URL: a distinct ID can be an email address.

Track progress

The API answers every request with 202 Accepted and the erasure:

{
  "id": "person_erasure_...",
  "projectId": "proj_...",
  "status": "queued",
  "personId": "person_...",
  "requestedAt": "2026-10-14T10:00:00.000Z",
  "completedAt": null
}

Most erasures finish within minutes. Poll GET /api/v1/projects/{projectId}/erasures/{erasureId} or subscribe to the person.deleted webhook, which fires when the erasure completes.

• Repeats are safe. Requesting the same person again returns the same erasure, and restarts it if it failed.
• Unknown people. A request that matches nobody returns an erasure that is completed at once, with personId set to null. Every request is recorded in the audit log either way.
• Late events. A day after completion, Voidhash erases once more to remove events the person's devices captured before the erasure but delivered later, for example from an offline queue. Events your app sends after the erasure belong to the new person and are kept.

Keep your own systems in sync

Voidhash only erases the data it holds. If your backend stores the same person, subscribe a webhook endpoint to person.deleted and delete your copy when it arrives. The event carries personId, erasureId and erasedAt, but no distinct ID, email or name, so store the Voidhash person ID next to your own record.

Next steps

• People and identity
• Webhook events
• Go-live checklist