How This Briefing Works
This report opens with key findings, then maps the gaps between what Docs Google 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
Docs Google was observed loading and executing before user consent was obtained on 48% of sites where it was detected.
Claims vs. Observed Behavior
pending
“Unknown - requires claims extraction via CDT”
Runtime evidence shows C06/C08/C09 patterns when embedded
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Docs Google
- →Audit embedded Google resources (Docs, Forms, Maps, Fonts)
- →Confirm consent before Google resource loads
- →Review DPA: Google is separate controller, not processor
If You're Evaluating Docs Google
- →Test page load: do Google embeds load pre-consent?
- →Check privacy policy: is Google data sharing disclosed?
- →Verify consent banner explicitly lists Google as third party
Negotiation Leverage
- →Embedded Google Docs = cross-domain sync with advertising ecosystem. Is this disclosed to visitors?
- →C09 consent bypass: Google resources load before banner interaction. How do you prevent this?
- →Google is controller, not processor. Do you have controller-to-controller agreement for GDPR compliance?
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.
Keystroke/mouse tracking
Identity stitching
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
24 detection signatures across scripts, domains, cookies, and network endpoints