Signature Page Redaction with anonym.plus

Clear signatory and attesting-party IDs from an execution block before sharing.

Signature-page redaction is the removal of signatory and witness PII from an execution block under UK GDPR Recital 26. anonym.plus runs offline. It strips the personal identifiers, titles, and attesting-party details but keeps the block structure.

When this applies

These blocks carry signatures, printed names, titles, and attestation details. To share an agreement without exposing who signed, you clear that section first.

How anonym.plus handles it

  1. Load the file into anonym.plus on your device.
  2. Local OCR reads scanned signatures and attestations.
  3. The tool flags printed names, titles, and attestation lines.
  4. Confirm the flags and keep the block layout.
  5. Black out the signatures and swap the printed IDs.
  6. Save the clean copy on your machine.

What you need to provide

PII entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONprinted name → [SIGNATORY]
TitleORGANIZATIONtitle/role → [TITLE]
NamesPERSONwitness → [WITNESS]
NamesPERSONsecond witness → [WITNESS_2]
DatesDATE_TIMEexecution date → [DATE]
LocationLOCATIONwitness address → [ADDRESS]

Compliance achieved

Anonymise signature pages offline — see plans & start free →

Limitations & cautions

Hand-signed scans lean on OCR, and a stylised signature can resist it. Review the block the tool found before you export. A unique title at a small firm can still hint at the signer after the name goes.

Frequently asked questions

Can a hand-signed scan be cleaned?

Yes. Local OCR reads the printed names and attestations. Signatures themselves are blacked out with the Redact operator.

Are attesting-party details removed?

Yes. The signatory details and addresses are PII and are flagged together.

Does the block layout survive?

Yes. The structure stays. Only the identifying marks and names change.