Skip to content
Welcome
UK
Dragonfly ITDragonfly Insights
Compliance & Regulation

The New Legal Duty to Handle Data Protection Complaints: Is Your Process Ready?

Since 19 June 2026 every organisation that handles personal data has had to run a process for data protection complaints. This is what the duty asks for, and a simple way for a small business or school to put it in place.

5 min readDragonfly IT

Explainer. Written by Dragonfly IT. Drafted with AI help and checked against the sources listed on this page.

The Data (Use and Access) Act 2025 changed UK data protection law in stages. The Information Commissioner's Office said most of the remaining data protection changes came into force on 5 February 2026, with one more following on 19 June 2026: a duty for organisations to have a procedure for handling data protection complaints. On 23 June 2026 the ICO confirmed the duty was in force, applied to all organisations that handle personal data, and that every outstanding provision of the Act was now in force.

For a business with a few customers' details in a CRM, or a school with pupil records, this is a small piece of work rather than a big project. It does need doing, and it helps to have it in place before the first complaint arrives. This article is general information, not legal advice; the ICO's own complaints guidance is the place to check the detail.

What does the complaints duty require?

The ICO summarises the duty in four parts. An organisation must:

  • Give people a clear way to raise a data protection complaint with it directly.
  • Acknowledge each complaint within 30 days of receiving it.
  • Look into the complaint appropriately, without undue delay.
  • Tell the person the outcome, and keep them informed of progress while it is being looked into.

What counts as a data protection complaint?

Any complaint that an organisation has not handled someone's personal data in line with UK GDPR or the Data Protection Act 2018. The ICO's guidance gives practical examples built around the most common complaints: subject access requests that went unanswered or were incomplete, personal data that is wrong and has not been corrected, and unwanted marketing.

Law firm CMS notes that complaints should be accepted however they arrive, which can include social media, that someone may complain on another person's behalf once you have checked they are allowed to, and that the ICO can ask to see records of when complaints were received, acknowledged and resolved.

A simple setup for a small business or school

Most small organisations already have the pieces. The work is joining them up and writing it down:

  • Choose one route people can use, such as a named email address or a short web form, and add it to your privacy notice.
  • Decide who owns complaints and who covers when they are away.
  • Keep a simple log: date received, date acknowledged, what was looked at, the outcome and the date it was sent.
  • Prepare a short acknowledgement template, so the 30 day step never slips.
  • Brief staff who answer phones and social media messages, so a complaint made there is passed on.

What to do this week

Read the ICO's data protection complaints guidance, update your privacy notice with the complaints route, and set up the log. If you use Microsoft 365, a shared mailbox and a Microsoft Forms form can provide the route, and a SharePoint list or a simple spreadsheet with restricted access can hold the log. Keep the log itself tidy, because it will hold personal data too.

How it fits with the rest of your data protection work

A complaints process works best when the things people complain about are under control. Knowing where personal data lives, answering subject access requests on time and keeping marketing lists clean all reduce complaints in the first place. The ICO also updated its subject access request guidance when the February 2026 changes came in.

Where Dragonfly IT can help

The legal judgement on each complaint is yours, with advice where needed. Setting up the mailbox, form and log, and finding personal data across Microsoft 365, is IT work. For help with that, see Dragonfly IT's Microsoft 365 support and Microsoft 365 assessment services.

Frequently asked questions

When did the data protection complaints duty start?

The duty to have a data protection complaints procedure came into force on 19 June 2026, under the Data (Use and Access) Act 2025. The ICO confirmed on 23 June 2026 that it applies to all organisations that handle personal data and that all the outstanding provisions of the Act were then in force.

How long do I have to acknowledge a complaint?

The ICO says organisations must acknowledge a data protection complaint within 30 days of receiving it, then look into it without undue delay and tell the person the outcome. Keeping a dated log of each step makes it easy to show the timescale was met.

Does a small business really need a complaints process?

Yes. The ICO says the duty applies to all organisations that handle personal data, whatever their size. For a small business it can be simple: one named route for complaints, a person responsible, an acknowledgement template and a log. The ICO's guidance gives practical examples.

Can people still complain to the ICO?

Yes. The new duty sits alongside the right to complain to the ICO rather than replacing it. What changes is that every organisation must now offer its own route and respond to complaints properly, which gives it the chance to put things right. A clear internal process and a dated log also help if the ICO later asks what happened.

Sources

More in Compliance & Regulation

Is your business exposed to IT risks you can't see?

Our engineers audit your network, cyber security, backups and Microsoft 365 setup, then hand you a written report on where you're exposed and what we'd prioritise first.

Book My Free Risk Assessment

No cost · No commitment · 0333 0444 323