Skip to content
Start free Sign in

Cookie policy generator

A policy that matches your site.

Kukie.io turns your answers to guided questions into a cookie policy and fills its cookie tables from your latest scan, so the policy lists the cookies your site sets.

Start free (opens in a new tab) Scan your website

Watch the explainer

From your scan to a published policy.

See how each wizard builds a document from your site, where it goes live and how you know when it falls behind.

1 minute 57 seconds, narrated, with captions in the player. The sites and rules in it are examples.

Read the transcript
  1. 0:00 Most cookie policies describe another website. Copied from a template, with the name changed at the top, they list cookies the site never sets, and miss the ones it does.
  2. 0:10 Kukie.io builds yours from your own site. Answer guided questions, and the cookie tables fill in from your latest scan: every cookie, its provider, purpose and lifetime.
  3. 0:22 Every plan gets a cookie policy and a privacy policy, in English or Brazilian Portuguese, and terms and conditions. Plus an accessibility statement, with the accessibility widget.
  4. 0:34 Every wizard starts with where your visitors are. Pick your regions, and the rights sections follow from them. Questions that don't apply are skipped.
  5. 0:42 Anything Kukie.io already knows arrives filled in: your organisation, your web address, the longest cookie lifetime, and the services the scan found. Change any of it.
  6. 0:53 Some sections are never asked. How your site answers privacy signals, like Global Privacy Control, is read from your banner settings. And when Google Consent Mode is on, the cookie policy explains it.
  7. 1:06 The last step is the whole document. Save a draft for review, or publish, after confirming it isn't legal advice. That confirmation is time-stamped and kept.
  8. 1:16 It goes live at its own address, and your banner links to it. Link it from your footer, or embed it with one line. One update reaches them all.
  9. 1:25 Then your site changes. When a scan finds a new cookie, the document is marked: needs updating. Reopen it, and publish again. Nothing is rewritten behind your back.
  10. 1:36 Policy alignment checks your privacy policy against the scan, and names any provider the scan found that your policy leaves out.
  11. 1:44 It's a draft, not legal advice, so have a lawyer review every document. But it's a draft about your site, not someone else's.
  12. 1:51 Kukie.io. A policy that matches your site.

Why it matters

Most cookie policies describe another website.

Many cookie policies started as a template copied from a similar company, with the name changed at the top. They list cookies the site never set and miss the ones it does.

A cookie policy is one of the few claims a stranger can check. Anyone can open your site, look at what it stores and compare that with your policy. When they disagree, the disagreement is the finding.

  • Describes another site

    A copied template

    • Lists the cookie table of the site it was copied from, on the day it was copied.
    • Contradicts your banner, which offers categories the policy never mentions.
    • Falls behind without warning, because nothing compares it with your site.
    • Writing one by hand instead means listing every cookie by name, provider, purpose and duration, a list few site owners have.
  • Describes your site

    A policy generated from your data

    • The cookie tables come from your latest scan, so they name the cookies a browser receives.
    • The sections are the ones your answers call for. Sections that do not apply are left out.
    • A rescan refreshes the list behind it, and the document is marked when your site has changed since you published it.
    • You start from a filled-in draft and correct it, which is a different task from starting from nothing.

What you get

A draft for review, not legal advice.

A generator assembles a document from your answers. It does not know your business, has not read your contracts and cannot judge whether your site meets a law.

It is

  • A drafting tool that gets you from nothing to a structured document about your site in one sitting.
  • A far cheaper thing to put in front of a lawyer than a blank page.
  • An accurate record of the technical facts, because the cookie detail comes from a scan, not from memory.

It is not

  • Legal advice, or a substitute for a qualified legal professional who knows your organisation.
  • Approved or certified by any regulator. No generator is, whatever its landing page implies.
  • A verdict on your site. Publishing a policy proves you published a policy, and nothing more.
  1. 1. Every generated document opens with this notice.
  2. 2. Publishing asks you to acknowledge it first.
  3. 3. The acknowledgement is time-stamped and kept with the document.

The documents

One generator for each document.

Kukie.io generates a cookie policy, a privacy policy and terms and conditions on every plan, and an accessibility statement on the Agency and Unlimited plans. Each has its own wizard and is published on its own.

The Kukie.io legal document generators: what each covers, what is filled in for you and when to generate it again
Document What it covers What is filled in for you When to generate it again
Cookie policy What your site stores on a visitor's device, why, for how long, and how someone changes their mind later The cookie tables, grouped by category, from your latest scan: name, provider, purpose and duration. Also your web address, the services the scan identified and the longest cookie lifetime it found After a scan finds cookies you have not seen before, and whenever you add or remove a tool
Privacy policy What personal data you collect, why you hold it, who you share it with, how long you keep it and what rights visitors have Your organisation name and web address, whether your site uses cookies at all, and the kinds of third party your detected cookies point to, such as analytics or payments When you change what you collect, bring in a new processor or start serving a new region
Terms and conditions The rules for using your site: accounts, acceptable use, user content, payments and refunds, liability and governing law Your web address, with the rest set by what you tell the wizard about accounts, paid features and how disputes are settled When your commercial terms change, such as a new refund period or a change of jurisdiction
Accessibility statement The accessibility standard your site aims for, its known limitations and how visitors can report a barrier Your organisation name and web address, and a section on the accessibility widget when it runs on your site When you fix a known limitation or find a new one

Most sites need the cookie policy and the privacy policy. Terms matter once you sell something, host accounts or accept content that visitors upload. The cookie policy is the usual one to do first, because it describes the cookies your banner asks about.

Where the answers come from

Questions arrive with answers filled in.

A blank page is why most policies get copied. Every question Kukie.io can answer from what it already knows arrives with that answer in the box, and you accept it or change it.

The scan supplies the facts

The part of a cookie policy nobody can write from memory is the cookie table, so Kukie.io does not ask you to. Your latest cookie scan holds every cookie found on your site with its provider, its purpose and how long it lasts, sorted into the categories your banner uses. Where you have not written a purpose yourself, it comes from the cookie database, when there is a match.

Your answers decide which sections exist

The wizards are conditional. Each one starts by asking where your visitors are, from 12 regions, and the rights sections that follow are the ones those regions call for. Say no to international data transfers and you are not asked which safeguards you rely on. The privacy policy builds up to 17 sections, 8 of them conditional.

Defaults you can see and change

Every default is visible in its field, marked when it came from your site, and you can change it before you move on. The services the scan recognised are pre-ticked in the third-party question. You also see the finished document in full before it goes anywhere, which is where most people spot the one answer they got wrong.

Publishing

The document goes live at its own address.

The document does not arrive as a file you then have to find a home for. Kukie.io publishes it at its own address, and you link to that address wherever the document needs to appear.

  1. Step 1: Answer the questions

    The wizard moves one section at a time. Questions that no longer apply are skipped, not greyed out, so the run is as short as your answers allow.

  2. Step 2: Read the whole document

    The last step is the finished document in full, cookie tables and all. Change an answer and it is rebuilt. This is the version to send to whoever reviews it.

  3. Step 3: Save a draft, or publish

    A draft is private and keeps your answers while a review is outstanding. Publishing asks you to acknowledge that the document is not legal advice, and only then makes it public.

  4. Step 4: Link your site to it

    The policy links in your banner point to it, unless you typed another address for them. Link it from your footer too, or embed it in a page of your own. Publishing an update refreshes every place it appears.

The published address

app.kukie.io/legal/<your site key>/cookie-policy

The same pattern gives you privacy-policy and terms-conditions. Nothing has to be pasted into your content management system, so nothing has to be pasted in again the next time the document changes.

Or inside your own layout

<iframe src="https://app.kukie.io/legal/<your site key>/cookie-policy" title="Cookie Policy" width="100%" height="600"></iframe>

Copy Embed gives you this one line for a page of your own. Copy HTML gives you the document itself, to paste where an embed is not allowed.

Keeping it current

You see when the document falls behind.

Sites change after a policy is published: a new chat widget, a campaign pixel, a tool removed. Kukie.io notices the change and tells you. It never rewrites a published document behind your back.

Your privacy policy, checked against your scan.

The Policy alignment card on the Legal Documents page compares the third-party providers your latest scan detected with the ones your published privacy policy mentions. A provider found on your site and missing from the policy is listed by name, with its category and the cookie or host that gave it away.

It works the other way too: a provider the policy mentions that the scan did not see is listed as possibly unused. A scan covers only the pages it visited, so that list is for information, and the check never states a legal conclusion.

When it matters most

Where a generator helps most.

Any site with a cookie banner needs a document behind it. These are the situations where generating one beats the alternatives.

  • Your first scan found more than you expected

    A site picks up cookies from a chat widget, an embedded video and an old campaign pixel, and nobody has the full list. Generating the policy from the scan turns that list into something a visitor can read.

    Learn more about the cookie scanner

  • Your visitors are in several jurisdictions

    A visitor in the EU has different rights from a visitor in California, and a policy that describes only one is incomplete for the other. Tell the wizard where your visitors are, and the matching rights sections are written in.

    Learn more about geo-targeting

  • Legal budget is the constraint

    Review costs less than drafting. Arriving with a complete document, an accurate cookie table and a list of the decisions you have already made changes what you are paying a lawyer for.

  • You maintain sites for other people

    Every site gets its own documents, generated from its own scan and published at its own address. Handing a site over means handing over stored answers, not a paragraph someone wrote once.

    Learn more about Kukie.io for agencies

The cookie policy, privacy policy and terms generators are on every plan, and every site you add gets its own set.

Learn more about privacy laws by region

Questions about the cookie policy generator

Generate a cookie policy for your site.

Scan the site, answer the questions and publish. Each site you add gets its own documents, each at its own address.

Start free (opens in a new tab) See pricing

Features this one relies on

A generated policy is only as good as the data behind it, and only useful if something links to it.

See all features

More on policies and what belongs in them

Background reading on what a cookie policy, a privacy policy and a set of terms are each expected to say.

See all articles

Disclaimer

Kukie.io provides tools to collect and record consent. It is not legal advice, and using it does not by itself make a website compliant with any law.

Listed on

Kukie.io on Trustpilot (opens in a new tab) Kukie.io on G2 (opens in a new tab) Kukie.io on SaaSHub (opens in a new tab) Kukie.io on AlternativeTo (opens in a new tab)