Cookie Consent features

The page that leaves the server has them switched off for everybody; the browser puts back what this visitor agreed to. That order is what makes it work behind a cache, and it is what most consent banners do not do at all.

On a slow site it stops after 45 seconds and says how many pages it did not read, rather than running on until something gives up. Nobody knows off the top of their head which of their plugins loads a pixel; this is how you find out rather than guess.

Hold each one back until visitors agree to a kind of cookie, or leave it loading. Holding back a host holds back the script or the snippet the row was found in. Nothing is chosen for you, payment and spam-check scripts are marked as usually needed, and the dashboard does not say nothing is getting past until each one found has been looked at. A script that another script adds later without writing its address on the page, such as a tag from Google Tag Manager, is not listed.

Recognised by address and by the snippet's own contents, because half of them arrive inline. Anything else takes one line to add.

When something new has turned up, the Dashboard says what it found, with one button that adds it to the banner and the cookie list. It never changes the banner by itself: until you say so, a service it recognises, of a kind the banner does not ask about yet, is held back for everybody.

Held-back embeds keep the space they were holding and offer a button, so the article does not jump when one loads — and loading one video is about that video, not consent to everything of its kind for ever.

Belt as well as braces: the blocker stops the tag loading, and this covers a Google tag you have deliberately let through.

Only on pages that carry them, on every page, and again whenever the answer changes.

It is not adjustable, because nearly every enforcement action taken over a cookie banner anywhere has been about exactly this — and a plugin that made it a setting would be selling you a way to get fined.

Scrolling is not treated as agreement and the setting for it is off. A browser sending Global Privacy Control or Do Not Track has already answered, so it is not asked again and the refusal is what gets stored.

An update asks nobody again, except once on a network of sites in sub-directories, where each site now keeps its own answer. And an Ask everybody again button, for when you change what you do with visitors' data, which does nothing until you confirm.

None is ever taller than the screen: on a small phone the choices scroll, every answer stays in view, and a choice reached with the keyboard is scrolled into view above them. Three colours, and the quieter greys are worked out from them — so a dark background gives a dark banner without three more fields.

If that visitor opens the choices, one line says their browser's privacy signal was honoured, so they can see it was.

With WPML or Polylang each box can be translated into every language you run, and the Dashboard tells you when a language's buttons would otherwise be in English, or when its pages show your words untranslated. Accept and Reject stay the same size whatever you type.

It is built from what the banner asks about, so when a new plugin adds a pixel the list follows at the next reading of the site.

It moves over for the range's other floating buttons instead of covering them, and shows only its drawing on a narrow phone. Or [cookie_choices] anywhere, or any element with the class trcc-open. Somebody who said no in January has to be able to say yes in March, and a consent tool with no way back is one that takes an answer and then refuses to hear a different one.

Each service's cookie names come from its maker's own documentation, and the cookie list shows them. What no website can touch, a company's cookies on its own address, is left to the visitor's browser, and the list says so.

WooCommerce's order attribution waits for Advertising, so orders from visitors who refuse show the origin Unknown.

Where a reading finds Google Tag Manager, the Dashboard says what holds the container back and shows the two ways to make advertising tags wait for Advertising. It works behind a page cache, because the event is worked out in the visitor's browser.

"What does this site load" is a question an agency asks about forty sites at once, and clicking through forty dashboards is how it stops being asked.

Spanish and French are included and complete, and in any other language you can type every word on the banner and its choices. It declares its own cookie and its own record to WordPress's privacy policy tool, which a consent plugin not doing would be a joke somebody eventually notices.

No IP address and no browser string. Handed a reference, you can answer "what did I agree to"; handed the whole table, nobody learns who visited. Downloads as a spreadsheet.