The UK GDPR vs EU GDPR differences used to be cosmetic: after Brexit the UK copied the EU text almost word for word. That changed on 5 February 2026, when most of the Data (Use and Access) Act 2025 (DUAA) came into force. The UK now has a new "recognised legitimate interests" lawful basis, looser rules on automated decisions, consent exemptions for some cookies, a statutory complaints duty and a different test for international transfers. The core principles, rights and fine levels remain closely aligned, and the EU renewed its UK adequacy decision in December 2025, so data still flows freely from the EU to the UK.
For a webmaster with visitors in both markets, the practical upshot is simple: the UK is slightly more permissive in a few areas, so if you build to EU standards you will almost always comply in the UK too. The table and sections below show exactly where the two now diverge.
This is general information, not legal advice. Take professional advice before relying on a UK-only exemption.
UK GDPR vs EU GDPR differences at a glance
| Topic | EU GDPR | UK GDPR (as amended by the DUAA) |
|---|---|---|
| Lawful bases | Six bases in Article 6 | The same six plus "recognised legitimate interests" (no balancing test for a fixed list of purposes) |
| Legitimate interests examples | Recitals mention direct marketing and fraud prevention | The Act itself names direct marketing, intra-group transfers and network security as examples, but a balancing test is still required |
| Automated decisions | Article 22: general restriction on solely automated decisions with legal or similarly significant effects | Restrictions focus on decisions involving special category data; other automated decisions are allowed with safeguards |
| Cookies (ePrivacy/PECR) | Consent for all non-essential cookies | No consent needed for statistical and appearance cookies, with a simple opt-out (since 5 February 2026) |
| Cookie and email fines | Set nationally under ePrivacy laws | PECR fines now up to £17.5m or 4% of turnover |
| Complaints | Individuals can complain to a supervisory authority | Controllers must run their own complaints process and acknowledge complaints within 30 days (from 19 June 2026) |
| Subject access requests | Guidance and case law on scope | Act confirms searches need only be "reasonable and proportionate" |
| International transfers | Adequacy requires "essentially equivalent" protection | New test: protection must be "not materially lower" than in the UK |
| Maximum fines | €20m or 4% of global turnover | £17.5m or 4% of global turnover |
| Regulator | National DPAs, with a one-stop-shop for cross-border processing | ICO only; no one-stop-shop with the EU |
UK GDPR changes in 2026: what the Data (Use and Access) Act changed
The DUAA received Royal Assent on 19 June 2025 and was commenced in stages. Most data protection provisions took effect on 5 February 2026, with the complaints procedure following on 19 June 2026. Here is a short Data (Use and Access) Act summary of the changes that matter to webmasters.
Recognised legitimate interests
A new lawful basis lets organisations process data for a fixed list of purposes without carrying out the usual balancing test. According to the ICO's guidance, the conditions cover responding to public-task disclosure requests, national security and defence, emergencies, crime and safeguarding. You still need to show the processing is necessary. None of these covers marketing, analytics or affiliate tracking, so for most publishers it changes very little. We explain the knock-on effects in legitimate interests vs consent.
Named examples of legitimate interests
The UK text now names direct marketing, internal intra-group transfers and IT security as purposes that may be legitimate interests. The ICO's March 2026 guidance is clear that you still have to pass the balancing test. Remember also that marketing by email or text is governed by PECR, which usually requires consent whatever your GDPR lawful basis.
Automated decision-making
The UK replaced its Article 22 with a more permissive framework. Solely automated decisions with significant effects are allowed on more lawful bases, as long as safeguards are in place: telling people about the decision, letting them make representations, offering human intervention and allowing them to contest it. Stricter limits remain where special category data is involved. For an adult platform using automated moderation or fraud scoring, this offers somewhat more room in the UK than the EU, but the safeguards are not optional.
Cookie exemptions and PECR fines
PECR now allows statistical cookies used to improve a website, and cookies that remember appearance preferences, without consent, provided users get clear information and a simple, free way to object. PECR fines rose to UK GDPR levels. See our full guide to the new UK cookie exemptions.
Complaints procedure
From 19 June 2026, controllers must make it easy for people to complain to them about how their data is handled, acknowledge complaints within 30 days, investigate without undue delay and report the outcome. Your privacy notice should explain how to do this.
Research, transfers and subject access
The Act clarifies what counts as scientific research, adds the "not materially lower" test for transfers out of the UK and confirms that subject access searches need only be reasonable and proportionate. Organisations still must answer within one month, extendable in some cases.
The EU adequacy decision for the UK
The biggest commercial question was whether the EU would keep treating the UK as "adequate" after the reforms. It did. On 19 December 2025 the European Commission adopted renewed adequacy decisions under the GDPR and the Law Enforcement Directive. They run until 27 December 2031 unless extended, with a review due within four years, and the Commission will monitor further UK changes in the meantime.
For webmasters this means:
- EU businesses can send personal data to UK hosting, analytics or affiliate partners without standard contractual clauses.
- UK companies serving EU users still have to comply with the EU GDPR for those users; adequacy is about transfers, not about which law applies.
- If the UK diverges further, adequacy could come under pressure again. Build processes that can flex.
What stays the same
It is easy to overstate the divergence. The following are still essentially identical:
- The seven principles: lawfulness, fairness and transparency, purpose limitation, data minimisation, accuracy, storage limitation, integrity and confidentiality, plus accountability.
- Individual rights: access, rectification, erasure, restriction, portability and objection.
- The consent standard: freely given, specific, informed, unambiguous, as easy to withdraw as to give.
- Special category data rules, which matter on adult sites where browsing can reveal sex life or sexual orientation.
- Breach notification within 72 hours where there is a risk to individuals.
- Processor contracts, records of processing, DPIAs for high-risk processing.
- Extraterritorial reach: both laws apply to non-resident businesses that target or monitor people in their territory.
The last point has a practical consequence. If you are based in one jurisdiction and serve the other, you may need a representative there. Our guide to EU and UK GDPR representatives explains when.
What the divergence means for your website
Most webmasters serving both markets have three realistic options.
| Approach | How it works | Best for |
|---|---|---|
| EU standard everywhere | Apply EU rules (consent for all non-essential cookies, EU-style Article 22) to all visitors | Small teams; sites where UK traffic is a minority |
| Geo-split cookies only | Use the UK statistical and appearance exemptions for UK visitors; everything else at EU standard | UK-heavy content sites that want better analytics coverage |
| Full dual regime | Separate processes for lawful basis, ADM and transfers per market | Larger platforms with legal support |
A hypothetical example: a UK-registered review site with 60% UK and 40% EU traffic geo-targets its consent tool. UK visitors get privacy-configured analytics by default with an opt-out link in the banner; EU visitors see an opt-in banner. Advertising and affiliate pixels remain consent-only in both. Its privacy notice explains the difference and includes the UK complaints route.
Check first: geo-targeting relies on IP-based location, which is imperfect. If your consent tool falls back to UK behaviour when it can't locate someone, you may be applying UK exemptions to EU visitors. Make the fallback the stricter EU rule set.
Frequently asked questions
Is UK GDPR still the same as EU GDPR?
Mostly, but not entirely. The principles, rights and core obligations are the same, but since February 2026 the UK has a new recognised legitimate interests basis, more flexible automated decision rules, cookie exemptions and a complaints duty that the EU does not have.
Does a UK company need to comply with EU GDPR?
Yes, if it offers goods or services to people in the EU or monitors their behaviour, for example through tracking cookies. The EU GDPR then applies to that processing alongside the UK GDPR, and you may need an EU representative.
Can I transfer data from the EU to the UK in 2026?
Yes. The renewed adequacy decisions adopted on 19 December 2025 allow transfers without extra safeguards until 27 December 2031, subject to review.
Does the UK cookie exemption apply to EU visitors to a UK site?
No. If you target EU visitors, EU ePrivacy rules as implemented in their country protect them, and those rules have no equivalent UK-style exemption. Assume EU visitors need opt-in consent for analytics unless a national exemption, such as France's for narrowly configured analytics, applies.
Next steps
If you only change one thing, review your cookie setup against the new UK exemptions and make sure EU visitors still get opt-in consent. Then check your lawful bases and privacy notice. For questions about whose rules apply in the first place, see which country's law applies to your website, and find related guides in our GDPR and cookies section.