Account

What new tool do you want?

Legal & Compliance

Cookie Policy Generator

Create a cookie policy listing the cookies your site uses — necessary, preferences, analytics and marketing — with how to manage consent, as required by the GDPR, UK PECR and the EU ePrivacy Directive.

For general information only — not legal advice. Laws vary by location; consult a qualified lawyer.

How to use

  1. 1Enter your site details.
  2. 2List the cookies you use (name, provider, purpose, duration, type).
  3. 3Download the policy and link it from your cookie banner.

Frequently asked questions

Is this cookie policy legally binding?

A document like this is binding when the parties agree to it (and sign where required). Whether each clause is enforceable depends on your local law, so have important agreements reviewed by a lawyer.

Do I need consent for cookies?

In the UK and EU, yes — for every cookie that isn't strictly necessary (analytics, advertising, most embeds). Necessary cookies (like a shopping basket) don't need consent but must be disclosed.

How do I find which cookies my site uses?

Use our Cookie Scanner tool, or your browser's developer tools (Application → Cookies), after accepting all cookies.

Is my information stored?

No. The document is generated in your browser and nothing you type is sent to our servers.

Why cookies are grouped by category, not listed as one list

The generator sorts each cookie you list into necessary, preferences, analytics or marketing because UK PECR and the EU ePrivacy Directive treat those categories completely differently — necessary cookies need no consent at all, while every other category needs an opt-in before the cookie is allowed to be set. Grouping the output this way mirrors how a consent banner has to behave, and makes it obvious at a glance which cookies are running unconditionally versus which require a visitor's prior choice.

Worked example: Cookie Policy Generator

Using the default cookie list — session_id and cookie_consent marked necessary, _ga from Google Analytics marked analytics, and _fbp from Meta marked marketing — the generated policy produces a 'Strictly necessary cookies (no consent needed)' section listing the first two, and separate 'Analytics cookies (only with your consent)' and 'Marketing cookies (only with your consent)' sections for _ga and _fbp, each showing the provider, purpose and expiry you entered (2 years for _ga, 3 months for _fbp). Add a new row to the textarea for a live-chat widget cookie marked 'preferences' and a fourth heading appears automatically — the policy structure is generated entirely from however you've categorized your own rows.

Why the cookie list has to come from an actual audit

This tool formats whatever cookies you type in — it doesn't scan your site to find them, so the accuracy of the published policy depends entirely on you knowing what's actually set. A mismatch (claiming only four cookies when a third-party embed quietly drops a dozen more) is the kind of gap regulators and privacy-conscious users do check for. Running a cookie scanner against your live site before filling in this form, rather than guessing from memory, is the difference between a policy that matches reality and one that doesn't.

A type the policy does not recognize is dropped

The type column is matched from the start of the word, ignoring capitals, so Necessary and necessary cookies both land under strictly necessary. A type that does not start with necessary, preferences, analytics, or marketing is left out, and that row never appears. A category with no rows does not get a heading, so an empty preferences group adds nothing. If the expiry column is blank, the line says expires with a dash rather than inventing a duration. A row needs the vertical bars between name, provider, purpose, duration, and type; a missing piece is shown as blank rather than shifting the later columns into the wrong slot only when the bars are still there. The date under the title is the day you generate the policy, and the contact line uses the email box.

Related tools

More: Legal & Compliance