How This Briefing Works
This dossier opens with key findings, then maps the gap between what Google Maps 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 366 sites
vendor fires before consent
Briefing
Google Maps positions as neutral mapping service but embeds the full Google tracking stack when loaded via JavaScript API. Scanner detections reveal defeat device obfuscation, behavioral biometrics tied to map interaction, cross-domain sync, persistent storage abuse, and GTM exploitation. Geolocation data links to Google's cross-product identity graph.
What This Means For You
Sites embedding Google Maps inherit location tracking and cross-product profiling from API load. Device fingerprints link to Google advertising profiles enriched with geolocation histories. Persistent storage creates long-term location tracking liability. GTM abuse enables surveillance beyond mapping. GDPR and location privacy exposure if Maps loads before consent.
Risk Channel Breakdown
Maps fingerprinting and location tracking distorts attribution by tying map engagement to Google's broader user profiles and geolocation histories, corrupting measurement of genuine location interest.
Device fingerprints, geolocation data, and behavioral profiles collected via Maps API feed Google's advertising network and location intelligence products, subsidizing competitors.
Expands attack surface
Fingerprinting, session recording, and geolocation capture initiate on Maps API load without user consent, creating GDPR liability and location privacy exposure for embedding sites.
Threat Indicators
Runtime-observed (BTI-C)
Evasion infrastructure, auditor bypass
Keystroke/mouse tracking
Full session replay
Identity stitching
Ignoring CMP signals
Device identification
Long-lived identifiers
PII deanonymization
Container/loader (neutral)
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 Google Maps'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
5 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 →