UK GDPR Compliance in 2026: What the DUAA Changes in Software
Published 4 November 2026 · 10 min read
Most DUAA provisions began 5 Feb 2026 and the complaints duty on 19 June. What UK GDPR compliance now requires in your software, plus costs.
The short answer
The Data (Use and Access) Act 2025 (DUAA) did not replace the UK GDPR — it amended it, and most of its data protection provisions came into force on 5 February 2026, with the new complaints duty following on 19 June 2026. For software teams, that means a handful of concrete, buildable changes: a complaints route inside your product, a lawful "stop the clock" pause on subject access requests, a narrower cookie banner, revised automated decision-making safeguards, and a restated test for sending data abroad. Most of the work is engineering and process work rather than paperwork, which is why it tends to get missed until an ICO complaint lands.
This guide is written for founders, product owners and engineering leads shipping software to UK users. If you want the wider picture of operating in this market, start with our UK technology and compliance hub, and for the implementation detail see UK GDPR compliance implementation. Stratgik is a technology firm, not a law firm: we build and operate the systems that make an obligation real, and we expect you to take your own legal advice on what the obligation is.
What actually changed, and when
The DUAA received Royal Assent in June 2025 and has been commenced in stages by statutory instrument. The ICO's commencement statement confirms that most remaining data protection provisions took effect on 5 February 2026, that the complaints procedure requirement is due on 19 June 2026, and that some ICO governance provisions follow later. Other provisions were commenced separately — the Commencement No. 5 Regulations 2026 brought section 138 into force on 6 February 2026.
So there is no single "DUAA compliance date". Two dates matter to your backlog: February, which has passed, and June, which carries a product dependency.
The 19 June 2026 complaints duty is the one that needs product work
From 19 June 2026, individuals have a right to complain about data protection directly to the controller, alongside their existing right to go to the ICO. The ICO's guidance, summarised well by Osborne Clarke, sets out what this looks like in practice:
- You must acknowledge a complaint within 30 days of receiving it.
- You must then respond without undue delay — there is no fixed statutory deadline as there is for subject access, and the ICO is explicit that blanket time periods are not appropriate. Each complaint is judged on its circumstances.
- You must keep the complainant informed of progress and tell them the outcome.
- You do not need a bespoke complaints form or tool. An existing complaints process can be adapted.
- You must offer a route to complain, but you choose the route — email, a portal, live chat, phone or in person. Crucially, individuals can still complain by other means, including social media, so you have to be able to recognise a complaint however it arrives.
The ICO has also said it will record complaint volumes per organisation and may review one that crosses a threshold within a set period. The thresholds are not finalised, and crossing one does not automatically mean enforcement. For scale: complaints to the ICO rose from 39,721 in 2023–24 to 42,881 in 2024–25.
Two engineering consequences follow. An auto-acknowledgement email is sufficient for electronic complaints, so the 30-day duty is cheap to satisfy — if complaints are routed into a system that can send one. And "recognise it however it arrives" is a triage problem, not a form problem: a privacy complaint that lands in a shared support inbox and is worked as a normal ticket leaves you with no acknowledgement, no audit trail and no evidence of outcome.
What each DUAA change means for your software
Drawing on the Clifford Chance summary of the commenced provisions, here is the translation from legal change to backlog item. The effort column is an indicative planning range for a single product with one primary database — treat it as a starting point for your own estimate, not a quote.
| DUAA change | In force | What you build or change | Indicative effort |
|---|---|---|---|
| Direct complaints right | 19 Jun 2026 | Complaint intake route, auto-acknowledgement, case record with status and outcome, triage rules across support channels | 5–15 days |
| Subject access "stop the clock" | 5 Feb 2026 | Clarification request flow and a deadline clock that pauses and resumes on the audit record | 3–8 days |
| Recognised legitimate interests | 5 Feb 2026 | Review and re-document lawful basis per processing activity; update the privacy notice and RoPA | 2–5 days |
| Automated decision-making | 5 Feb 2026 | Classify which decisions are "significant"; add transparency text, a contest route and human review for those | 5–20 days |
| Cookies and PECR exemptions | 5 Feb 2026 | Re-categorise tags; move qualifying cookies out of consent into a simple opt-out | 2–5 days |
| International transfers test | 5 Feb 2026 | Refresh transfer risk assessments against the new test; re-check sub-processor regions | 3–8 days |
Subject access: the clock can now stop
The one-month deadline for a subject access request has not changed, and can still be extended to three months where a request is complex. What has changed is that the deadline can be paused while you wait for a requester to clarify a vague request. The ICO's updated guidance drops the earlier condition that this applied only where you held a large amount of information about the person; as Slaughter and May note, clarification now needs only to be reasonably required. Volume is also a relevant factor in judging whether a search would be disproportionate, and refusals must tell the requester they can complain to the controller as well as the ICO and the courts.
In software terms this is a small but easily botched feature. A single due_date field no longer suffices: you need the request, the clarification sent, the clarification received and a derived deadline, plus refusal templates carrying the new three-route wording. Teams running subject access from a spreadsheet discover this the first time a requester disputes the date.
Cookies: a narrower banner, not no banner
Consent is no longer required for a defined set of low-intrusion purposes: statistical, appearance and emergency assistance cookies. Statistical and appearance cookies still need a free and simple opt-out, and the existing "strictly necessary" exemption is unchanged. Everything else — advertising, cross-site tracking, personalisation beyond appearance — still needs consent as before.
What makes this worth doing properly is the penalty change: the maximum PECR fine was £500,000 and now matches UK GDPR levels at £17.5 million or 4% of global annual turnover. A banner that was "good enough" when the downside was capped at half a million pounds deserves a second look. Our free website audit tool shows what your site actually loads before consent — usually more than the team believes.
Automated decisions and international transfers
The general prohibition on solely automated decisions with significant effects now applies only where the decision rests wholly or partly on special category data, such as health data — a genuine relaxation. But the safeguards (transparency, the ability to contest, human intervention) still apply to all significant automated decisions based on personal data. If you are adding AI-assisted scoring, triage or eligibility logic, only the outright prohibition has narrowed; the safeguard work remains. This is where we most often see a UK product get the new regime wrong, because "we're allowed to do it now" is heard as "we don't need the controls".
On transfers, the old "essential equivalence" test is replaced by a data protection test asking whether the standard in the destination country is not materially lower than the UK's; the ICO updated its transfer guidance on 15 January 2026 to reflect this. For most SaaS teams the output is the same artefact as before — a refreshed transfer risk assessment and an accurate list of where each sub-processor stores and accesses data — judged against a differently worded test. The ICO also gained teeth here: it can require a report at the controller's or processor's expense, compel witness interviews and demand specific documents.
What this costs, and where the money goes
The statutory cost is small. The ICO data protection fee sits at £52 for tier 1, £78 for tier 2 and £3,763 for tier 3, following an increase that took effect on 17 February. The real cost is engineering time and the ongoing operational load of handling requests and complaints once the routes exist.
So the decision in front of most teams is not "comply or don't" but "build or buy". A consent platform, a privacy request portal and a complaints case tool can all be bought off the shelf; the case for buying is speed and a maintained response to future guidance. The case for building is that your request flow has to reach into your own data model to actually fulfil a deletion or an export, and no vendor can do that for you. Most products end up with a bought front end and a built fulfilment layer. Our build vs buy calculator and app cost estimator will give you a defensible number for a planning meeting, and our custom software practice covers the fulfilment side where off-the-shelf tooling stops.
A build checklist for UK software teams
- Confirm a complaint can arrive by email, portal, chat, phone and social, and that each route creates one case record.
- Wire an auto-acknowledgement that fires inside 30 days — same day is simpler and safer.
- Store complaint status, enquiries made, updates sent and the final outcome against the case.
- Add a clarification step to subject access handling and make the deadline a derived value, not a typed date.
- Update refusal and response templates to name all three complaint routes.
- Re-run your tag inventory and move qualifying statistical and appearance cookies to opt-out, leaving everything else behind consent.
- List every significant automated decision in the product and confirm each has transparency text, a contest route and human review.
- Re-document lawful basis per processing activity, including anything you now rely on recognised legitimate interests for.
- Refresh transfer risk assessments and verify sub-processor regions against your own documentation.
- Check your ICO fee tier and that the registration is current.
- Assign an owner and a review date to each item above.
Frequently asked questions
Does the DUAA mean the UK no longer follows the GDPR?
No. The DUAA amends the UK GDPR, the Data Protection Act 2018 and PECR rather than replacing them. The core structure — lawful basis, data subject rights, accountability, the ICO as regulator — is unchanged. Treat it as a set of amendments to a regime you already have to meet, not a new regime.
Do we need a dedicated complaints form by 19 June 2026?
No. The ICO has confirmed that a separate form or complaints tool is not required and that an existing complaints process can be adapted. What you do need is a route people can use, an acknowledgement within 30 days, a substantive response without undue delay, and the ability to recognise a complaint whichever channel it arrives through.
How long do we have to resolve a data protection complaint?
There is no fixed deadline. The duty is to respond without undue delay, which the ICO defines as without an unjustifiable or excessive delay, assessed case by case. Setting an internal target is sensible operationally, but the ICO has said a blanket time period applied to every complaint is not the right approach.
Has the EU adequacy decision for the UK been affected?
The UK's adequacy status under EU law is a separate matter from the DUAA's domestic commencement, and the position continues to be reviewed by the European Commission. If your product moves personal data between the EU and the UK, confirm the current status with your legal adviser rather than assuming it from a blog post, including this one.
Does any of this apply to us if we are outside the UK?
Potentially yes. The UK GDPR's extraterritorial reach means a non-UK company offering goods or services to people in the UK, or monitoring their behaviour, can fall within scope. Many of the teams we work with are headquartered elsewhere and serve UK users through the same product. Our UK hub and UK GDPR compliance implementation pages set out how we scope that work, and managed technology covers running it once it is live.
Who should own this inside a small team?
A named engineering or product owner, with legal input rather than legal ownership. The failure mode we see most often is an obligation assigned to someone with no access to the backlog, so the paperwork exists and the product behaviour does not match it.
Most of what the DUAA asks of a software team is a week or two of focused engineering work, done once and then maintained. The expensive version is the one where a complaint arrives in June, nobody acknowledges it, and the response has to be reconstructed from a support inbox. If you would like a second opinion on where your product stands against the February and June changes, book a free 30-minute session with the Stratgik team and we will walk your request, complaint and consent flows with you and tell you plainly what needs building. We are a technology firm rather than a law firm, so we will say clearly where you need a lawyer instead.
Keep reading
More from Stratgik

22 Nov 2026
AI Automation Funding for Singapore SMEs: EDGE Grant 2026
PSG and EDG ceased on 29 September 2026. How Singapore SMEs now fund AI automation under the EDGE Grant, plus PDPA dutie...

21 Nov 2026
AI Ecommerce Automation in the UK: Rules, Cost and ROI 2026
Automating UK ecommerce support and returns with AI: the 2013 Regulations deadlines, DMCC and DUAA duties, real build co...

20 Nov 2026
Fixed-Price vs Time and Materials for Custom Software 2026
A 2026 guide to fixed-price vs time-and-materials software contracts: where each works, the clauses that matter, and who...

