Use TermsFeed Free Cookie Consent to follow the cookie consent rules of your site
By default, Cookie Consent holds the optional scripts you tag until the visitor agrees. That default behavior serves the part of the cookie consent rules that asks for consent before anything is stored on or read from the device. Find out which laws ask for a cookie consent banner, how visitors refuse as easily as they accept, and how to prove that a visitor consented. Then check what Google AdSense needs and what Cookie Consent leaves to you. Whether your site complies depends on the scripts you run and the visitors you serve.
Decide what the law asks of your site
Check which laws apply to your visitors, then keep the "I decline" button those laws expect on the consent banner.
| Page | What it answers |
|---|---|
| Do I Need a Cookie Banner? EU, UK, and US Rules | Which laws require consent, which cookies need none, and what Cookie Consent decides for you |
| Reject All Button and Cookie Walls | What "as easy" means, why a page-blocking layout with the "I decline" button is not a cookie wall, and how visitors withdraw |
Keep evidence of consent
Cookie Consent stores each answer in the browser only, so the evidence is yours to keep.
| Page | What it answers |
|---|---|
| Keep a Consent Log to Prove Consent | What Cookie Consent stores, what a consent record holds, and how to send one from a callback |
Know what Cookie Consent does not do
Some rules need features that Cookie Consent does not have. Find out which ones before you rely on Cookie Consent for advertising or for visitors outside the EU and the UK.
| Page | What it answers |
|---|---|
| Google AdSense and the IAB TCF | What tagging AdSense achieves, and the 2 options for Google ads in the EEA, the UK, and Switzerland |
| Limits of Free Cookie Consent: What It Does Not Do | Every limit of Cookie Consent, each with a workaround or an alternative |