Consent
Consent management · GDPR · TDDDG
TEKKNA Consent is the cookie banner, blocker and scanner we run on our own sites. One synchronous script, served from Cloudflare's edge, that holds every third-party tag back until the visitor decides — and keeps a record they can quote.
Three parts, one script
Each part does one job, and each is the one we wished our old consent tool had done properly.
Accept, reject and settings side by side, same size, same weight — the configuration format refuses a banner that demotes "Reject". The second layer lists every service with vendor, purpose, duration and third-country transfer before anyone agrees to anything. German and English ship in the box; any language is a config away.
Anything a page inserts from script — tag managers, pixels, embeds — is intercepted and held. Anything written directly into the HTML can be marked up once and never fetched at all. Blocked embeds show a click-to-load box instead of a hole, and a "load once" that stores nothing.
<!-- held until "functional" is allowed --> <iframe data-cmp-src="https://www.google.com/maps/embed?…" data-cmp-service="google-maps"></iframe>
A crawler visits each page as a visitor who said nothing, then as one who said yes. Cookies, storage and third-party requests are recorded for both passes and matched against a vendor knowledge base. Anything set before consent is a finding you will hear about the same morning.
How it works
The script is synchronous and comes first, so it runs before anything it needs to stop. Your site's configuration is compiled into it at the edge — one cached request, under 10 kB — and the banner's second layer loads only when someone opens it.
<head> <meta charset="utf-8"> <script src="https://cmp.tekkna.dev/s/‹your-site›.js"></script> … your own tags, exactly as before … </head>
Google tags get gtag('consent','default') before they load and an
update the moment a decision is made — Consent Mode v2, with the German
default of not loading Google at all until then.
Records live in an EU-region database for the limitation period (four years by default, yours to set). Any visitor can quote their consent id from the settings layer; you can look it up.
Compliance
What the Datenschutzkonferenz and the EDPB ask for is enforced by the configuration format. A banner that breaks a rule cannot be published.
Switching
The order matters — the scan runs while your old banner is still up, so nothing is guessed.
Questions we get
Not yet. TCF matters if you sell programmatic advertising through AdSense, Prebid or similar. For everyone else it adds 100 kB of vendor list and a dozen purposes nobody reads. If you need it, tell us — it is on the list, gated on demand.
Built in, version 2, with all seven signals. The default is "basic" mode: Google tags do not load at all until a decision, which is what German supervisory authorities expect. "Advanced" mode (cookieless pings before consent) is available and labelled as the trade-off it is.
Safari caps anything set from script at seven days without interaction. Every consent tool has this limit; the banner simply asks again. A server-set cookie bridge for the client's own origin is planned for sites where this matters.
Consent records in a Cloudflare D1 database pinned to Western Europe; configuration in Cloudflare KV; the script on Cloudflare's edge. Nothing is stored before a decision, and no full IP is stored ever.
Yes. The blocker holds the container until a decision if you want the strict mode, or
lets it load with Consent Mode denied signals if you prefer. Either way the tags
inside get tekkna_consent_* events they can trigger on.
For TEKKNA clients it is part of the engagement. For everyone else we quote per site; there is no per-pageview meter and no plan tiers to grow out of.
Talk to us
A first scan of your site with and without consent, and what switching would involve. No form, no funnel.
Where we are