The Data (Use and Access) Act 2025 is the most significant change to UK data protection law since the UK GDPR first took effect. It amends the rules your organisation follows every day, but it does not replace them. For Data Protection Officers, Heads of Legal and privacy teams, the practical question is simple: what has changed in UK GDPR between 2024 and 2026, and what does it mean for your working day?
The short answer is that the framework you already know remains in place, with targeted adjustments to access requests, complaints, automated decisions, data sharing, research, cookies and marketing enforcement. Some of these changes give you more flexibility. Others add new obligations with firm deadlines. Treating them as one large compliance project usually leads to delays, so a better approach is to map each change to the people, processes and systems it affects. The sections below set out what changed, when it changed, and where your attention is most needed.
The New UK Rule Book
The Data (Use and Access) Act 2025, usually shortened to DUAA, is an amending statute rather than a new standalone code. It amended the UK GDPR, the Data Protection Act 2018 and PECR, and the majority of its provisions came into force on 5 February 2026. You can read the consolidated text of the Act itself if your legal team needs to trace a specific amendment back to its source.
Commencement has been staged, which means your compliance calendar needs more than one date in it. The two dates that matter most for most organisations are:
- 5 February 2026: the bulk of the reforms took effect, including changes to automated decision-making, research, data sharing and PECR enforcement.
- 19 June 2026: the new formal complaints procedure requirement begins.
The core principles have not changed. Lawfulness, fairness and transparency, purpose limitation, data minimisation, accuracy, storage limitation, security and accountability all remain the foundation of UK data protection law. You still need a lawful basis for processing, you still need Records of Processing Activities, and you still need DPIAs for high-risk processing.
This continuity matters for your planning. Your existing privacy programme does not need rebuilding from scratch, but your policies, notices and workflows do need reviewing against the specific amendments. The organisations that manage this period with confidence are those that treat DUAA as a set of targeted updates to an established structure, not as a reason to start again.
Requests, Complaints, and Decisions
The rights changes most staff will meet first: access requests, complaints and automated decisions.
Rights handling is where most of your colleagues will feel the reforms first, because it touches customer service teams, HR and frontline staff as well as the privacy function.
Subject access requests remain a core right, and the reforms aim to give you greater clarity about how far your searches need to go. Your teams should document the scope of each search and the reasoning behind it, since that record is what demonstrates a proportionate response if a requester or the regulator later questions it.
Complaints are the most concrete new obligation. From 19 June 2026, organisations must have a formal data protection complaints procedure, including acknowledging complaints within 30 days, and you are expected to respond without undue delay. In practice, this means you need an intake route, a named owner, a tracked acknowledgement and an auditable record of the outcome.
Automated decision-making has changed in a more fundamental way. The DUAA replaces the previous prohibition on solely automated decisions with a permission-plus-safeguards model for data that is not special category data. Those safeguards include a right to contest the decision and to obtain human intervention. The government states that the reforms make it clear to controllers and individuals when the safeguards and restrictions apply.
If your organisation uses automated credit checks, recruitment screening or fraud scoring, you should confirm three things: whether the decision is solely automated, whether special category data is involved, and whether your contest and review routes actually work when someone uses them.
Using and Sharing Data
When you can share data, re-use it for something new, or send it abroad.
The reforms are designed to make responsible data use clearer, and in several areas they give your organisation more room to innovate. The ICO notes that the DUAA makes it clearer when you can use personal information for scientific research, including commercial scientific research. For product, analytics and R&D teams, that clarity can shorten the time between an idea and a compliant project.
Re-using data for a new purpose has also been given a clearer structure. Purpose limitation still applies, but the Act sets out more explicitly when a further purpose can be treated as compatible with the original one. Your teams should still record the compatibility assessment, because the clarity of the rule does not remove the need to show your reasoning.
Data sharing benefits from the introduction of recognised legitimate interests, which cover certain public-interest purposes such as safeguarding and crime prevention. These reduce the need for a full balancing test in defined situations, although you will still need to identify which recognised interest applies and keep evidence of that decision.
International transfers continue to require a lawful mechanism, and the DUAA reframes the test the UK applies when assessing whether protection abroad is adequate. For most organisations, the practical steps remain familiar:
- Map your transfers: know which vendors and group entities receive personal data outside the UK.
- Review your mechanisms: confirm that contracts and transfer assessments reflect the amended rules.
- Record your decisions: keep TIAs and vendor assessments linked to the relevant processing records.
Where your organisation is going through M&A due diligence or onboarding new third parties, these records become the evidence that buyers, partners and regulators will ask to see.
Marketing, Children, and What’s Next?
Cookies, bigger marketing fines, designing for children, and what’s still coming.
Marketing and cookies sit under PECR rather than the UK GDPR itself, but the DUAA has changed them significantly. Certain low-risk cookies and similar technologies, such as those used for some analytics and service improvement purposes, may now be set without consent where the conditions are met. Your consent banners and cookie audits should be reviewed so that you neither over-ask nor under-protect.
The enforcement position is the change that boards tend to notice. Maximum fines for PECR breaches have increased from £500,000 to the higher of £17.5 million or 4% of global annual turnover, aligning them with UK GDPR penalties. Unsolicited marketing, consent failures and cookie breaches now carry the same financial exposure as serious data protection failures, which makes the reputational and financial case for investment much easier to present to your executive team.
Children’s data receives explicit attention. Organisations providing online services likely to be used by children are expected to consider their higher protection needs when designing those services. This is Privacy by Design in its most practical form: decisions about defaults, profiling and data collection should be made, documented and approved before launch, not retrofitted afterwards.
What remains to come is mostly guidance and staged commencement. The ICO continues to publish updated guidance, and some provisions take effect later in the commencement timetable. The most sensible approach is to assign an owner for regulatory monitoring, schedule periodic reviews of your policies, and keep a change log that shows when each amendment was assessed and how your organisation responded. That record is the clearest evidence of accountability you can offer a regulator.
Building Confidence Into Your Programme
The question of what has changed in UK GDPR has a reassuring answer: the foundations remain, while the details have moved. Access requests need documented proportionality, complaints need a formal process by 19 June 2026, automated decisions need working safeguards, and marketing failures now carry fines comparable to the most serious data protection breaches. Each of these is manageable, provided your people, processes and systems are aligned before the deadline rather than after it.
Think of it as you would a change to accounting standards. Finance teams do not rebuild their ledgers each time a rule shifts; they update their controls, record the decision and move forward with an auditable trail. Your privacy programme deserves the same discipline.
If your team is still working across spreadsheets, inboxes and disconnected tools, now is the time to consolidate. PrivacyEngine brings RoPA records, DPIAs, rights requests, complaints, breach governance and vendor assessments into one platform designed by DPOs for DPOs, so your accountability evidence is always ready. Book a Demo to see how it fits the way your team already works.



