Preview and execute privacy erasure

Before you begin

Use an ERASURE request for a USER with verified identity in PROCESSING. Require erasure capability and an approved change/case record. Erasure is destructive; take and validate required backups while respecting the erasure policy for restored data. STATUS_SUBSCRIBER erasure is not automated in 2.0 and must follow the approved manual subscriber-data process.

Open the feature

Open Settings → Privacy Requests, select the erasure request, and open Erasure.

Configure the decision

Select Preview erasure.
Review every affected category, retained audit record, ownership dependency, and blocker.
Resolve or document holds and ownership transfers. Never bypass a blocker by editing the database.
Re-run preview until the current request is executable.
Confirm subject and request ID again, then execute once.

What OpsKnight does

Execution rechecks verification and PROCESSING state inside the operation, claims the request against concurrent execution, applies the policy, records results, and retains the Privacy Request row as fulfilment evidence. A blocker moves the operation/request into auditable failed or blocked state rather than silently deleting partial data.

Verify the erasure

Confirm execution is completed, the request reaches COMPLETED, prohibited subject data is no longer returned, and retained/audit records match the preview. Review audit logs for the actor and request.

Roll back or recover

There is no UI undo. If execution fails, stop, preserve evidence, inspect the recorded phase, and resolve the blocker before a controlled retry. Do not restore erased personal data from backup into production without applying the erasure obligation to the restored dataset.

Troubleshooting

Preview is blocked: inspect legal hold, ownership, and dependency details.
Execute is unavailable: verify permission, identity, request type, and PROCESSING state.
Concurrent/stale state: reload the detail; another operator may have transitioned or claimed it.
Subscriber erasure has no preview/execute action: this is expected. Do not substitute a user ID or edit the database; complete and evidence the manual subscriber erasure workflow.

Next steps

Retention, holds, and troubleshooting