Consent experience

A cookie policy generator
that already knows your cookies

A cookie policy generator turns a set of guided questions into a finished document. Kukie generates three: a cookie policy, a privacy policy and terms and conditions. The cookie tables are filled in from your most recent scan, so the policy lists the cookies your site actually sets. Each one publishes at its own URL.

What it produces is a starting point for review, not legal advice. Kukie says so on the face of every document, and this page says so before it says anything else.

Start free → Find your cookies first

Why the cookie policy on most websites does not describe that website

Almost every cookie policy on the internet arrived the same way. Somebody found a template, or copied one from a company that looked similar, changed the name at the top and pasted it into a page. The result names cookies the site has never set, omits the three it does set, and gives durations nobody measured. It is a document about a hypothetical website.

That is a problem because a cookie policy is one of the few compliance claims a stranger can check. Anyone can open your site, look at what it stores, and compare that with what your policy says. When the two disagree, the disagreement is the finding.

The copied template

Written about somebody else's site

Lists a cookie table that was true for the site it was copied from, on the day it was copied.
Contradicts your banner, which offers categories the policy never mentions.
Ages quietly. Nothing tells you it has drifted, because nothing is comparing it to anything.
The alternative, writing it by hand, means listing every cookie by name, provider, purpose and duration. Very few site owners have that list.

Generated from your own data

Written about the site it is published on

The cookie tables come from your most recent scan, so they name the cookies a browser really receives.
The sections that appear are the ones your answers called for, and the ones that do not apply are simply absent.
A rescan refreshes the underlying list, so you can see when the document has fallen behind the site.
You start from a filled-in draft and correct it, which is a different task from starting from nothing.

What a generated document is, and what it is not

This belongs near the top of the page rather than in a footnote, because getting it wrong is expensive and because a tool that oversells itself here is not a tool you should trust with the rest. A generator assembles a document from your answers. It does not know your business, it has not read your contracts, and it cannot tell you whether your site is compliant.

It is

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

It is not

Legal advice, and it is not a substitute for a qualified legal professional who knows your organisation.
Approved, certified or blessed by any regulator. No generator on the market is, whatever its landing page implies.
A verdict on your compliance. Publishing a policy proves you published a policy, and nothing more than that.

This is built into the product, not just written on this page. Every document Kukie generates carries a notice at the top stating that it was produced automatically, that it does not constitute legal advice, and that it should be reviewed by a qualified legal professional. Publishing one requires you to tick an acknowledgement saying you have read that, and the acknowledgement is time-stamped and kept with the document. Kukie provides the technical infrastructure for cookie consent management; whether your site is compliant depends on how you configure it and may require additional legal measures specific to your organisation.

Which document covers what?

Three generators, three separate wizards, one site. Most sites need the first two. The third matters once you sell something, host accounts or accept anything a visitor uploads.

The three Kukie legal document generators, what each covers, what is filled in automatically and when to regenerate
Document	What it covers	What gets filled in for you	When to regenerate
Cookie Policy	What your site stores on a visitor's device, why, for how long, and how somebody changes their mind later	The cookie tables, grouped by category, from your most recent 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 turns up 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 categories of third party your detected cookies point at, such as analytics or payments	When you change what you collect, bring in a new processor, or start serving a region you did not before
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 driven by what you tell the wizard about accounts, paid features and how disputes should be settled	When your commercial terms move, for example a new refund period or a change of jurisdiction

Each document is generated, saved and published on its own. Doing the cookie policy first is the usual order, because it is the one your banner links to.

Where the answers come from

A blank page is the reason most policies get copied. The wizards are built the other way round: every question that can be answered from something Kukie already knows arrives with that answer in the box, and you either 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 does not ask you to. Your most recent cookie scan already holds every cookie found on your site with its provider, its purpose and how long it lasts, sorted into the categories your banner uses. Those rows go straight into the document, grouped exactly as a reader would expect to find them. The services the scan recognised are pre-ticked in the third-party question, and the longest cookie lifetime it saw is offered as the default duration.

Your answers decide which sections exist

The wizards are conditional rather than fixed. Say that GDPR applies and the cookie policy grows the rights section that goes with it; say it does not and that section is never written. Answer no to international data transfers and you are not asked which safeguards you rely on, because the question no longer has a point. The privacy policy wizard is the deepest of the three: it covers GDPR, CCPA, UK GDPR, PIPEDA and POPIA, and has 15 conditional sections that appear or disappear as you answer.

Sensible defaults, not silent ones

Defaults are visible in the field, on the step where they matter, and every one of them can be overruled before you move on. Nothing is decided for you behind a screen you never see. You are also shown the finished document in full before it goes anywhere, which is the point at which most people spot the one answer they got wrong.

A cookie table row

Name: The cookie exactly as it appears in the browser.
Provider: Who set it, or first party when it is your own.
Purpose: A plain description, matched against the 3,400+ entries in the cookie database where there is one.
Duration: How long it stays, or session when it goes with the tab.

From the first question to a page you can link to

The document does not arrive as a file you then have to find a home for. It is published by Kukie at its own address, and you point at that address from wherever the document needs to appear.

Pick a document and answer the questions

The wizard moves one section at a time and tells you which step you are on. Questions that no longer apply are skipped rather than shown greyed out, so the run is as short as your answers allow.
Read the whole thing before anyone else does

The last step is the finished document, rendered in full, cookie tables and all. Go back a step, change an answer, and it is rebuilt. This is the version to send to whoever reviews it for you.
Save it as a draft, or publish it

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

Link the published address from your footer and from the policy link in your consent banner, or copy a one line snippet that embeds the document inside a page of your own. Republishing an updated version refreshes every place it is used.

What the published address looks like

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, which means nothing has to be pasted in again the next time the document changes. If you would rather serve it inside your own layout, the raw HTML can be copied out in one click and dropped into a page you control.

When a generator earns its keep

Any site with a cookie banner needs a document behind it. These are the situations where generating one beats every other option available to you.

Your first scan found more than you expected

This is the common one. 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 is the fastest way to turn that list into something a visitor can read.

Your visitors are in several jurisdictions

The rights an EU visitor has are not the rights a Californian visitor has, and a policy that describes only one of them is incomplete for the other. Tell the wizard which regimes you have decided apply, and the matching sections are written in. Which banner each region sees is a separate setting, covered on geo-targeting.

Legal budget is the constraint

Review is cheaper 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 buying from a lawyer, and it is the difference between an afternoon and a project for most small organisations.

You maintain sites for other people

Every site gets its own documents, generated from its own scan, published at its own address. Nobody has to remember which client got which template, and handing a site over means handing over answers that are still stored, not a paragraph somebody wrote once.

The three generators are part of every plan, free included, and every site you add gets its own set. Compare plans if you need more sites or more scanned pages, or read the global compliance overview if you are still working out which regimes apply to you.

Features this one leans on

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

Cookie scanner

Find every cookie automatically

Geo-targeting

The right banner in every region

Cookie banner

Layouts, categories and consent modes

See the full feature set

Cookie policy generator questions

What site owners ask before they generate a document, and what they ask again when the site changes.

What is a cookie policy generator?

It is a tool that turns a set of guided questions into a finished cookie policy, instead of leaving you with a blank page or a template written for somebody else. Kukie asks who you are, which privacy laws you have decided apply to you and how long your cookies last, then assembles the document. The cookie tables inside it are filled in from your most recent scan of your own site.

Is a generated cookie policy legally valid?

A generator produces a draft, not a legal opinion, and no software can tell you that your particular site is compliant. Kukie states this on the face of every document it produces and asks you to acknowledge it before you publish. The sensible way to use the output is as a reviewable starting point that a qualified legal professional can check, which is faster and cheaper for them than writing one from nothing.

Do I need a cookie policy if I already have a cookie banner?

They do different jobs. The banner asks for permission in a sentence or two. The policy is the fuller explanation it links to: which cookies your site sets, who provides them, what they are for and how long they stay. Regulators generally expect a banner to point at a document of that kind, and a visitor who wants the detail has nowhere else to find it.

Where does the cookie policy live once it is generated?

Each published document gets its own public address on Kukie, ending in cookie-policy, privacy-policy or terms-conditions. You can link straight to it from your footer and from the banner, or paste a one line snippet that embeds it inside a page on your own site. Nothing has to be copied into your content management system, and updating the document updates every place it appears.

Does the policy update itself when my cookies change?

The scan data updates on its own, the published document does not. A rescan refreshes the list of cookies and services Kukie holds for your site, and reopening the generator pulls that newer list into the tables. You then republish, which is one click. This is deliberate: a live legal document that silently rewrote itself between visits would be impossible to keep a record of.

What is the difference between the cookie policy and privacy policy generators?

The cookie policy covers what your site stores on a visitor device and why. The privacy policy is broader: what personal data you collect, who you share it with and what rights people have over it. They are separate wizards because they ask different things. The privacy policy wizard covers GDPR, CCPA, UK GDPR, PIPEDA and POPIA, and has 15 conditional sections that appear or disappear depending on your answers.

Generate a cookie policy that matches your site

Free plan, no card required. Scan the site, answer the questions, publish the document.

Start Free → View pricing

A cookie policy generator
that already knows your cookies