Cookie policy generator · Pro and up
A cookie policy written from what we watched your site do.
Most cookie policies come from a form you filled in once. This one comes from a real browser that visited your pages twice — before consent and after it — and wrote down what loaded, what was set, and when. You publish the result in your own name.
Three dates, never one
Every generated policy prints all three, because the day it was written and the day your site was watched are rarely the same day.
- Effective:
- March 3, 2026
- Website last scanned:
- February 27, 2026
- Policy last generated:
- March 3, 2026
Behavior is attributed to the scan date or to nothing at all. No regeneration can pass itself off as a fresh look at your site.
IllustrationSample site, sample dates.
Cookie Policy
example.com · Operated by Example Media LLC
- Effective:
- March 3, 2026
- Website last scanned:
- February 27, 2026
- Policy last generated:
- March 3, 2026
This policy was generated from an automated scan of this website on February 27, 2026 (48 pages, observed in a real browser before and after consent). Site technologies may change between scans.
Cookies on this site
| Cookie | Duration | Consent behavior |
|---|---|---|
| _ga | About 13 months | Set only after consent |
| _fbp | Persistent | Set only after consent |
| _clsk | Session | Set only after consent |
| ep_session_id | Session | Present before consent |
| __cf_bm | About 30 minutes | Set when a consent choice is recorded |
Durations are the lifetimes observed in the browser during the scan, where recorded. Browser privacy settings, site configuration, or withdrawing consent can shorten them.
Reading the tables
- Present before consent
- The cookie was already in the browser before any consent choice had been made.
- Set only after consent
- The cookie appeared only after the scan accepted every category; it is not set until you allow the category it belongs to.
- Set when a consent choice is recorded
- The cookie is set by the service that stores your consent choice, at the moment you make one — not before.
IllustrationThe generator's own wording and duration vocabulary. Sample site, sample dates.
Why a questionnaire gets this wrong
You cannot list what you do not know about
Tags arrive through plugins, theme updates, embedded media and marketing integrations that nobody wrote down. A scan finds them because it watches the network, not the documentation.
The interesting column is timing
Listing a cookie is easy. Saying whether it appeared before anyone chose anything needs two visits to the same pages, which is what the scan does.
It goes stale the week you publish it
Your site keeps changing. Scans are scheduled, so the next one sees what changed — and the document always prints the date the behavior in it was observed.
What is in the document
Seven sections, in this order. Sections with nothing to report are left out rather than printed empty.
- 01
What cookies are
Plain-language preamble, including the local storage, pixels and scripts a cookie-only policy misses.
- 02
How consent works on this site
Written to match your site's actual posture — hold-until-consent or opt-out — and it states what a Global Privacy Control signal does here.
- 03
Reading the tables
Defines each consent-behavior label as something a scan observed, never as a promise. Only the labels your policy uses are defined.
- 04
Services that use cookies or similar technologies
One table per category, naming each service, its provider, and what data moves.
- 05
Cookies on this site
Every cookie the scan saw: name, domain, party, category, service, observed duration, and whether it appeared before or only after consent.
- 06
Other third-party services
Hosts the scan reached that the catalog does not recognize, listed rather than quietly dropped.
- 07
Managing cookies
How a visitor changes their mind, and what withdrawing consent does and does not reach.
The byline names the operator you set per site — name, privacy contact and privacy-policy link. Leave it unset and the policy still generates, named after your organization instead; if you manage sites for clients, that is your agency's name on your client's document, so the dashboard warns you rather than blocking the generate button.
What it will not say
This is a document you publish in your own voice, so every sentence in it is a claim we wrote for you. These are the rules it follows.
Three dates, never one
Effective, website last scanned, policy last generated. Regenerating without a new scan is normal, and the document will not let that pass as a fresh observation — behavior is attributed to the scan date or to nothing.
Durations are observed, not looked up
A Google Analytics cookie documented as lasting two years reads “About 13 months,” because Chrome caps every cookie at 400 days and that is what your visitor receives. A cookie whose expiry was not recorded reads “Persistent” — never a number we did not see.
A description says what data moves
Never whether that needs consent. Three catalog entries once drew a legal conclusion in the customer's own voice; they were rewritten, and a test now refuses the old wording. Your counsel concludes; the document describes.
Unrecognized means unrecognized
A cookie we cannot match to a known service says so, rather than being given a plausible purpose or left blank — which in a published disclosure reads as nothing to disclose. When you see one, tell us and it becomes a catalog entry.
Our own cookie is in your policy
Cloudflare sets __cf_bm when a browser contacts Consentinel's infrastructure. It is excluded from your scan results, because that is our conduct and not your site's — and it is disclosed in your policy, because your visitor's browser really does receive it.
It is addressed to your visitors
No template hedging, no instructions to you, no “consult your attorney” in the middle of a public document. The notes meant for you stay in the dashboard where you generate it.
You reference it. You never paste it.
Copying HTML into a page editor failed in the field: Wix rejects it, WordPress builders reflow it, and every regeneration meant editing every site again — so the published copy drifted from the generated one with nothing noticing. Consentinel hosts the document and you point at it.
Generated
Cookie policy, version 3
From the scan of February 27, 2026. Earlier versions are kept.
/policy/example.com/cookies
A complete page, in your banner's colors. Link it from your footer.
cookies.js
Writes the policy into a div on a page you already have, in your own fonts.
[consentinel_cookie_policy]
WordPress shortcode. Fetches server-side and keeps a local copy.
IllustrationNothing is pasted. Regenerate once and every reference follows.
Regenerate once and every reference updates within a minute. The hosted page takes its colors from your banner, so it looks like the rest of your site without you styling anything.
A published policy does not disappear if your plan lapses. Generating a new version needs Pro and up; serving the latest version you already generated does not. A legal document vanishing from a customer's website over a card that expired is the worse failure, so it does not happen.
On WordPress it is a shortcode. [consentinel_cookie_policy] fetches the document on the server, keeps a local copy, and refreshes on a schedule — so your visitors never wait on us, and a bad day at our end leaves the last good copy in place.
Worth knowing first
- It describes a scan, not a guarantee. The document says what a browser saw on a given date. Add a plugin next week and the policy is behind until the next scan runs.
- It lists the durations the scan recorded. Not every cookie yields one, and the ones that do are what a real browser was given — which is often shorter than the vendor's own documentation claims.
- Generating needs a paid plan: Pro and up. Free accounts get the banner, the blocking and the scan verdict. The generated policy is one of the four things paid plans add.
See what your site is doing first. The policy writes itself from that.
What a scan can observe depends on where your platform lets our script run, so read this alongside each platform's external exposure. A generated cookie policy is a factual description of observed behavior, not a legal opinion about it — Consentinel is compliance tooling, not legal advice.