UK GDPR for websites and apps: what to build in from the start
In 2026 a UK website or app handles personal data under UK GDPR and the Data Protection Act and sets cookies under PECR, as changed by the Data (Use and Access) Act 2025, whose new cookie rules apply since 5 February 2026.
Clinic Website with Online BookingSources checked on 12 November 2026What applies in the UK
The laws, the regulator and what changed in 2026.
- In forceThe rules
- In forceData (Use and Access) Act 2025
- Checked on 12 November 2026
More
- In forceThe rules
UK GDPR and the Data Protection Act 2018 cover personal data; PECR covers cookies and electronic marketing. The ICO regulates all three.[1]
- In force
- Checked on 12 November 2026
- Analytics without consent
Analytics may run without consent if users get clear information and a simple, free way to object. The exception cannot be used for advertising or to track individuals.[4]
- Higher PECR fines
PECR fines can now reach £17.5 million or 4% of worldwide turnover, the same ceiling as UK GDPR.[5]
- Breaches
A personal data breach that is likely to put people at risk must be reported to the ICO without undue delay and, where feasible, within 72 hours.[6]
Sites that book, sell, explain.
Related pages
More
Builders against custom sites, AI agents and accessibility.
- Website builder or custom
- Wix, Squarespace, Shopify or your own site.
- AI agent
- Agents that answer, book, file and check.
- Web accessibility in the UK
- The Equality Act, WCAG and the EAA.
What a UK website or app should have
The parts we put into the first release.
Tick the ones that apply to you.
More
- Privacy notice
- What you collect, why, for how long and who receives it.
- Cookie choices
- Consent for advertising and other non-exempt storage; an easy objection for analytics.
- Processor contracts
- A written agreement with every provider that handles personal data for you.
- Rights on request
- Export and deletion of a person’s data without a developer.
- Access and logs
- Roles for your staff and a record of who saw or changed what.
- A breach plan
- Alerts and logs, so you know in time to report.
How we build it
Privacy as a feature, not a pop-up added later.
- Less data
- Hosting you choose
- Our part
More
- Less data
- Each form asks only for what the next step needs.
- Hosting you choose
- The hosting region is agreed with you and written into the scope.
- Our part
- Where we handle your data, we sign a data processing agreement with you.
Read more on this
Checked on 12 November 2026
A summary for planning software, not legal or tax advice. Rules change: check the source or ask your adviser before you rely on a date.
Sources
- ICO: Legislation we cover
- GOV.UK: Data (Use and Access) Act 2025, plans for commencement
- legislation.gov.uk: The Privacy and Electronic Communications Regulations 2003, regulation 6
- ICO: Storage and access technologies, what are the exceptions?
- ICO: Statement on the commencement of the Data (Use and Access) Act
- ICO: Personal data breaches
Questions we get asked
Can we drop the cookie banner now?
Only if everything you use is exempt, such as strictly necessary storage and analytics with an easy way to object. Advertising and most third-party tags still need consent.
Do UK GDPR and EU GDPR both apply?
If you offer goods or services to people in the EU, EU GDPR can apply as well. Ask your adviser how it applies to you.
What does a privacy-ready website cost?
Websites start from €2,500; consent, privacy notice and processor setup are part of the scope.

Local rules belong in the first scope, not in a fix after launch. That is why we put them into the quote.
Build it right the first time
Tell us what data your site or app collects; we price the build.




