How This Briefing Works
This report opens with key findings, then maps the gaps between what Bluecava 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 Mechanism
50% pre-consent tracking rate detected; explicit rejection of Do Not Track signals
Pre-Consent Activity
Bluecava was observed loading and executing before user consent was obtained on 50% of sites where it was detected.
Data Recipient Disclosure
Vague categories including Clients, Business Partners, subsidiaries with no specific list
Technology Scope
Cross-device fingerprinting, household identity graphs, persistent advertising IDs that survive cookie deletion
Undisclosed Sharing
Hidden data recipients
Claims vs. Observed Behavior
Consent Mechanism
“GDPR and CCPA compliant”
50% pre-consent tracking rate detected; explicit rejection of Do Not Track signals
Runtime detection data and privacy policy quote: we do not recognize or respond to browser-initiated Do Not Track (DNT) signals
Data Recipient Disclosure
“Shares data with service providers”
Vague categories including Clients, Business Partners, subsidiaries with no specific list
No subprocessor list available on website
Technology Scope
“Device identification for advertising”
Cross-device fingerprinting, household identity graphs, persistent advertising IDs that survive cookie deletion
BlueCava opt-out page confirms identity of your device sharing and advertising ID generation
Security Assurance
“None made”
No security documentation, SOC2, or trust center available
Website audit found no security/compliance pages
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Bluecava
- →Audit consent implementation — 50% pre-consent rate indicates consent mechanism failure for device fingerprinting
- →Update privacy policy to specifically disclose BlueCava/Adstra and the device fingerprinting capability
- →Implement GPC signal recognition — BlueCava rejects DNT but GPC has stronger legal backing under CCPA
- →Request specific named list of data recipients instead of vague Clients and Business Partners categories
If You're Evaluating Bluecava
- →Assess whether device fingerprinting aligns with your privacy posture — this technology is designed to circumvent user privacy controls
- →Request Adstra's complete data sharing partner list before any engagement
- →Compare with privacy-respecting alternatives that honor DNT and GPC signals
- →Verify regulatory compliance in all jurisdictions — device fingerprinting faces increasing regulatory scrutiny
Negotiation Leverage
- →Do Not Track rejection: BlueCava explicitly ignores DNT signals — use this documented policy to negotiate GPC (Global Privacy Control) signal recognition as a contract requirement
- →Device fingerprinting persistence: Technology designed to survive cookie deletion and private browsing — leverage for enhanced consent and opt-out requirements in your contract
- →Vague data recipients: Data shared with undefined Clients, Business Partners, and affiliates — require named recipient disclosure as a non-negotiable condition
- →50% pre-consent rate: Half of tracking fires before consent — negotiate consent architecture requirements and contractual penalties for pre-consent data collection
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
Ignoring CMP signals
Device identification
PII deanonymization
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
41 detection signatures across scripts, domains, cookies, and network endpoints