How This Briefing Works
This report opens with key findings, then maps the gaps between what Adplexity 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
Subprocessor Disclosure
8 specific vendors (Clarity, DoubleClick, GA4, Google Ads, Intercom, LinkedIn, Mapbox, MetaPixel) load pre-consent with zero named
Pre-Consent Activity
Adplexity was observed loading and executing before user consent was obtained on 3% of sites where it was detected.
Jurisdiction Disclosure
Data transmitted to US-based vendors (Google, Meta, Microsoft, LinkedIn) without disclosure
Policy Currency
Policy predates GDPR enforcement (May 2018), unchanged for 8+ years
Undisclosed Party
Not in privacy policy
Claims vs. Observed Behavior
Subprocessor Disclosure
“Privacy policy Section 4 mentions disclosure to 'third party service providers' generically”
8 specific vendors (Clarity, DoubleClick, GA4, Google Ads, Intercom, LinkedIn, Mapbox, MetaPixel) load pre-consent with zero named
Runtime scan of adplexity.com shows all 8 vendors fire on page load before consent
Jurisdiction Disclosure
“Section 5 states data stored in Hong Kong”
Data transmitted to US-based vendors (Google, Meta, Microsoft, LinkedIn) without disclosure
Network analysis shows requests to google-analytics.com, facebook.com, linkedin.com, clarity.ms
Policy Currency
“Policy effective Nov 29, 2017”
Policy predates GDPR enforcement (May 2018), unchanged for 8+ years
Policy footer states 'effective as of 29 Nov 2017'
Consent Mechanism
“Section 6 references consent and choice”
No consent banner observed, 8 vendors fire immediately
Page load captures show tracking before any user interaction
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Adplexity
- →Audit your privacy policy — AdPlexity's undisclosed vendors may affect your compliance posture if their tools process your data
- →Request their subprocessor list — they have none published despite 8 vendors detected at runtime
- →Document that their 2017 privacy policy predates GDPR — this creates compliance uncertainty for EU usage
- →Consider that their ad network relationships may expose your competitive research patterns to the platforms you monitor
- →Implement your own consent mechanism — do not rely on AdPlexity's non-existent compliance infrastructure
If You're Evaluating Adplexity
- →Note the 2017-dated privacy policy with zero GDPR references — this is a fundamental compliance gap
- →Request SOC2 or any security certification — expect none to exist for a Hong Kong-based ad spy tool
- →Assess whether competitive intelligence gathered through AdPlexity creates data processing obligations under GDPR Art 14
- →Factor in that your research activity becomes demand signal data for the same ad networks being monitored
- →Consider alternatives with modern privacy compliance infrastructure before committing
Negotiation Leverage
- →Privacy policy modernization: AdPlexity's privacy policy dates from 2017, predating GDPR. Require updated privacy policy with GDPR/CCPA language and named subprocessor list as a contract precondition.
- →Subprocessor disclosure: Zero vendors named while 8 detected at runtime. Require complete enumeration of all third-party data recipients.
- →Pre-consent remediation: 100% pre-consent rate. Require contractual guarantee that tracking fires only after consent on their properties where your data is processed.
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
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
58 detection signatures across scripts, domains, cookies, and network endpoints