How This Briefing Works
This report opens with key findings, then maps the gaps between what CommonRoom 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
Compliance Claim vs Behavior
91.7% pre-consent tracking rate. 19 vendors fire before consent on own website
Data Sale Disclosure
Loads identity resolution vendors whose business is selling identified visitor data
Pre-Consent Activity
CommonRoom was observed loading and executing before user consent was obtained on 92% of sites where it was detected.
Subprocessor Disclosure
30 specific vendors detected, none named
Privacy Policy Currency
Policy predates Person360, web visitor identification, waterfall enrichment products
Claims vs. Observed Behavior
Compliance Claim vs Behavior
“SOC2 Type II, GDPR compliant, CCPA compliant”
91.7% pre-consent tracking rate. 19 vendors fire before consent on own website
Runtime scan of commonroom.io shows Albacross, Demandbase, DoubleClick, G2, GoogleAnalytics4, HubSpot, IDVisitors, LinkedIn, LiveIntent (4x), Vector all firing pre-consent
Data Sale Disclosure
“Common Room does not sell personal information”
Loads identity resolution vendors whose business is selling identified visitor data
Albacross, IDVisitors, Vector detected on site - all commercial identity resolution services
Subprocessor Disclosure
“Generic service providers and business partners”
30 specific vendors detected, none named
Privacy policy names zero specific vendors. All 30 observed vendors effectively undisclosed
Privacy Policy Currency
“Effective Date: March 30, 2021”
Policy predates Person360, web visitor identification, waterfall enrichment products
Major product launches in 2022-2024 not reflected in 2021 policy
DNT Signal Handling
“We do not respond to or honor DNT signals”
Honest disclosure but contradicts GDPR/CCPA compliance posture
Privacy policy explicitly states DNT not honored
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use CommonRoom
- →Audit your consent implementation immediately — Common Room fires pre-consent by default and you are likely non-compliant
- →Review subprocessor agreements — 30 vendors detected on their site likely flow into their product infrastructure
- →Update privacy policy to disclose Common Room and all downstream vendors their product introduces
- →Implement server-side consent gating — do not trust client-side consent with a 91.7% pre-consent rate vendor
If You're Evaluating CommonRoom
- →Request complete named subprocessor list — zero vendor names in privacy policy is a disqualifying red flag
- →Compare with Clearbit Reveal and 6sense on pre-consent behavior and vendor disclosure transparency
- →Require consent architecture documentation and independent audit before any deployment
- →Negotiate contractual guarantees that your visitor data will not enrich competitors using the same platform
Negotiation Leverage
- →91.7% pre-consent rate: Nearly all vendors fire before consent on commonroom.com — use this to negotiate consent architecture guarantees and contractual termination rights if pre-consent behavior is detected on your properties
- →Zero vendor disclosure: 30 vendors detected, zero named in privacy policy — require complete named vendor disclosure as a non-negotiable contract condition
- →Identity resolution risk: Person360 and web visitor identification built by a company with 91.7% pre-consent rate — negotiate data usage restrictions preventing your visitor data from enriching competitors
- →SOC2 certification scope: Claims SOC2 Type II yet 19 vendors fire pre-consent — request the SOC2 report and verify vendor management is within the certification scope
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
Full session replay
Ignoring CMP signals
Device identification
Container/loader (neutral)
IOC Manifest
Indicators of compromise across 4 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
57 detection signatures across scripts, domains, cookies, and network endpoints