Escrow-document redaction is the removal of PII from holding agreements and wire instructions. It supports anonymous sharing under GDPR Recital 26. anonym.plus runs locally and keeps the release terms that the parties agree.
When this applies
These papers name the parties, the agent, and the bank with wire details. A reviewer needs the release terms, not the people or the banking data.
How anonym.plus handles it
- Load the papers into anonym.plus on your device.
- It flags party names, agents, and bank numbers.
- Release terms, amounts, and triggers stay in place.
- Swap or black out the confirmed PII.
- Save the clean document on your device.
What you need to provide
- The papers (DOCX, PDF, or scan).
- An operator; Replace keeps the clauses readable.
- Optional role map for party and agent labels.
PII entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | the signatory → [PARTY] |
| Org | ORGANIZATION | holding agent → [AGENT] |
| Finance | IBAN_CODE | holding account → [ACCOUNT] |
| Identifiers | NATIONAL_ID | tax ref → [ID] |
| Contact | EMAIL_ADDRESS | agent email → [EMAIL] |
| Dates | DATE_TIME | release 31 Dec → [DATE] |
Compliance achieved
- Supports anonymous sharing under GDPR Recital 26.
- Keeps release terms and amounts whole for review.
- Runs offline with AES-256-GCM at rest — no cloud relay.
Anonymize escrow documents offline — see plans & start free →
Limitations & cautions
Bank numbers can appear in headers and wire blocks. Check those blocks with care. A unique release trigger may hint at one party even after the name goes, so review rare triggers by hand.
Frequently asked questions
Do the release conditions stay?
Yes. The amounts, triggers, and timelines stay. Only personal and banking data changes.
Are bank numbers cleared?
Yes. Bank and escrow numbers are flagged and swapped along with the names.
Can I process a scanned agreement?
Yes. Local OCR reads scanned pages, so IDs in image files are caught.