The Data (Use and Access) Act does not rewrite subject access. It adjusts the mechanics around it, and the real work lands in your tooling, not your policy library.
Most of the commentary on the DUAA has been written for lawyers, and it reads that way: a tour of amended sections, a note that the changes “largely codify existing practice”, a reassurance that little has changed. That is true at the level of legal obligation. It is misleading at the level of the systems you actually operate. A codification of existing practice still has to be encoded in the DSAR platform, the case-management workflow and the privacy notice, and until it is, your tooling is running the old assumptions. This is a reading of what changes in the configuration, written for the people who own that configuration rather than the ones who advise on it.
What the Act actually touches
Two changes matter for the machinery. The first is a set of clarifications to how subject access requests are handled, which came into force with the main data-protection provisions of Part 5 on 5 February 2026. These put a statutory footing under two things the ICO had long said in guidance: that the response clock can be paused while you seek clarification or verify identity, and that the search you run need only be reasonable and proportionate rather than exhaustive. The second is genuinely new: a statutory complaints-handling duty on controllers, in force from 19 June 2026, which requires you to give people a way to complain directly to you, acknowledge it, and investigate.
Free · 4 minutes
Is your engineering team shipping safely, or quietly accumulating risk?
Fourteen questions on how work gets from idea to production — cadence, testing, rollback, and the key-person risk in your delivery. Banded finding on screen, full sheet by email.
Neither is dramatic in isolation. Together they change three distinct parts of your estate: the timer logic in your DSAR tool, the scoping assumptions behind your searches, and a complaints route that for most firms does not exist as a system at all. Treat them as a policy update and you will either over-engineer the response or miss a deadline you did not realise had moved.
Stop-the-clock is now a state machine, not a courtesy
The one-month response period is unchanged, and so is the ability to extend it by a further two months for complex or numerous requests. What the Act does is put the pause on a firmer footing: where you reasonably need further information to identify the requester or to clarify what they are asking for, the clock does not run while you wait for their reply. Practically, that has always happened. The problem is that most DSAR tooling models the deadline as a single date arithmetic from receipt, and a pause implemented as a manual note in a comment field.
If the pause has statutory weight, it needs to be a first-class state, not a note. That means the request record has to carry an explicit status — awaiting clarification, awaiting identity verification — with a timestamp when it enters and leaves that state, so the deadline is computed from elapsed working time rather than a fixed calendar date. It also means the trigger has to be defensible: a supervisor reviewing a late response will ask when the clarification request went out, what it asked for, and when the answer arrived. If your tool cannot produce that timeline automatically, you are relying on someone having written it down, and that is exactly the evidence that goes missing. The engineering task is small. The failure mode of not doing it is a clock that a regulator can argue never legitimately stopped.
Reasonable and proportionate is a scoping decision, not a licence to under-search
The proportionate-search standard is the change most likely to be misread, in both directions. Read too generously, it becomes an excuse to search only the easy sources and call it done. Read too cautiously, it changes nothing and you keep running the exhaustive sweep across every backup and archive you have. The Act’s position sits between: you must make reasonable efforts, judged against the volume of information, the difficulty of retrieval and your resources, but you are not required to turn the estate upside down.
For tooling, that turns search scope into a documented decision rather than a fixed script. The useful artefact is a search-scope record attached to each request: which systems were queried, which were excluded, and the proportionality reason for each exclusion. That record is what makes the standard operable — it lets you defend a narrower search on a genuinely disproportionate source without inviting the accusation that you simply did not look. The same discipline of turning a legal test into a reusable, evidenced decision is what makes the rest of the DUAA workable, from the recognised legitimate interests regime to the assessments behind it. Without the record, proportionality is just an assertion, and assertions are what supervisory engagements are designed to test.
The complaints duty is new plumbing
This is the part that is not a tweak. From 19 June 2026, a new section 164A of the Data Protection Act 2018 requires controllers to facilitate complaints about how they handle personal data — including, in the ICO’s framing, providing an accessible route such as an electronic form that can be completed and submitted online — to acknowledge a complaint within 30 days of receiving it, and to take appropriate steps to investigate without undue delay, keeping the complainant informed of progress and outcome.
For most firms the gap is not the form; it is everything behind it. A complaint submitted through a web form has to become a tracked case with an owner, an acknowledgement that fires inside 30 calendar days, an investigation step, and a communication trail. If your only current route is a shared inbox that someone triages when they can, you do not have a compliant process — you have a place where the 30-day clock starts running unnoticed. There is a routing question too: a message that is really a subject access request, or a rectification demand, should land in the DSAR workflow, while a genuine complaint about your handling goes down the new track. Getting that classification right at intake is what stops one duty’s clock being started by the wrong queue. The privacy notice also has to change, because the amended transparency provisions expect you to tell people the complaint route exists.
What survives unchanged
It is worth being clear about what you do not need to touch, because over-reaction is as costly as neglect. The lawful bases have not moved. The one-month baseline and the two-month extension are the same. The exemptions you already apply — legal privilege, third-party data, management-forecast material — are intact, and the redaction logic that implements them does not change. Identity verification is still required; the Act simply confirms that seeking it stops the clock. If you built a defensible DSAR pipeline under the old regime, most of it stands, and the same underlying case-handling engine can carry the new complaints track rather than justifying a separate build. This is the kind of consolidation worth doing deliberately, in the same spirit as running one assessment engine across several regimes instead of standing up a tool per obligation.
The wider DUAA reshaping — smart data, digital verification, the recast legitimate-interests provisions — is a larger programme, and the smart data schemes in particular will demand real build work over the next few years. Subject access and complaints are not that. They are a bounded retune of systems you already run. The mistake is to file them under “minor legal update” and leave the tooling asserting a pause it cannot evidence and starting a complaints clock it cannot see.
Sixteen Pillars is a technology governance consultancy based in Cyprus. Engagements run remote across the EU, UK, and Middle East, with on-site time where the engagement requires it.
Free interactive tool
Website compliance checklist
What your site has to do, based on what it actually does
Answer as much or as little as you like — the list builds as you go. Nothing is stored against your name and no email is required.
Everything that applies
Ordered by what to do first: legal requirements you can close quickly, then larger pieces of work, then what is expected rather than required. Not exhaustive, and not a legal audit.
Dated PDF, yours to keep or circulate.
Free interactive tool
Interactive deadline calculator
Check which regulations apply to you and when
Regulation across the EU, UK, US and Asia-Pacific has moved considerably in the past eighteen months, and several headline dates have shifted more than once. Twelve questions, about three minutes.
Results are shown on screen — no email required. A dated summary is available to download, and can be sent on if that's more useful. What we do with your answers.
Most technology problems are not technology problems. They are control problems.
The systems exist. The investment has been made. The question is whether leadership can understand, direct, evidence, and sustain what those systems produce. Find out where control exists — and where it only appears to.
Full Governance by Sixteen Pillars
Govern your business. Prove your compliance.
A board assurance cockpit for EU-regulated financial firms — tamper-evident, hash-chained proof of governance across DORA, GDPR, NIS2, ISO 27001, the EU AI Act and MiCA. In development.
See what's coming