How This Briefing Works
This report opens with key findings, then maps the gaps between what Complianz discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection data and evidence underneath.
Key Findings
Analysis pending. Findings will appear here once intelligence collection is complete.
Claims vs. Observed Behavior
pending
“Awaiting scanner verification”
No scanner data available for Complianz runtime behavior
disclosure
“Self-hosted with no third-party dependencies”
Cookie scan data transmitted to cookiedatabase.org external service
consent_integrity
“Advanced Mode default does not pre-load tracking”
Google tags fire on page load in Advanced Mode, consent modifies but does not gate collection
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Complianz
- →Verify Complianz runtime behavior: inspect network requests to cookiedatabase.org during cookie scans and quantify what data leaves your infrastructure.\n2. Switch Google Consent Mode from Advanced to Basic Mode to ensure tags do not fire before consent resolution — accept the analytics data loss as the cost of actual compliance.\n3. Audit consent record storage: confirm consent logs are stored locally as claimed and not transmitted to external services.\n4. Review cookiedatabase.org data retention: validate the claimed one-hour retention window and confirm no persistent profiling of your site's technology stack.\n5. Evaluate alternative consent solutions that do not operate external data aggregation services or default to pre-consent tag firing.
Negotiation Leverage
- →Complianz's primary vulnerability in procurement negotiations is the gap between its "self-hosted, no third-party" positioning and the cookiedatabase.org data pipeline. Request written confirmation of exactly what data leaves your server during cookie scans, retention periods, and whether aggregated scan data is used commercially. Demand contractual commitment to Basic Mode as the default Consent Mode configuration, with Advanced Mode requiring explicit opt-in documentation. The plugin's free tier creates vendor lock-in through feature gating (consent statistics, A/B testing, premium integrations are paid) — negotiate for full feature access or evaluate whether the free tier's limitations create compliance gaps. Leverage the 1M+ installation footprint as a security concern: demand SLA commitments for vulnerability disclosure and patching timelines given WordPress plugin supply chain risks.
Runtime Detections
BLACKOUT observed this vendor's JavaScript executing in a live browser and classified each hostile behavior using our BTI-C (Behavioral Threat Intelligence — Capability) taxonomy. These are not theoretical risks — each code below was triggered by something we watched this vendor's code actually do.
Evasion infrastructure, auditor bypass
Keystroke/mouse tracking
Impact: Consent signals are routed to Google Ads, Google Analytics, and Tag Manager, translating privacy preferences into optimization signals for the advertising ecosystem rather than enforcing data minimization boundaries.
Full session replay
Ignoring CMP signals
Impact: Cookie scan telemetry from 350,000+ installations flows to cookiedatabase.org, creating a centralized technology deployment database. Site owners may not fully understand that their cookie scan data is being aggregated externally despite claims of self-hosted operation.
Device identification
PII deanonymization
Container/loader (neutral)
IOC Manifest
Indicators of compromise across 3 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
139 detection signatures across scripts, domains, cookies, and network endpoints