Oliver, in short
UK GDPR requires security appropriate to the risk, and copies of passports and bank statements are high-risk data. Keep them in one access-controlled system (not inboxes or desktops), encrypt and back them up, limit access to people who need it, store suspicion reports separately, and delete them when the five-year retention period ends.
The legal standard. UK GDPR Article 32 requires "a level of security appropriate to the risk". Identity documents, dates of birth, addresses and bank statements are exactly what fraudsters need for identity theft, so the risk is high even in a two-person firm. Regulation 41 adds that AML data may only be used to prevent money laundering, terrorist financing or proliferation financing, which also means limiting who can see it.
Practical controls
- One home for CDD records. A case-management system, secure document store or your AML provider's platform, not email inboxes, desktops, USB sticks or personal phones. Move documents clients email to you into the system, then delete the email copies.
- Access control. Individual logins, multi-factor authentication, and access only for staff who need it. Remove leavers' access on their last day.
- Encryption and backups. Use encrypted storage and devices, and backups you have tested restoring (Article 32(1)(c)).
- Secure collection. Ask clients to upload through a secure link or portal rather than sending passports by ordinary email or messaging apps.
- Paper. If you hold paper copies, keep them in a locked cabinet, never on open desks, and shred them securely.
- Suspicion records apart. CCAB says records of internal and external suspicious activity reports should be "stored separately and securely" to avoid tipping off.
- Suppliers. Have a written data processing contract with any provider that stores records for you, and know where the data is held. HMRC says records held outside the UK must still be "readily available" when it asks.
- Deletion. Diary the end of each retention period (five years after the relationship ends) and delete, unless regulation 40(5) allows longer.
- Incidents. Have a plan for loss or theft. A personal data breach must be reported to the data protection regulator without undue delay and, where feasible, within 72 hours, unless it is unlikely to result in a risk to people (Article 33). Since 30 September 2026 that regulator is the Information Commission, which replaced the Information Commissioner and still operates as the ICO.
Test it. Check access lists and backups at your annual AML review, and include data security in staff training: regulation 24 requires training to cover the data protection rules relevant to AML.
This is general information, not legal advice. The ICO's published security guidance gives more detail.
Sources
- UK GDPR, Article 32(1) (security of processing)
- CCAB AMLGAS (law as at 1 July 2026), paragraphs 7.2.1 and 7.5.1, 7.2.1, 7.5.1
- MLR 2017, regulation 41(1) (use of AML data)
- HMRC AMLG11700, section 17 (records held outside the UK), Records held outside of the UK
- UK GDPR, Article 33(1) (notifying a personal data breach)
- Data (Use and Access) Act 2025, sections 118(1) and 119(1)-(2) (Information Commission; in force 30 September 2026, SI 2026/1015), 118(1), 119(1)-(2)
Still have a question?
Ask Oliver in your own words, or send it to the AML Buddy team and we’ll use it to add a checked answer.
Ask Oliver Email the team