Financial-account redaction is the removal of full account numbers from a court filing and its exhibits. UK GDPR Art. 32(1)(a) names pseudonymisation and encryption as appropriate technical measures, and card schemes expect a card number to be masked when it is displayed. anonym.plus finds each value on your device and masks it.
When this applies
Bank statements and transfer records list full numbers across dozens of exhibit pages. Many of those pages came from the other side's disclosure, where CPR 31.22(1) limits use of the document to these proceedings. A schedule of losses still needs the figures, so mask the numbers and keep the sums.
How anonym.plus handles it
- Open the statements in anonym.plus on your device.
- Local OCR reads scanned bank and card pages.
- The tool flags bank, sort-code, and card numbers.
- Apply Mask to hide the bulk of each value.
- Confirm no full value remains in any exhibit.
- Save the clean papers locally.
What you need to provide
- The statements and exhibits (PDF, scan, DOCX).
- The Mask operator set to leave only a short remnant.
- Optional batch for many statement pages.
PII entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Financial | UK_BANK_NUMBER | 4412 9087 1120 → ****1120 |
| Financial | CREDIT_CARD | card 4111 ... → ****1111 |
| Financial | IBAN_CODE | GB IBAN → masked |
| Names | PERSON | account holder → [HOLDER] |
| Identifiers | UK_NINO | linked NINO → [NINO] |
| Dates | DATE_TIME | statement date → [DATE] |
Compliance achieved
- Applies the pseudonymisation measure named in UK GDPR Art. 32(1)(a) to every stored value.
- Follows the minimisation test in UK GDPR Art. 5(1)(c): keep the sum in issue, not the account it sat in.
- Masks the primary account number in line with PCI DSS v4.0, which limits how much of a card number may be displayed.
- Holds the collateral-use limit in CPR 31.22(1) for statements that came from the other side's disclosure.
- Keeps a schedule of past and future losses usable, which CPR PD 16 expects in a personal injury claim.
- Reduces exposure to the unlawful-disclosure offence in DPA 2018 s.170.
Anonymise financial filings offline — see plans & start free →
Limitations & cautions
A spaced or hyphenated number on a faint scan can confuse OCR. Verify the flags on image pages so no full number remains. The tool masks what it detects; check the output before the exhibit goes out.
Frequently asked questions
How much of an account number should remain?
As little as the case needs. UK GDPR Art. 5(1)(c) limits data to what is necessary, and PCI DSS v4.0 restricts how much of a card number may be shown. anonym.plus masks the bulk of each value in one pass across the filing.
Can I keep the amounts in a schedule of loss?
Yes. CPR PD 16 expects a schedule of past and future expenses and losses in a personal injury claim, and the figures are the point of it. Allow-list the sums and mask the numbers behind them.
Does it catch credit-card and IBAN numbers?
Yes. Card numbers, sort codes, and IBANs are flagged along with bank account values, and local OCR reads them off a scanned page.