GDPR erasure workflow
VeriProof provides an authorized workflow for data-subject erasure requests. Your privacy and legal teams determine whether the complete process satisfies a specific request.
The workflow removes the subject-specific salt used to verify linked commitments. Review any remaining records under your legal and privacy requirements.
Before you request erasure
Confirm:
- the subject reference matches the request;
- your role permits the action;
- the reason and external reference are recorded;
- retention duties and active legal holds have been reviewed; and
- linked records are within the intended application scope.
Sessions without a data-subject link cannot use subject-scoped cryptographic erasure.
What the workflow changes
For linked sessions, VeriProof derives commitments with a subject-specific salt. The erasure operation removes that salt and marks the subject as erased.
Afterward, VeriProof cannot derive the subject-specific key needed to verify those commitments. Other subjects use separate salts and remain unaffected.
The operation does not remove a proof that a configured provider has already recorded. Review the remaining database, export, backup, and provider records under the approved deletion procedure.
Request and waiting period
Open the data subject
Open Compliance, then the privacy and data-subject area. Find the subject by its readable reference.
Review holds and scope
Confirm the subject, application, status, and any legal hold. An active legal hold blocks a new erasure request.
Request erasure
Enter the reason and applicable reference. VeriProof records the requesting user and request time.
Monitor the request
The current workflow uses a 30-day waiting period. Check the status view for remaining days and eligibility for execution.
This product waiting period does not determine the legal deadline for responding to the request.
Verify the outcome
After execution, confirm that the subject is marked erased and linked subject-scoped commitments no longer verify.
Cancel a pending request
An authorized user can cancel the request before execution. The workflow records the cancellation and restores the subject to the active state.
Record why the request was cancelled and retain any external case reference with the privacy record.
Legal holds
An active legal hold prevents an erasure request or execution, according to the current workflow state. Review the hold reason and date before taking action.
When a hold expires, recheck the request, applicable duties, and authorization. Do not assume that expiration alone authorizes erasure.
Validate the workflow
Use a non-production subject and record to test:
- permitted and denied role behavior;
- request and cancellation audit records;
- waiting-period status;
- legal-hold enforcement;
- final subject status; and
- commitment verification before and after execution.