How This Briefing Works
This report opens with key findings, then maps the gaps between what QuantumMetric 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
Consent Compliance
100% pre-consent tracking rate - 12 vendors including DoubleClick, MetaPixel, LinkedIn load before consent obtained
Pre-Consent Activity
QuantumMetric was observed loading and executing before user consent was obtained on 100% of sites where it was detected.
Subprocessor Disclosure
Only Google LLC disclosed as subprocessor; 27 vendors detected on own website including identity resolution and advertising platforms
Undisclosed Party
Not in privacy policy
Undisclosed Sharing
Hidden data recipients
Claims vs. Observed Behavior
Consent Compliance
“GDPR and CCPA compliant with SOC2+HITRUST attestation”
100% pre-consent tracking rate - 12 vendors including DoubleClick, MetaPixel, LinkedIn load before consent obtained
Runtime scan 2026-01-23 shows pre_consent=true for Clay, Cloudflare Insights, CommonRoom, CookieYes, DoubleClick, G2, GoogleAnalytics4, HubSpot, LinkedIn, MetaPixel, Qualified, StackAdapt
Subprocessor Disclosure
“Transparent data processing with subprocessor notification”
Only Google LLC disclosed as subprocessor; 27 vendors detected on own website including identity resolution and advertising platforms
Privacy policy subprocessor section lists only Google; runtime detection shows ZoomInfo, Clay, HubSpot, LinkedIn, DoubleClick, StackAdapt and 21 others
Security Documentation
“SOC2+HITRUST attestation demonstrates security commitment”
SOC2 report not publicly downloadable; requires sales contact/NDA
Trust center at /platform/data-privacy-security does not provide direct access to attestation documents
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use QuantumMetric
- →Audit your consent implementation independently — Quantum Metric's 100% pre-consent rate on their own site means their compliance claims require independent verification
- →Request SOC2+HITRUST report directly and verify controls match your data protection requirements for session recording
- →Review all data flows to understand what behavioral data leaves your environment through Quantum Metric's platform
- →Verify session replay masking covers all PII fields in your application — test with synthetic data before production deployment
- →Document Quantum Metric in your GDPR Article 30 records as a processor with all 27+ detected subprocessors
If You're Evaluating QuantumMetric
- →Visit quantummetric.com with browser DevTools open to observe their 100% pre-consent tracking behavior firsthand
- →Note the gap between SOC2+HITRUST/ISO 27001 certifications and the worst pre-consent rate in our detection network
- →Request complete subprocessor list beyond Google LLC — 27+ vendors detected at runtime represents a massive disclosure gap
- →Ask for evidence of consent-gated data processing in their production environment before trusting compliance marketing
- →Evaluate alternative session replay vendors with demonstrable consent compliance (FullStory, self-hosted options)
Negotiation Leverage
- →Pre-consent SLA: 100% pre-consent rate on quantummetric.com — the worst score in our detection network. Require contractual guarantee of 0% pre-consent activity on your property with quarterly independent audit verification and liquidated damages per violation.
- →Subprocessor disclosure: Only Google LLC disclosed while 27+ vendors detected including ZoomInfo, Clay, and CommonRoom (identity resolution). Require complete subprocessor enumeration with 30-day advance notice before additions.
- →Session replay data scope: Quantum Metric captures detailed user interactions. Require contractual specification of exactly what data is recorded, with mandatory PII masking verified by independent audit before deployment.
- →Certification scope verification: Request SOC2+HITRUST report and ISO 27001 certificate — verify scope explicitly covers client-side session recording JavaScript, not just server-side infrastructure.
- →Identity resolution prohibition: ZoomInfo, Clay, and CommonRoom on their site deanonymize visitors. Require contractual guarantee that no identity resolution capabilities are embedded in their session replay product deployed on your property.
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
Long-lived identifiers
PII deanonymization
IOC Manifest
Indicators of compromise across 5 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
206 detection signatures across scripts, domains, cookies, and network endpoints