As of 13 August 2026, AI can only partly check your cookie banner for UK compliance.

What to actually do

1. Hand it to a person

   The route this page recommends

   Someone with a licence or accountable authority has to sign this before it counts.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, chat-fluent skill, and roughly 1 hour until you can act on the result.

   How to actually do it

   1. Open the live website in a private browser window and save screenshots of the first cookie banner, its settings panel, its refusal path and its withdrawal control.
   2. Open the browser developer tools and record which cookies, local-storage items, pixels and network requests appear before consent, after refusal and after each consent category is accepted.
   3. Export the consent-management-platform configuration and cookie scan, including purposes, vendors, durations, default states, consent records and withdrawal settings.
   4. Gather the linked cookie notice and privacy notice, then paste the banner text, screenshots, configuration, scan and site context into the prompt.
   5. Ask the model to produce the evidence-based issue list, source citations, missing-evidence list and prioritised corrections without filling gaps from assumptions.
   6. Compare each cited requirement with the current ICO guidance, rerun the browser tests after changes and send unresolved or high-risk findings to your solicitor or data protection specialist before publishing.

   Prompt

   Review the following cookie banner and consent implementation for a UK website against the UK GDPR and PECR, using current ICO guidance where available. This is a compliance review, not a declaration that the site is legally compliant.
   
   Website purpose and audience:
   [DESCRIBE THE WEBSITE, ITS USERS AND ANY AGE OR VULNERABLE-USER CONSIDERATIONS]
   
   Banner wording and screenshots:
   [PASTE THE FULL BANNER TEXT AND ATTACH SCREENSHOTS]
   
   Consent-management-platform settings:
   [PASTE THE RELEVANT SETTINGS, INCLUDING DEFAULTS, CATEGORIES, PURPOSES, VENDOR LISTS, WITHDRAWAL METHOD AND CONSENT-LOGGING DETAILS]
   
   Cookies and similar technologies found on the live site:
   [PASTE THE COOKIE SCAN OR BROWSER-DEVELOPER-TOOLS EXPORT, INCLUDING NAME, DOMAIN, PURPOSE, PROVIDER, DURATION AND WHETHER EACH ITEM LOADS BEFORE CONSENT]
   
   Privacy and cookie information linked from the banner:
   [PASTE THE RELEVANT TEXT OR LINKS]
   
   Review requirements:
   1. Separate strictly necessary technologies from non-essential analytics, advertising, personalisation and other technologies.
   2. Check whether non-essential technologies appear to be blocked until valid consent, whether consent is freely given and specific, and whether refusing or withdrawing consent is as easy as accepting it.
   3. Check the wording, button labels, category descriptions, purposes, vendor information, retention details and links for misleading or missing information.
   4. Identify evidence that is missing and state exactly what live-site test would establish it.
   5. For every finding, quote the relevant banner or implementation evidence, state the issue, explain the risk, and give a practical correction.
   6. Distinguish clear issues, likely issues and questions requiring a solicitor or data protection specialist. Do not invent facts, cookies, vendors, legal sources or test results.
   7. Cite the specific ICO guidance or other official UK source used for each legal conclusion, and say when a conclusion depends on facts that have not been supplied.
   8. End with a prioritised list of changes and a separate list of tests I must run before publishing.
   
   Do not call the banner compliant merely because the wording looks acceptable. Do not treat this review as professional advice.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.