A bank statement is a running record of one person's money. UK GDPR Art. 5(1)(c) allows a copy to carry only what its purpose needs. Art. 5(1)(e) stops it being kept longer than that purpose lasts. Above both sits the banker's duty of confidence from Tournier v National Provincial and Union Bank of England [1924] 1 KB 461. That duty binds a bank outside data protection law, and yields in only four defined situations. DPA 2018 s.3(2) then decides whether a cleaned copy is personal data at all. anonym.plus applies each test on your own machine, so the figures stay readable while the protected fields drop out.
When this applies
An external auditor in Manchester needs twelve months of activity to test a control. The auditor has no use for the holder's name, sort code or account number. Tournier gives no general licence to hand those over, so you strip them before the file leaves the team.
How anonym.plus handles it
- Open the file in anonym.plus on your workstation.
- Local OCR reads any scanned or imaged pages.
- It flags names, account details, and balances.
- Confirm each flag and keep the dates you must show.
- Apply Mask to leave only the last four digits.
- Save the clean copy. It never leaves your machine.
What you need to provide
- The monthly record (PDF, scan, or CSV).
- An operator: Replace, Redact, or Mask.
- Optional batch for many statements at once.
PII & financial identifiers detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Financial | UK_SORT_CODE | 12-34-56 → [SORT_CODE] |
| Financial | UK_BANK_NUMBER | 12-34-56 12345678 → ****5678 |
| Names | PERSON | Carla Davies → [HOLDER] |
| Identifiers | UK_NINO | QQ 12 34 56 C → [NINO] |
| Money | MONEY | balance £14,209.55 → [AMOUNT] |
| Dates | DATE_TIME | statement 04/2026 → [DATE] |
Compliance achieved
- Holds a shared copy to what the purpose needs, as UK GDPR Art. 5(1)(c) requires.
- Supports the storage-limitation duty in UK GDPR Art. 5(1)(e), so nothing outlives its reason.
- Respects the banker's duty of confidence in Tournier v National Provincial and Union Bank of England [1924] 1 KB 461.
- Tests the cleaned copy against the identifiability threshold in DPA 2018 s.3(2).
- Leaves the statement content itself, which FCA BCOBS 4 governs, readable.
- Working copies are kept safe with AES-256-GCM; 340+ PII types are covered.
Anonymise bank statements offline — see plans & start free →
Limitations & cautions
Masking an account number to its last four digits can still help re-identify a holder when a name sits beside it. A six-year retention habit follows the contract period in the Limitation Act 1980 s.5, not a privacy rule — decide per use whether full removal is safer than a partial mask.
Frequently asked questions
Which fields does the tool target on a statement?
The holder name, sort code, account number, running balance and contact lines. Those are the values UK GDPR Art. 5(1)(c) asks you to leave out of a copy that does not need them. Dates and transaction descriptions can stay, so the record still reads like a record.
Does redaction satisfy the banker's duty of confidence?
It answers the duty in practice rather than replacing it. Tournier permits disclosure only where the law compels it, a public duty applies, the bank's own interests require it, or the customer consents. A copy that no longer names a customer or an account is not disclosing their affairs in the first place.
Does the record get uploaded for processing?
No. The app is a 100% offline desktop tool. Nothing leaves your device, so no second copy appears on a server for UK GDPR Art. 5(1)(e) to worry about.