Key takeaways
- The regulator is now the Information Commission, which replaced the Information Commissioner's Office on 30 September 2026.
- Since June 2026, every controller must make data protection complaints easy to submit, acknowledge them within 30 days and tell the complainant the outcome.
- Most complaints about practices concern late subject access requests, disclosures to the wrong person and inaccurate records.
- A prompt, factual response that shows what you have put right usually ends the matter.
Who the regulator is now
Patients and staff still talk about complaining to the ICO, and the phrase will stay in use for years. Formally, the section of the Data Protection Act 2018 establishing the office of Information Commissioner was omitted with effect from 30 September 2026 by the Data (Use and Access) Act 2025[1], and its functions now sit with the Information Commission. For a practice, little changes in practice: the same law applies, complaints still arrive, and the regulator still expects you to have handled the matter properly first.
What has changed is that practices now have a statutory complaints duty of their own. That makes the first stage, how you handle a complaint before it reaches the regulator, more important than ever.
Your own complaints duty
Section 164A of the Data Protection Act 2018, fully in force from 19 June 2026, requires controllers to facilitate the making of data protection complaints, for example by providing a form that can be completed electronically and by other means; to acknowledge receipt within 30 days; to take appropriate steps to respond without undue delay, including investigating and keeping the complainant informed; and to tell the complainant the outcome[2].
Make it easy to complain
Add a data protection complaints route to your website, privacy notice and practice leaflet: an online form, an email address and a postal address. Reception should know how to log a complaint made in person or by phone.
Log and acknowledge
Record every complaint the day it arrives and acknowledge it well within the 30-day limit, ideally within a few working days, saying who is handling it.
Investigate
Collect the facts: the request or disclosure involved, the dates, the people involved and the relevant records or audit logs. Involve your DPO.
Keep the complainant informed
If the investigation will take time, tell them, and give a realistic date.
Tell them the outcome
Explain what you found, what you have done to put it right and what you have changed, and remind them of their right to complain to the regulator.
Data protection complaints can overlap with NHS or clinical complaints. Use one investigation where the facts are the same, but make sure the data protection questions are answered explicitly.
What patients complain about
| Complaint | Typical cause | What resolves it |
|---|---|---|
| Subject access request late or incomplete | Request lost in a shared inbox; deadline missed; records partly sent | Send the complete response now, apologise, fix the request log |
| Information given to the wrong person | Weak identity checks; wrong address or number | Explain what happened, the risk assessment and the changes made |
| Inaccurate record | Wrong entry, wrong patient, disputed opinion | Correct factual errors; add the patient's statement where opinions are disputed |
| Marketing texts or emails without consent | Service and marketing templates mixed | Stop messages, suppress the number, review templates |
| CCTV or call recording concerns | No signage, audio on, retention too long | Review the system against your impact assessment |
| Confidentiality breach by staff | Inappropriate access to a record | Audit, HR process, explanation to the patient |
Late subject access requests are the most avoidable. The deadline is one month from the relevant time, extendable by two months only for complex or numerous requests[3]. A simple request log with due dates, checked weekly, prevents most of these complaints.
Disputed records
Complaints about inaccurate records need care, because a clinical record contains both facts and professional opinions. A wrong date of birth, a result filed in the wrong patient's notes or an allergy recorded in error are factual mistakes and should be corrected promptly, with an audit trail showing what changed and why. A clinician's opinion, such as a working diagnosis the patient disagrees with, is different: it was the clinician's view at the time and is usually kept, with the patient's own statement added alongside it.
Explain the distinction to the patient in plain terms, show them what you have changed or added, and tell them how to take it further if they remain unhappy. A thoughtful reply here prevents many complaints from escalating.
Getting ready before a complaint arrives
- Publish a data protection complaints route in the privacy notice and on the website.
- Keep one log for complaints, subject access requests and breaches, with dates and owners.
- Agree with your DPO how quickly they will review a complaint and a letter from the regulator.
- Keep evidence folders current: policies, training records, impact assessments, supplier contracts.
- Brief reception on how to recognise and log a data protection complaint made in person or by phone.
When the regulator writes to you
If a complaint reaches the regulator, you will usually receive a letter or email setting out the concern and asking for your response by a stated date. Treat it as a priority, tell your DPO the same day, and diarise the deadline. If you need more time, ask before it passes.
- Expect to be asked what happened, in date order, with evidence.
- Expect to be asked how you responded to the complainant, and whether the matter is resolved.
- Expect to be asked for the relevant policy or procedure, and whether it was followed.
- Expect to be asked what you have done to stop it happening again.
- Answer the questions asked, briefly and factually, and attach evidence rather than describing it.
Writing the response
- A short summary: who you are, the complaint reference and your conclusion in two sentences.
- A timeline of events with dates, drawn from logs and records.
- Your assessment: where you met your obligations, and where you did not.
- What you have done for the complainant, such as providing the records, correcting the entry or apologising.
- What you have changed: process, training, system settings, with evidence.
- A named contact for follow-up questions.
Be candid about failures. A practice that says ‘we missed the deadline because the request was filed in the wrong inbox; we have since moved all requests into a tracked log and trained staff’ is in a far better position than one that argues the request was unclear.
Possible outcomes
Most complaints about small organisations end with advice or a finding that the organisation should take particular steps. Formal action is reserved for more serious or repeated failures, and serious infringements of UK GDPR can attract fines of up to £17.5 million or 4% of worldwide annual turnover[4]. Health data is special category data[5], so the regulator expects higher standards from practices than from many other small organisations.
The reputational cost often matters more than any penalty. Public trust in the NHS's use of data is good but has been slipping: the share of UK adults trusting the NHS to use data to improve services fell from 78% to 73% between waves of the government's tracker[6].
Source: GOV.UK (Department for Science, Innovation and Technology), 2024[6]
Show the data
| Item | Value |
|---|---|
| Wave 3 | 78% |
| Wave 4 | 73% |
Example: a late request becomes a complaint
Example: a patient of Hillcrest Dental, a fictional practice, asks for his records in an email to the general inbox. Nobody logs it. Seven weeks later he complains to the practice, and the next day to the regulator. The manager acknowledges the complaint immediately, finds the original email, and sends the full records within a week with an apology.
Example: when the regulator's letter arrives, the manager replies with a timeline, a copy of the response to the patient, the new request log and evidence that staff were briefed. The regulator closes the case with advice to keep the log in place. The patient later writes to say he is satisfied.
Learning from complaints
Every data protection complaint shows you where a process failed. Record the cause, the fix and who owns it, review complaints at the quarterly governance meeting, and share the lessons with staff. Patterns across several complaints, such as repeated identity check failures at the same desk, are more valuable than any single case. When a fix works, say so at a team meeting; people are more willing to change routines when they can see the result.
Related reading: sharing records for direct care, clear desk and screen rules, data protection training, the IG lead's role and the wider GP complaints procedure.
Frequently asked questions
Is it still called the ICO?
Informally, yes. Formally, the Information Commission took over from the office of the Information Commissioner on 30 September 2026[1].
Do we have to acknowledge a data protection complaint?
Yes. Since June 2026, controllers must acknowledge receipt within 30 days, respond without undue delay and tell the complainant the outcome[2].
Can a patient complain to the regulator without complaining to us first?
They can, but the regulator generally expects organisations to have had the chance to resolve it. A clear, accessible complaints route makes that more likely.
Will we be fined?
Fines are for serious infringements. Most complaints about practices end with advice or required steps, especially when the practice has put things right[4].
References
legislation.gov.uk (The National Archives) (2026). Data Protection Act 2018, section 114 (omitted) (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). Data Protection Act 2018, section 164A: Complaints by data subjects (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 12A: Time limits for responding to requests (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 83: General conditions for imposing administrative fines (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 9: Processing of special categories of personal data (opens in a new tab) ↑
GOV.UK (Department for Science, Innovation and Technology) (2024). Public attitudes to data and AI: Tracker survey (Wave 4) report (opens in a new tab) ↑