Cookie banner
Cookie banner overview
How the Privacyboard cookie banner works: it asks first, blocks known trackers until consent, supports Google Consent Mode v2 and keeps a log of every choice. Part of the Pro plan.
The Privacyboard cookie banner asks visitors for consent before non-essential cookies and trackers run, holds back known analytics and marketing tools until the visitor agrees, and records every choice. It is installed with one line of code and managed from your workspace.
#What it does
- Asks first. Equal Accept all and Reject all buttons. Closing the banner without choosing is not counted as consent.
- Blocks known trackers. Scripts, frames, pixels and requests from known tools wait for the visitor's answer. See Blocking before consent.
- Signals Google. Google Consent Mode v2 starts as denied and updates with the choice. See Google Consent Mode.
- Removes cookies on refusal. Cookies of well-known tools are removed when a category is refused or withdrawn.
- Speaks five languages. English, French, German, Spanish and Italian, chosen from the visitor's browser.
- Keeps the proof. A log of choices without IP address, kept for 13 months. See Consent log.
- Writes your cookie declaration. The services you list become your cookie policy and the cookie section of your privacy policy.
- Checks your site. A scan and a real-browser check show what your pages load and when. See Site check.
#How it works
- You list the services your website uses and give each one a category: necessary, preferences, statistics or marketing.
- You choose the look and texts of the banner and publish it.
- You add one script line to your pages.
- A visitor opens your site. The banner script loads its settings, shows the banner and holds back the tools of categories not yet accepted.
- The visitor chooses. The choice is saved in a first-party cookie named
pb_consenton your site, applied to blocked tools and logged.
#Plans
Setting up and previewing the banner are free. Publishing it on your website, the site check and the consent log are part of Pro.
#What it is not
The banner helps you meet the ePrivacy and GDPR rules on consent, but compliance also depends on what your site actually loads. It is not a Google-certified CMP and does not implement the IAB TCF framework. See Limits.
#FAQ
#Does this make my website GDPR compliant?
No tool can promise that. The banner asks for consent, blocks the services it knows and keeps a log. What your site loads, and what your declaration says, remains your responsibility, and the site check helps you verify it.
#What does a cookie banner have to do?
Cookies and similar technologies that are not strictly necessary generally need consent before they are set or read. Consent must be freely given, specific, informed and unambiguous, you must be able to demonstrate it, and withdrawing must be as easy as giving it.
#Does it work with my website builder?
Yes. It is one script line, with guides for Webflow, Google Tag Manager, Shopify and WordPress. Any site that lets you edit the head can use it.
#Does the banner slow my site down?
It is one small script, loaded early so it can hold back other tools. Its size is small compared with the tools it manages.
Privacyboard is a guidance tool, not legal advice. This page describes what the product does today. Found something unclear or out of date? Write to antoine@unmake.io.