Since 19 June 2026, every controller has been under a statutory duty, in section 164A of the Data Protection Act 2018, to provide a way for individuals to complain about the handling of their personal data, to acknowledge complaints within 30 days, and to take appropriate steps to respond without undue delay, including making enquiries and keeping the complainant informed. The duty was inserted by the Data (Use and Access) Act 2025, and it applies to all controllers, whatever their size.
What does the duty actually require?
- A means of complaining – the organisation must facilitate complaints, for example by providing an electronic form, without excluding other ways of making them
- Acknowledgement within 30 days – of receiving the complaint
- Appropriate steps without undue delay – including making enquiries into the subject matter of the complaint to the extent appropriate
- Keeping the complainant informed – of progress and, in due course, of the outcome
The ICO’s guidance reads the 30 days as starting on the day after the complaint is received, and makes clear that the obligation to investigate without undue delay runs from receipt, not from the acknowledgement. Where it differs in emphasis from the statute, the statute governs, but the guidance is a useful indication of how the regulator will approach the question.
What counts as a complaint?
Rather more than many organisations are logging. A complaint need not use the words “data protection” or cite the legislation; an individual who objects that their information was shared without their agreement, or that a request was mishandled, is making a data protection complaint whether they label it as one or not. For governing bodies, complaints of this kind often arrive tangled up with disciplinary or safeguarding grievances, and the data protection element needs to be identified and handled under the statutory process even where the wider grievance runs through another procedure.
Where are processes falling short?
- No identifiable route – privacy notices that mention the right to complain to the ICO but not the right to complain to the organisation
- Complaints not recognised as such – sitting in general inboxes, or treated purely as service complaints
- The clock not tracked – no record of when a complaint was received, so the 30-day acknowledgement cannot be evidenced
- Investigations that stall – acknowledged on time and then left
- No link to other processes – complaints that reveal a breach not routed to the breach response plan, or complaints about a subject access response not referred back to whoever handled the request
What should a compliant process look like?
Short, owned and recorded. A named owner, often the DPO; a published route; a log that records the date of receipt, acknowledgement, enquiries made and outcome; and a short procedure that ties the complaint into the organisation’s other processes. Updating privacy notices to mention the right to complain to the organisation, alongside the existing information about complaining to the ICO required by Articles 13 and 14, is the quickest single fix, and the one most often still outstanding. Complaints about a subject access response in a disciplinary case are among the most common, and the most likely to escalate.
If you’d like a review of your complaints process against section 164A, see our Data Protection advisory services.