Dataset batch redaction is the removal of personal data from many capital-markets files in one run. FCA SYSC 9.1 and the five-year rule in UK MiFIR Art. 25 tell you what a master set must still contain; UK GDPR Art. 5(1)(e) storage limitation tells you why an archive should not keep identifiers it no longer needs. anonym.plus processes up to 20 files at a time on your machine, with a shared map so one party maps to one alias across the whole set.
When this applies
A deal archive holds rosters, blotters and statements that name the same clients in different formats. File-by-file work drifts, so a batch run applies one rule evenly and leaves an archive you can still reconcile.
How anonym.plus handles it
- Point anonym.plus at the archive folder on your machine.
- It scans each file for names, IDs, and account fields.
- Local OCR reads any scanned pages in the set.
- A shared map keeps repeat clients steady across files.
- Review the summary and fix low-confidence flags.
- Save the clean set locally.
What you need to provide
- A folder of datasets (CSV, PDF, DOCX, mixed).
- The shared label map turned on for steady results.
- An operator (Mask suits structured fields).
PII & financial identifiers detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | client across files → [CLIENT_1] |
| Identifiers | UK_NINO | tax NINOs → [NINO] |
| Financial | UK_BANK_NUMBER | accounts → [ACCOUNT] |
| Financial | IBAN_CODE | wire IBANs → [IBAN] |
| Contact | EMAIL_ADDRESS | emails → [EMAIL] |
| Money | MONEY | amounts → [AMOUNT] |
Compliance achieved
- Record duties in FCA SYSC 9.1 and the five-year rule in UK MiFIR Art. 25 define what the master archive must still hold.
- Storage limitation under UK GDPR Art. 5(1)(e) is why an archive should not keep identifiers beyond their purpose.
- Pseudonymisation is named as a security measure in UK GDPR Art. 32(1)(a) — the shared map is exactly that, so switch it off when you need true anonymity.
- Data protection by design under UK GDPR Art. 25 favours one even pass over file-by-file editing.
- 'Personal data' follows DPA 2018 s.3(2): a living individual, identifiable directly or indirectly.
Anonymise capital-markets datasets offline — see plans & start free →
Limitations & cautions
A mixed folder of scans and native files leans on OCR for the images, so review low-confidence flags. The shared map is pseudonymisation, not anonymisation — keep it and the set can be re-linked; turn it off when Recital 26 anonymity is the goal. Never clean a record SYSC 9.1 or UK MiFIR Art. 25 still requires.
Frequently asked questions
How does batch mode keep one client steady?
A shared map logs each person once, so the same client maps to the same alias in every file across the folder.
Is a shared map anonymisation?
No. It is pseudonymisation, named as a security measure in UK GDPR Art. 32(1)(a). The data stays personal data while the map exists. Turn the map off to reach the Recital 26 anonymity standard.
Does batch work upload anything?
No. The whole run is offline, so customer data stays on your machine.