Since 19 June 2026, every controller covered by UK data protection law has had a statutory data protection complaints procedure duty. You must make it easy for people to complain to you about how you handle their personal data (for example, with a complaint form that can be completed electronically), acknowledge each complaint within 30 days, look into it, keep the complainant updated and tell them the outcome without undue delay. It applies to sole traders and small websites just as much as large companies.
This guide explains what the law requires, what the ICO expects, and a simple process a small site can set up in an afternoon. It is general information, not legal advice.
The UK data protection complaints procedure: what the law requires
The Data (Use and Access) Act 2025 inserted section 164A into the Data Protection Act 2018. In summary:
- a data subject may complain to the controller if they think there has been an infringement of the UK GDPR (or Part 3 of the DPA 2018) in connection with their personal data;
- the controller must facilitate complaints, by taking steps such as providing a complaint form that can be completed electronically and by other means;
- the controller must acknowledge receipt within 30 days of receiving the complaint;
- the controller must, without undue delay, take appropriate steps to respond (including making enquiries to the extent appropriate and keeping the complainant informed of progress) and tell the complainant the outcome.
The duty commenced on 19 June 2026 under the DUAA commencement regulations. It sits on the controller; processors do not have their own duty, but should help you, so check your contracts.
The ICO complaints requirement in 2026: what the regulator expects
The ICO published final guidance on handling data protection complaints in February 2026. Key points for small operators:
- Any channel counts. You can offer a preferred route, but a complaint sent by email, live chat, social media or through a support ticket is still a complaint.
- No standalone system needed. An existing email inbox, web form or helpdesk is fine, as long as complaints are recognised and tracked.
- Automated acknowledgements are acceptable for complaints made electronically.
- No fixed deadline for the outcome, but "without undue delay" means no unjustified delay, judged case by case.
- Keep records of receipt, acknowledgement, enquiries and outcome. The ICO may ask to see them.
- Tell people about the route, for example in your privacy notice and when you respond to rights requests.
The ICO also expects people to raise concerns with the organisation first, and it can decline to deal with complaints that haven't been through your process. A working procedure therefore protects you as well as the complainant: it gives you the chance to fix things before a regulator gets involved.
The DUAA 30-day acknowledgement: how to count it
The 30-day period begins when you receive the complaint and includes weekends and bank holidays. The acknowledgement does not need to answer the complaint; it confirms receipt and sets expectations. Hypothetical example: a complaint arrives through your contact form on Saturday 4 July. Your auto-reply acknowledges it the same day, which comfortably meets the 30-day duty. You then reply properly within, say, two weeks, after checking your systems.
Don't confuse complaints with requests. A subject access or erasure request has its own one-month deadline. If someone complains that you didn't answer their request, deal with both: answer the request and handle the complaint. See how to respond to a subject access request.
A simple data protection complaint handling process for small sites
- Create the route. Add a "Privacy complaints" section to your privacy notice with a dedicated email address and a short web form. Offer a postal address as an alternative.
- Set up the acknowledgement. An automatic reply that confirms receipt, gives a reference number, and says when the person can expect to hear back.
- Log it. A spreadsheet with: reference, date received, channel, summary, date acknowledged, enquiries made, outcome, date closed.
- Investigate proportionately. Check the relevant systems, ask any processor involved, and identify whether something went wrong.
- Update the complainant if it is taking longer than you said.
- Close with a clear outcome. Say what you found, what you have done (deleted data, fixed a setting, changed a process), and that they can complain to the ICO if they remain unhappy.
- Learn from it. Recurring complaints about the same issue, such as marketing emails after unsubscribing, are a sign to fix the underlying problem.
What to put in a privacy complaint form
Keep it short. Ask only for what you need to find the person's data and understand the problem:
- name and the email address associated with their account or subscription;
- a free-text description of the complaint;
- optional: date of the issue, any reference number, and the outcome they want;
- a note that they can also complain by email or post if they prefer.
Don't make ID upload mandatory just to complain. If you later need to verify identity before disclosing data, ask then, proportionately. For adult and creator businesses, keep acknowledgement emails neutral in sender name and subject line.
Does it apply to me if I'm outside the UK?
The duty applies to controllers subject to UK data protection law, which includes businesses outside the UK that offer goods or services to people in the UK or monitor their behaviour. The EU GDPR has no equivalent statutory complaints procedure, though handling complaints well is still good practice and reduces regulator escalations. For more on how the regimes now differ, see UK GDPR vs EU GDPR.
Frequently asked questions
Do I need to publish a complaints policy?
Publishing a full policy isn't required. You do need a working route that people can find, and it makes sense to describe it in your privacy notice.
What if the complaint is about one of my partners, such as an affiliate network?
If it concerns data you control, it is your complaint to handle, even if a partner caused the problem. If the partner is an independent controller, you can explain that and point the person to them, while handling the part that relates to you.
Is a one-person business really covered?
Yes. The duty applies to controllers regardless of size. A shared inbox, an auto-reply and a simple log are enough for most small sites.
Next steps
Add a complaints section to your privacy notice today; our guide to a privacy policy for an affiliate website shows where it fits. If you are setting up a UK site from scratch, our checklist for launching an affiliate site in the UK covers the other legal basics.