Consentdeck

Article 7 (1) GDPR requires consent to be demonstrable. Most banners only keep the latest state in the visitor’s browser — clear that storage and the evidence is gone. Consentdeck writes every decision into a log instead: with consent ID, settings version, chosen categories and services, language, banner presentation and an HMAC over exactly those details. In the admin you recompute the checksum against the stored entry — valid or not, no argument.

Nothing loads before the decision. Third-party scripts, embeds and tracking pixels are held back until the matching category is allowed — including those another plug-in only writes into the page at runtime. For maps and videos a placeholder with a load button appears in their place. For measurement and advertising there is Google Consent Mode v2: every signal sits at denied before the first tag and is updated after the decision. For Tag Manager, Consentdeck generates a ready-made container with variables, triggers and tags plus documentation — import it once and you are done.

Which services a website really loads is what the cookie scanner finds out: it fetches the pages, matches the findings against a signature database of known providers and runs on a schedule if you want. Known services are adopted with one click, and the cookie declaration is generated from the maintained configuration automatically — a block on the page that never goes stale.

The banner ships with five themes and a dark mode, plus dimming, blur and a scroll lock as needed. It is installed through a plug-in for WordPress, TYPO3, Shopware and Joomla — or as a single embed script on any other website. Operations and the log stay in Germany. Two things are deliberately missing: A/B tests on the banner (optimising for the approval rate is nudging) and TCF 2.2 (only websites with ad networks need it).