Most CMPs leak.
consentline doesn't.
A true hard-block consent platform: zero data reaches Google before consent — even gtm.js is blocked, not merely gated. Built for a CIPA/CCPA litigation posture.
No app to sign into · SRI-pinned releases · CDN-delivered
Why consentline
Compliance that actually holds up
Six capabilities that separate a real hard-block CMP from a consent-mode checkbox.
True hard-block
Zero data to Google before consent. gtm.js itself is blocked — no cookieless pings.
Jurisdiction-aware
Auto geo-detects and applies the correct ruleset across 8 state laws, with a fail-closed baseline.
GPC honored
Respects Global Privacy Control signals — and auto-applies them for returning visitors.
Append-only audit log
Every choice recorded to an append-only edge log (salted IP hashes, no raw PII) — exportable as CSV evidence for audits and DSARs.
GTM-native
Declarative gating via data-consent markup — no DOM monkey-patching.
Fast & supply-chain-safe
Tiny vanilla-JS banner, SRI-pinned immutable releases (sha384), CDN-delivered.
How it works
Live in one snippet
Add one snippet
Drop a single SRI-pinned tag into your <head> — or install via GTM.
integrity="sha384-…"></script>
Visitor chooses
A jurisdiction-correct banner appears. Until they accept, no tracking tag — not even gtm.js — is allowed to load.
Gated & logged
Tags fire only for granted categories, and every choice is written to an append-only audit trail at the edge.
Most CMPs leak. consentline doesn't.
The difference is what happens before a single click — at the network layer.
Data left the browser before the visitor chose.
Zero requests to Google. Nothing leaves until consent.
See your own site stop leaking.
Request a demo and we'll show consentline blocking tags on a real page — and walk through the audit log and jurisdiction rules.
- Live before/after network capture
- Your GTM container, reviewed
- No app to set up
Thanks — we'll be in touch.
Your request was routed to the consentline team at IFMM.