Erasure requests and attestations

Erasure is different from access: instead of collecting data, each system owner has to delete it and confirm they've done so. Blankitt Privacy records that confirmation as an erasure attestation, your evidence that deletion actually happened.

The flow

1. An erasure (or US "delete") request is verified and its tasks are created, one per data source, exactly like an access request.
2. Each owner deletes the person's data from their system.
3. The owner attests: a per-system confirmation of what was deleted (or that nothing was held), recorded with who attested and when.

Attaching evidence

An attestation can carry an evidence file (up to 10 MB): a screenshot of the deletion confirmation, an export of the deletion job log, whatever your system produces. Evidence can be replaced if a better artifact turns up, and each attestation shows a download chip for its file.

Evidence is internal only. It is never included in anything delivered to the requester. It exists for your compliance file and for the auditor or regulator who asks, a year from now, "prove you deleted it".

What the requester gets

When attestations are in, package and deliver as normal. The response confirms erasure rather than enclosing data. The cover letter records the systems covered.

Exemptions are normal

You'll often be required to keep some data (order records for tax law, for example). Delete what you can, record what you kept and the legal basis in a case note, and say so plainly in the response. A partial erasure honestly explained is compliant. A silent one is not.