How does the cookie policy generator work?
Give us your domain, that is it. Our scanner visits your website like a real visitor and records every cookie that gets set: first-party and third-party, session and persistent, analytics pixels and social embeds. Each cookie is matched against our database and enriched with provider, purpose, retention period and classification. The result is a cookie policy built from what actually runs on your site, not from a questionnaire.
What does your cookie policy include?
A complete cookie table listing, for every detected cookie: name, provider, classification (necessary, functional, analytics, marketing), purpose and retention period. Plus the explanatory text a cookie policy needs under the GDPR and ePrivacy rules: what cookies are, how visitors withdraw consent and how changes are communicated. Publish it via an auto-updating snippet or export it as a dated, versioned PDF.
Why a scan beats a template
Template generators ask which cookies you use, but most site owners honestly do not know. A tag manager, a chat widget or a YouTube embed can set a dozen cookies you never chose. A template policy that lists the wrong cookies is not just useless, it is proof that your disclosure does not match reality. We scan, so your policy describes what your website actually does. And when a later scan finds new cookies, your policy is updated along with them.
FAQ
Is the cookie policy generator free?
Yes. The website scan is free, no account or credit card needed. To generate, publish and export the full cookie policy you create a free GDPRWise account, which also keeps your policy current when your cookies change.
Which details does the generator list per cookie?
For every cookie: name, provider, classification, purpose and retention period. That is exactly the metadata regulators expect in a GDPR-compliant cookie policy.
Does my cookie policy stay up to date automatically?
Yes. GDPRWise rescans your website periodically. When new cookies, trackers or third parties appear, your dossier is updated and your published cookie policy is regenerated. If you use the embed snippet, the version on your site is always current.
Do I still need a cookie banner?
Yes, a cookie policy and a cookie banner solve different problems. The banner collects consent before non-essential cookies are set; the policy documents them. From your banner you can link straight to your always-current GDPRWise cookie policy.