Cookie Policy Generator UK
A cookie policy that lists the cookies you really set.
Paste your website. We load it in a real browser, click Accept on your cookie banner and record every cookie that lands: its name, who sets it and how long it lasts. You check the categories and purposes, and the PECR cookie policy writes itself. Free, no signup.
Step 1 — scan
The policy
Scan your site above to fill the cookie table from what it actually sets. Without a scan, the policy lists only the cookies of the services you tick.
№ 01 — Your business
Who the policy speaks for.
Most UK businesses processing personal data must register with the ICO — check at ico.org.uk.
№ 02 — Services the scan may have missed
The scan loads one page. Tick services that set cookies elsewhere (checkout, account pages); their cookies are merged with the scanned ones, marked as typical rather than measured.
Your cookie policy
How it works
Measured,
not assumed
Most cookie policy generators ask which tools you use and print a list of the cookies those tools usually set. That list drifts from the truth the day someone adds a plugin. This one reads the cookies off your live site.
- № 01
Load and accept
We open your page in a real Chrome browser, note the cookies set before anyone clicks, then find your cookie banner and click its Accept button. A cookie policy has to cover everything a visitor can end up with, which is the accept path.
- № 02
Classify
Each cookie name is checked against our rules for known analytics, advertising and essential cookies. Names the rules don't know get a best guess, clearly labelled, and anything still unknown is left unclassified for you to decide. Third-party cookies are filed as marketing and flagged for you to check.
- № 03
Write the policy
Your checked list becomes a UK cookie policy grouped as strictly necessary, preferences, analytics and marketing, with each cookie's provider, purpose and measured lifetime, and the date of the scan it came from. Copy it as Markdown or HTML, or download it.
FAQ
Common
questions
- Q1
Do I need a cookie policy in the UK?
If your site sets cookies, yes in practice. PECR requires you to tell visitors clearly what cookies you use and why, and to get consent for any that are not strictly necessary. A cookie policy listing each cookie, its purpose and its lifetime is how most sites meet the "clear and comprehensive information" part.
- Q2
Why scan instead of ticking the tools I use?
Because tools set cookies you did not know about, and plugins add more. A list built from what your live site sets after a visitor accepts is accurate on the day of the scan. Tick-box generators print what a tool usually sets, which may not be what yours sets.
- Q3
Do preference cookies need consent?
Usually, yes. PECR exempts only cookies that are strictly necessary for a service the visitor asked for. A cookie that remembers a language or layout choice the visitor made can fall within that; one set by default "for a better experience" needs consent like analytics does.
- Q4
What does "unclassified" mean?
The scan could not establish what the cookie is for: the name matches none of our rules and could not be identified. We never guess these into a category. Find out what sets it (your developer or the plugin list will know), then pick a category and describe the purpose.
- Q5
How often should I regenerate it?
Whenever you add, remove or reconfigure a tool on your site: a new analytics tag, a chat widget, an embedded video, a marketing pixel. The policy states the scan date, so it is easy to see when it was last checked.