DEVELOPER GUIDES
AI will generate a banner that looks right. The trouble starts later — when the client adds a new script, when the law gets reinterpreted, when a redesign quietly breaks blocking and nobody notices.
It’s not about whether it can write one. It can. It’s about what happens next.
| Hand-rolled | CookieFood | |
|---|---|---|
| Renders a banner, stores the choice The basics — anyone can do this. | ✓ | ✓ |
| Knows what cookies are actually on the site Including the ones your client adds next month through GTM or a plugin. | ✗ | ✓ |
| Blocks scripts before they load Hiding them is not enough — they must not execute. That’s ordering, not CSS. | partly | ✓ |
| Consent Mode v2 for Google Without it Google degrades measurement and remarketing in the EU. | manual | ✓ |
| Proof of consent In an audit you must show who consented and when. localStorage is not evidence. | ✗ | ✓ |
| Keeps up with legal changes Code written in January knows nothing about a July ruling. | ✗ | ✓ |
| Notices when it stops working Banners don’t fail loudly. They stop blocking and look exactly the same. | ✗ | ✓ |
We crawl your pages and find every cookie and storage entry. Regularly — not once at setup.
Third-party scripts don’t execute until the visitor consents. Not hidden — not executed.
A record for every site and every day showing the check ran and how it went. That’s your evidence.
Signals for Google Ads and Analytics set correctly, with no manual GTM work.
EN, DE, IT, PL, HU, SK, CS. The banner follows the visitor.
Folders per client, one invoice. Hand a domain over to the client in one click.
One line in <head>, as high as possible. Everything else is configured in your account — the snippet never changes.
From €5 a month per domain. You pay for how many people actually see the banner — not for how many pages you have. The price you sign up at stays yours.