Data deletion and erasure
Review exactly what will be removed before approving deletion. Required approvals and retained evidence depend on the request, deployment, legal holds, and approved account terms.
Deletion can be irreversible. Confirm the organization, application, data categories, legal basis, and required reviewers before approving a purge.
Review a deletion request
Confirm the scope
Identify the organization, application, person, date range, and data categories covered by the request. Do not approve a broad deletion when a narrower request meets the requirement.
Check retention obligations
Review active legal holds, audit engagements, regulatory requirements, and approved retention terms. Resolve any conflict before authorizing deletion.
Complete the required reviews
Use the approval flow shown in VeriProof. A reviewer must confirm the impact presented by the portal and must not approve their own request when separation of duties is required.
Verify completion
Check the final status. Approval alone does not confirm deletion. Keep the request ID, scope, approvals, timestamps, and completion evidence in the appropriate audit record.
Check timing and retained evidence
Check the timing and any recovery window shown for the request and in the applicable account terms. Do not assume a grace period. Blockchain commitments may remain independently verifiable without containing the deleted session content.
For organization closure, see Retirement and offboarding. Retirement does not mean evidence deletion. For an erasure request, follow Data erasure and have your privacy owner confirm the required scope.