United Kingdom version. Opens on the United Kingdom filter: UK GDPR with the Data Protection Act 2018, and PECR for cookies and marketing, with fines as amended by the Data (Use and Access) Act 2025. US version

Software Compliance Checklist (UK)

Build a software compliance checklist for the UK: UK GDPR, the Data Protection Act and PECR cookie and marketing rules, with maximum fines and ICO links.

The interactive tool loads here when JavaScript runs.

About this tool

What is the Software Compliance Checklist?

This version opens on the United Kingdom filter, which lists the two regimes a UK software product meets first: the UK GDPR read with the Data Protection Act 2018, and the Privacy and Electronic Communications Regulations (PECR) for cookies, similar tracking and electronic marketing. Each card gives the main duties, who the law applies to, the maximum fine and links to legislation.gov.uk and the ICO.

The figures are UK ones. The higher maximum under section 157 of the Data Protection Act 2018 is £17.5 million or 4% of annual worldwide turnover, whichever is higher, with £8.7 million or 2% for other infringements. Since 5 February 2026 most PECR breaches carry the same higher maximum, after the Data (Use and Access) Act 2025 raised PECR fines from the old £500,000 cap.

Add the cards to your checklist, then switch the geography filter to Global for standards UK buyers ask about, such as ISO 27001, PCI DSS and SOC 2, or to EU if you also serve customers there. The list is a starting map, not legal advice.

  • 31 laws, standards and frameworks with requirements and penalties
  • Search plus domain and geography filters
  • Custom checklist downloaded as Markdown task list
  • CSV export of the filtered list
  • Runs in your browser with no account
Read the guide: Which Compliance Rules Apply to Your Software? A Map for Engineers

Updated

How to use the Software Compliance Checklist

  1. On the Browse Compliances tab, type in Search compliances (for example "cookies" or "health") and narrow with the Domain and Geography filters.
  2. Click a card to open its details: requirements, applicability, penalties, related items and official resources.
  3. Click the + on a card to add it to your checklist.
  4. Open the My Checklist tab, rename the checklist, and click Download MD to save a Markdown file with a checkbox for every requirement.
  5. Use Export Report on the Browse tab to download the currently filtered list as CSV.

Worked examples

UK SaaS with a marketing site

Input

Geography: United Kingdom

Output

2 results: UK GDPR and Data Protection Act 2018, and PECR

The product's personal data falls under the UK GDPR; the analytics cookies and newsletter fall under PECR. Most UK teams need both checklists, and the cookie banner is where PECR bites first.

Taking card payments as well

Input

Geography: Global, Domain: Payments

Output

PCI DSS appears alongside the global standards

PCI DSS is a contractual card-scheme standard, not UK law, so it sits under Global. Hosted payment fields keep most card data out of your scope.

Background and insight

Most software teams meet compliance through a product decision rather than a legal memo: a signup form that collects a birth date, a checkout that stores card numbers, an analytics script that sets cookies for EU visitors. Each of those pulls in a different regime. Card data brings PCI DSS, health records held for a US covered entity bring HIPAA, children under 13 bring COPPA, and EU residents' personal data brings GDPR wherever the company is based.

The documents differ in kind. GDPR, CCPA and HIPAA are laws with regulators and fines; GDPR's upper tier is EUR 20 million or 4 percent of worldwide annual turnover, whichever is higher, and it requires breach notification to the authority within 72 hours. PCI DSS is a contractual standard set by the card brands (version 4.0 became the only active version in 2024). SOC 2 is an attestation report by an independent CPA firm against AICPA criteria, not a certification. WCAG 2.2, published by the W3C in October 2023, is the technical yardstick most accessibility laws point to.

Engineering work tends to repeat across regimes: an inventory of personal data, access control and audit logs, encryption in transit and at rest, retention and deletion, breach response, vendor contracts, and accessible UI. Building those once and mapping them to each framework is cheaper than treating every framework as a separate project.

Common use cases

  • Scoping a new product

    List the regimes a feature might trigger before design starts, while changes are cheap.

  • Answering a security questionnaire

    Get a quick summary of SOC 2, ISO 27001 or HIPAA terms an enterprise buyer asks about.

  • Planning an engineering roadmap

    Download a Markdown checklist and turn requirement lines into tickets.

  • Onboarding new engineers

    Give a team a shared vocabulary for the frameworks their product is subject to.

Tips and limitations

  • Report a personal data breach to the ICO within 72 hours of becoming aware of it unless it is unlikely to result in a risk to people; keep a record of every breach either way.
  • Most organisations that process personal data must pay the ICO data protection fee; check whether you are exempt.
  • Transfers to the US and elsewhere need UK adequacy regulations (such as the UK-US data bridge), the IDTA or the UK Addendum.
  • The Data (Use and Access) Act 2025 added cookie exemptions for some low-risk purposes; read the ICO guidance before relying on one.

Sources and further reading

  1. Statement on the commencement of the Data (Use and Access) Act, Information Commissioner's Office. The higher PECR fines from 5 February 2026; they do not cover the PECR breach-notification duty.
  2. Data Protection Act 2018, section 157: maximum amount of penalty, legislation.gov.uk
  3. UK GDPR guidance and resources, Information Commissioner's Office
  4. Privacy and Electronic Communications Regulations 2003, legislation.gov.uk
  5. Data (Use and Access) Act 2025, legislation.gov.uk

Frequently asked questions

Is the UK GDPR the same as the EU GDPR?

It started as a copy kept in UK law after Brexit and is read with the Data Protection Act 2018. The Data (Use and Access) Act 2025 has since changed parts of it, so UK and EU rules are drifting apart. If you serve both, keep both cards in your checklist.

What is the maximum UK GDPR fine?

Up to £17.5 million or 4% of total annual worldwide turnover in the preceding financial year, whichever is higher, for the most serious infringements; up to £8.7 million or 2% for others (Data Protection Act 2018, section 157).

Do I need consent for analytics cookies in the UK?

Under PECR you need consent for storage or access that is not strictly necessary, unless one of the exemptions applies. The Data (Use and Access) Act 2025 added exemptions for some purposes such as certain statistical analytics, with conditions; check the ICO guidance for the current position.

How much can the ICO fine for PECR breaches now?

Since 5 February 2026, most PECR breaches can be fined up to £17.5 million or 4% of worldwide turnover, the same as the UK GDPR higher maximum, instead of the old £500,000 cap.

Does a small UK start-up need a Data Protection Officer?

Only if its core activities involve large-scale regular monitoring of people or large-scale special category or criminal offence data, or it is a public authority. Most small SaaS firms name a privacy lead instead.

Is there an in-depth guide to the Software Compliance Checklist?

Yes. “Which Compliance Rules Apply to Your Software? A Map for Engineers” covers the background, how it works, common pitfalls and worked examples. Read the full guide.