How This Briefing Works
This report opens with key findings, then maps the gaps between what Gamned 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
Pre-Consent Activity
Gamned was observed loading and executing before user consent was obtained on 67% of sites where it was detected.
Claims vs. Observed Behavior
consent
“Unknown - requires claims extraction via CDT”
Deploys cross-domain identity syncing + pre-consent ad tracking
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Gamned
- →Disable Gamned pixel immediately - no ad platform justifies pre-consent deployment
- →Request list of all cookie-sync partners: assess total liability exposure
- →Demand deletion of all historical cross-domain tracking data
If You're Evaluating Gamned
- →Require Gamned to implement consent-first architecture before any contract consideration
- →Demand contractual liability assumption: vendor pays 100% of penalties for consent violations and unauthorized data transfers
- →Migrate to privacy-safe advertising: contextual targeting (no tracking), consent-first programmatic, or direct publisher relationships
Negotiation Leverage
- →Gamned creates exponential consent liability through cross-domain syncing: per-visitor violations multiplied by number of ad network partners
- →Vendor must eliminate pre-consent tracking AND cookie syncing, or assume 100% liability for multi-jurisdiction regulatory penalties
- →Programmatic advertising works with consent-first architecture - pre-consent deployment is vendor choice, not technical requirement
- →Current architecture violates GDPR Article 7 (consent) + ePrivacy Article 5(3) (cookies) + potential Article 44 (data transfers) across jurisdictions
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.
Identity stitching
Impact: Cookie syncing with third-party ad networks before consent creates liability for each sync partner. GDPR enforcement agencies can assess penalties per data recipient - 5 sync partners = 5x violation multiplier.
Ignoring CMP signals
Impact: Ad tracking and identity syncing load before consent opportunity, creating strict liability under GDPR Article 7 and ePrivacy Directive Article 5(3). Combined with cross-domain data sharing, elevates to data transfer violation.
IOC Manifest
Indicators of compromise across 3 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
No indicators in this category
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
7 detection signatures across scripts, domains, cookies, and network endpoints