Small tool, nothing hidden.
One snippet, and the list keeps itself
You paste one snippet. From then on the banner holds back cookies and browser storage that scripts on your page try to set before there is consent, including ones it has never seen before. We visit your site every day, so the cookie list in your banner stays current without you touching it.
| What we find | Where it belongs |
|---|---|
_ga | statistics |
_fbp | marketing |
session | necessary |
We check your site every day. New cookie found? Your list updates itself.
What we see, and what we do not
The script talks to one server: ours, in Europe. It asks which cookies your site uses, and it sends back each visitor's choice so you can later show that consent was given. That is the whole exchange.
We never follow your visitors and we never build profiles. No ad network, no data broker, nobody else is in the loop. A consent tool that tracked people would be the very thing it is meant to prevent.
And if our server is unreachable, nothing on your site breaks. The banner still appears and still blocks everything except strictly necessary cookies until someone chooses. An outage on our side is never an outage on yours.
Where a choice is kept
In two places. In the visitor's browser, so the banner does not ask again for about six months, unless you change what you ask. And on our server as a receipt, so you can show it later. A receipt holds no name and no email address. We do not store the visitor's IP address in it, only a salted hash.
Proof you can hold
Every fresh decision gets its own number and a receipt: the number, the date, the exact cookie list the visitor was shown, and the choice per category. You look up a receipt by its number in your dashboard, and you can export all of them whenever you like, so if a regulator asks, you have them ready. GDPR Article 7 puts the burden of proof on you, so we make the proof easy to keep.
- consent-id
- 7F3A-…-9C
- date
- today, 14:02
- statistics
- yes
- marketing
- no
- its own number
- what was chosen, per category
- the date and the cookie list they were shown
One receipt per choice. That is the proof.
Tracking stays off until consent
Through Google Consent Mode v2, Google's tags start on "denied". A tag you mark for a category loads only after the visitor says yes to that category, and withdrawing is as easy as agreeing: the settings button stays on the page.
| Before the choice | After the choice | |
|---|---|---|
| Statistics | off | on, the moment the visitor says yes |
| Marketing | off | still off: the visitor said no |
Your numbers keep working. Nobody who said no gets followed.
Built like it matters
Every change goes through an automated test suite and an independent security review before it goes live. The scanner that visits your site runs locked in a sandbox and can reach public web addresses only. The database accepts encrypted connections only, and backups are restored as a test, not just made.
What a banner cannot do
It cannot undo a script that has already run, and it cannot remove a cookie that your own server sets. Tags that must wait for consent have to be connected once: in your tag manager, or with one attribute on the tag. The install check looks at your site and tells you in plain words what it found.