How This Briefing Works
This report opens with key findings, then maps the gaps 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 data and evidence underneath.
Key Findings
Pre-Consent Activity
Mile Tech was observed loading and executing before user consent was obtained on 67% of sites where it was detected.
Claims vs. Observed Behavior
disclosure
“Pending claims extraction”
Limited public information about Mile Tech data practices. Counselor score (40) indicates consent violations but specifics require vendor documentation review.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Mile Tech
- →Implement consent gate before Mile Tech scripts load
- →Audit platform configuration for data collection scope and third-party sharing
- →Review Data Processing Agreement for processor obligations
- →Confirm privacy policy adequately discloses Mile Tech data processing
If You're Evaluating Mile Tech
- →Defer all Mile Tech scripts until post-consent confirmation
- →Request vendor documentation on consent management integration capabilities
- →Assess whether platform functionality can be replicated with privacy-respecting alternatives
- →Investigate platform data retention and deletion capabilities
Negotiation Leverage
- →Mile Tech contract terms are critical to assess - demand clarity on data sharing permissions and processor vs controller status
- →Negotiate explicit consent management integration requirements in service terms
- →Confirm platform honors consent withdrawal and data deletion requests
- →Request technical documentation on tag firing controls and consent signal integration
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.
Ignoring CMP signals
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