Your DPA is a claim. Runtime is the evidence.
Privacy policies declare. DPAs declare. Subprocessor lists declare. Runtime executes. We capture the delta and cite the regulations that address it. Your counsel makes the call.
▸ Vendor declared
“We use 3 subprocessors.”
▸ Runtime observed
13 third-party connections
adnxs.com · demdex.com · doubleclick.net · +7 undisclosed
▸ Delta
10
undisclosed data sharing relationships
We observe and cite. We never assert.
Blackout is not a legal tool and does not provide legal advice. We document what vendors do, identify the regulations that address that behavior pattern, and hand the artifact to your counsel.
Your General Counsel reads the evidence. Your General Counsel determines what it means. We're the camera, not the judge.
▸ The posture, in two columns
✓ What we say
- “observed”
- “detected”
- “fires”
- “transmits”
- “addressed under”
- “maps to”
- “touches”
- named clause citations
✕ What we don't
- “violation”
- “non-compliance”
- “breach”
- “applicable” (legal)
- “counsel review recommended”
- “liability”
- “penalty” / “fine”
- predictions of any kind
Blackout provides evidence. Counsel provides assessment.
The delta is documentable.
Three passes. One verdict on your CMP.
01 / Pre-Consent
Before the banner appears
Captures every vendor that fires before any user interaction.
02 / Post-Accept
After explicit consent
Captures the full set of vendors authorized by the user.
03 / Post-Reject
After explicit rejection
Captures any vendor still firing despite a rejection click.
Disclosed: 3. Observed: 13.
When a vendor's privacy policy lists three subprocessors and the scanner detects thirteen third-party connections, the “product functionality” defense collapses.
Each undisclosed subprocessor adds a layer of exposure your DPA never bound, your team never approved, and your visitors never consented to. The chain depth multiplies; accountability approaches zero.
Disclosed in privacy policy (2026-01-15)
- + AWS · processing
- + Google Cloud · processing
- + Cloudflare · CDN
Observed at runtime
- − adnxs.com (AppNexus / Xandr)
- − demdex.com (Adobe Audience Manager)
- − doubleclick.net (Google Ads)
- − liveramp.com (identity graph)
- − pubmatic.com (programmatic)
- − tiktok.com (pixel)
- − 4 additional
We name the clauses. Counsel names the call.
GDPR
EU / EEA- ▸ Art. 6 · lawfulness
- ▸ Art. 7 · consent
- ▸ Art. 13 / 14 · transparency
- ▸ Art. 28 · subprocessors
CCPA / CPRA
California- ▸ § 1798.100(b) · disclosure
- ▸ § 1798.135 · opt-out
- ▸ “sale” / “share” definitions
ePrivacy Directive
EU member states- ▸ Art. 5(3) · cookie consent
- ▸ Member-state implementations
TCPA
United States- ▸ Vendor-initiated tracking
- ▸ Automated contact patterns
State Privacy Laws
CO · CT · VA · UT · TX · OR · MT- ▸ Per-state consent regimes
- ▸ Sensitive-category collection
- ▸ Opt-out signal handling
PIPEDA
Canada- ▸ Knowledge & consent principles
- ▸ Data collection without adequate consent
▸ Regulatory ceilings (GDPR 4%, CCPA per-violation, etc.) live on the methodology page as reference. They do not surface in product.
The artifact your counsel already knows how to read.
▸ counsel-evidence-package.zip
SHA-256 chain of custody · ISO-8601 timestamps · HAR + payload hashes
Capture the delta. Hand it over.
Run a scan. Get the DPA-vs-runtime artifact in 60 seconds. Counsel reads the evidence. Counsel makes the call.
▸ Free · No signup · No credit card · 600+ vendor signatures