How Nomkora checks the law

Every answer Nomkora gives is fixed text, written and checked before it goes live. Nothing is made up on the spot: the same answers about a build always give the same checklist. This page explains where that text comes from, how it's checked, how it's kept up to date, and what Nomkora can't do.

What we cover

UK and EU law that applies to websites, AI chatbots, AI agents and automations built for clients:

  • Data protection: UK GDPR and the Data Protection Act 2018 (as changed by the Data (Use and Access) Act 2025), and the EU GDPR.
  • Marketing messages and cookies: PECR in the UK and the ePrivacy Directive in the EU.
  • The EU AI Act, including the 2026 changes made by the Digital Omnibus on AI.
  • Selling online: UK and EU consumer law, including subscriptions and the EU withdrawal button.
  • Accessibility.
  • Extra flags for some industries: health, financial services, legal and accountancy, property, education and children, recruitment, physical products, food and drink, charities, and advertising.

Not covered yet: other countries' laws (we tell you when your build reaches them), the Online Safety Act, public sector accessibility rules, EU financial services rules, and Scotland's and Northern Ireland's own licensing and food rules. A detailed coverage map will follow.

Where the rules come from

Every rule is based on the law itself, not on someone's summary of it. We use, in this order:

  1. Legislation: the official text, from legislation.gov.uk for the UK and the Official Journal of the EU.
  2. Regulator guidance and codes: for example the ICO, the European Commission and the AI Office, the CMA, the FCA and the ASA.
  3. Court and regulator decisions.

News articles, blogs and law firm commentary can point us to something, but they're never a source. Each rule lists its sources under "Why", with the exact article or section.

How every rule is checked

Before a rule goes live, and each time it changes:

  1. Research. Each claim in the rule is traced to the exact article or section of the official text, read on the day, with the version noted. We use AI research tools for this step.
  2. Independent check. A separate check, working only from the draft and the official texts, reads every source again and tries to prove the draft wrong. Where the two disagree, the version the evidence supports wins, and the disagreement is written down.
  3. Approval. A named person at PM Product Solutions reads the evidence and approves the wording.
  4. Tested. The live site is tested against the approved wording, so what you see is exactly what was approved. Realistic example builds are run through the checker on every change, to catch a rule showing up where it shouldn't, or not showing up where it should.

Each check is written up in a report listing every claim, its source, the verdict and what changed.

Who approves the rules

Rules are approved by David Payne, co-founder of PM Product Solutions.

Outside review: no lawyer or data protection officer outside PM Product Solutions has reviewed the rules yet. We're appointing an outside expert to review new rules before they go live, and every rule each quarter. When they're in place, they'll be named here with the date of their last review.

Keeping it up to date

  • Every rule has a review date: every 3 months for AI law and for anything unsettled, every 6 months for everything else. If a rule's review date passes before it's re-checked, we can't publish an update to the site until it is. Out-of-date rules can't quietly stay live.
  • We watch for changes every week: new legislation, regulator guidance, consultations and court cases, across every law we cover. Anything that could change a rule is logged, then researched and checked in the same way before the rule changes.
  • Dates are kept in one place. When a law's start date moves, every rule that depends on it is re-checked.
  • Your checklist shows the date the laws were last checked, and every change is listed on What's changed.

What the labels mean

  • Must do: a legal requirement that applies to the build you described.
  • Recommended: good practice, or something the law requires only in some situations.
  • Get specialist help: too serious or nuanced for a quick check. We tell you why, and stop short of telling you what to do. Get advice before going live.

Where the law is unsettled, or depends on facts a few questions can't capture, we say "Get specialist help" rather than guess.

What Nomkora isn't

  • It isn't legal advice. It's guidance based on the answers you give. If your answers are incomplete, the checklist will be too.
  • It doesn't tell you a build is compliant. It tells you what the law asks, so you can do it or get help.
  • It doesn't check your build. It doesn't look at your site, code or data, and it only knows what you tell it.
  • It doesn't use AI to answer you. No chatbot is writing your checklist.

Found a mistake?

If you think a rule is wrong, out of date or missing something, email hello@pmproductsolutions.co.uk with the rule's title and what you think should change. We check every report against the official text and, if it's right, fix the rule and list the fix on What's changed.