Deletion confirmation redaction is the removal of personal identifiers from the proof that an erasure ran. UK GDPR Art. 17(1) gives a person the right to have their data deleted, Art. 19 requires you to tell each recipient it happened, and Art. 5(2) requires you to be able to demonstrate all of it. anonym.plus marks the subject and references on your device, so the record of action survives while the named individual is hidden.
When this applies
The paradox is obvious once you see it: a confirmation that names the person, lists their request ID, and cites the systems purged is itself a fresh copy of the data you just erased. Art. 12(3) gave you one month to act, so the timestamp matters and the name does not. Where a record legitimately stayed — a PAYE file, right-to-work evidence — Art. 17(3)(b) is the reason, and that reason belongs in the log too.
How anonym.plus handles it
- Open the confirmation in anonym.plus on your device.
- The tool flags the subject, request ID, and contacts.
- Local OCR reads a scanned acknowledgement.
- Keep the action timestamps and system names.
- Swap or black out the confirmed items.
- Save the clean record locally.
What you need to provide
- The erasure confirmation (PDF, DOCX, TXT, scan).
- An operator (Replace keeps the log readable).
- Optional allow-list for system names you must keep.
PII entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | data subject → [SUBJECT] |
| Identifiers | NATIONAL_ID | request DSR-4412 → [REQUEST_ID] |
| Contact | EMAIL_ADDRESS | subject@example.co.uk → [EMAIL] |
| Dates | DATE_TIME | erased 01/06 → [DATE] |
| Organisation | ORGANIZATION | system name → [SYSTEM] |
| Location | LOCATION | subject city → [CITY] |
Compliance achieved
- Documents the action UK GDPR Article 17(1) required without re-storing the data it erased.
- Records the notification to each recipient that Article 19 adds to the erasure itself.
- Keeps the timestamps that show the one-month deadline in Article 12(3) was met.
- Leaves room to state where Article 17(3)(b) let a record stay because a legal obligation required it.
- Serves the accountability duty in Article 5(2) — evidence you can show a regulator, holding nothing you should not.
Anonymise deletion confirmations offline — see plans & start free →
Limitations & cautions
A proof of erasure should show that work was done, not re-store the very data just deleted. The tool flags named items. Confirm no kept reference — a request ID, a ticket number — rebuilds the link to the subject through another system.
Frequently asked questions
Why redact a confirmation of deletion?
Keeping the subject's identifiers in it re-stores the data Art. 17 told you to erase. Redaction lets you keep the audit trail safely.
What should the record still show?
The timestamps and system names that prove the erasure ran, the Art. 19 notifications sent, and any Art. 17(3)(b) reason a record stayed. Allow-list those.
Is the log uploaded?
No. The app is fully offline, so the file stays on your device.