How This Briefing Works
This dossier opens with key findings, then maps the gap between what Mile Tech discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection evidence underneath. BLACKOUT observes runtime browser behavior and cites the regulations that address each pattern — legal determinations are your counsel's call.
At a Glance
across 1 sites
vendor fires before consent
Briefing
Mile Tech deploys platform scripts that begin data collection before consent mechanisms engage. Limited public information suggests standard marketing tag behavior with consent bypass patterns common to the category.
What This Means For You
Functionality impact depends on Mile Tech deployment purpose - removal may affect analytics, personalization, or campaign tracking. Retention risk includes regulatory exposure for consent violations and potential data subject complaints if tracking scope exceeds disclosures.
Risk Channel Breakdown
Distorts attribution data
Feeds competitor intelligence
Expands attack surface
Pre-consent script execution violates GDPR consent requirements and ePrivacy Directive cookie rules.
Threat Indicators
Runtime-observed (BTI-C)
Ignoring CMP signals
Per-code narrative explanations of what each detected behavior means for your organization
Per-code evidence with full attribution chain, severity rankings, and consequence narratives See pricing →
Claims vs. Reality
BLACKOUT analyzed Mile Tech's public claims against observed runtime behavior and identified 1 contradiction.
Full claim-vs-reality gap analysis with claim text, observed behavior, severity, regulatory citations (GDPR, CCPA, ePrivacy), and evidence pointers per gap See pricing →
What To Do
4 for current users · 4 for evaluators
contractual leverage points
Role-specific actions (security / legal / marketing / procurement), full negotiation brief with contractual language, and BTI-code-specific consequences See pricing →
Supply Chain & Pairings
Full supply-chain mapping (loads / loaded-by lists with vendor identities) and the undisclosed-subprocessor list with observation evidence See pricing →