The Blackout Trust Standard: GTM behavior you can verify.

We measure the gap between what your privacy policy promises and what your GTM stack actually does at runtime. Then we publish receipts.

47,823
detections logged to date
3.7
avg undisclosed vendors per site
127
critical consent violations documented
Join the Founding Cohort

Introducing the Blackout Trust Standard (BTS)

SOC 2 made security legible to auditors. ISO 27001 made information governance legible to enterprises. BTS makes GTM behavior legible to legal, buyers, and regulators.

BTS-001: Subprocessor Disclosure Parity
Runtime vendors match Annex A or equivalent
BTS-002: Consent Gate Timing
No exfiltration before affirmative consent
BTS-003: Deanonymization Disclosure
Person-level ID vendors explicitly disclosed
BTS-004: Session Replay Disclosure
Keystroke/click capture vendors named in policy
BTS-005: Fingerprinting Controls
Canvas/WebGL/AudioContext disclosed or blocked
BTS-006: CNAME Cloaking Detection
First-party subdomains resolve to third-party tracking
BTS-007: Post-Reject Behavior
Zero network calls to rejected vendors post-opt-out
BTS-008: Data Residency Claims
Observed request geography matches policy promises

How We Verify

  • Runtime timelines — Timestamped HAR captures showing script load, API calls, cookie writes
  • Policy/Subprocessor Diff — Automated comparison of detected vendors against disclosed lists
  • Chain of Custody — SHA-256 hashing of all artifacts; immutable audit trail

Badges & Tiers (BTS)

You earn it with proof—or you don't.

Bronze
≥70 score
  • All critical controls (BTS-001, BTS-002, BTS-003) pass
  • Subprocessor list published and ≥80% accurate
  • Consent banner gates exfiltration within 500ms tolerance
  • No silent deanonymization vendors detected
Silver
≥80 score
  • All Bronze requirements met
  • Zero post-reject violations (BTS-007)
  • Session replay and fingerprinting fully disclosed (BTS-004, BTS-005)
  • CNAME cloaking either disclosed or absent (BTS-006)
Gold
≥90 score
  • All Silver requirements met
  • 100% subprocessor disclosure parity (BTS-001)
  • Data residency claims verified via observed request geography (BTS-008)
  • Public manifest hosted at /.well-known/blackout.json

Badge can be suspended or revoked on critical breach.

Badge Examples

BLACKOUT TRUST STANDARD
Bronze Badge • Verified
Score
74
Controls
6/8
Company: Acme Corp
Verified: 2025-11-07
BTS v0.1 • Next check: Q2 2026
BLACKOUT TRUST STANDARD
Silver Badge • Verified
Score
84
Controls
7/8
Company: TechFlow Inc
Verified: 2025-11-07
BTS v0.1 • Next check: Q2 2026
BLACKOUT TRUST STANDARD
Gold Badge • Verified
Score
94
Controls
8/8
Company: DataShield Ltd
Verified: 2025-11-07
BTS v0.1 • Next check: Q2 2026

Not Gartner. Not G2.

Pay-to-Play RankingsBlackout Evidence
Sponsorable placement
Revocable badge tied to runtime proof
Vendor self-reported data
Third-party detection with chain-of-custody
Analyst subjectivity
Automated control scoring (0.0–1.0)
Annual refresh cycles
Quarterly re-verification for badge holders
Opaque methodology
Open spec, published controls, public revocation log
Influence wins
Behavior wins

This isn't Gartner or G2. You can't sponsor your way up a chart. We grade behavior, not influence.

How It Works (Detect → Diff → Prove)

1

DETECT

We fingerprint every script, pixel, and API call. Runtime reality vs. what you disclosed.

+186 ms post-reject → s3-us-west-2.amazonaws.com/b2bjsstore/.../reb2b.js.gz
2

DIFF

We compare detected vendors against your subprocessor list and privacy policy. No guessing. Just facts.

policy_subprocessors[] ≠ runtime_vendors[] (3 undisclosed: ████, ██████, █████)
3

PROVE

Counsel-ready Evidence Pack with timestamped artifacts, control results, and remediation roadmap.

sha256(evidence_pack.zip) = a3f9c8e7d2b1a4f6c9e8d7b3a2f1c0e9

For Legal, RevOps, and Buyers

Legal

  • • Counsel-ready evidence for GDPR Article 13/28 compliance
  • • Subprocessor disclosure parity checks against Annex A
  • • DSAR posture assessment (what vendors have PII access)

RevOps

  • • Vendor sprawl inventory with ownership attribution
  • • Consent gating verification (pre/post-opt-in timing)
  • • Remediation roadmap with BTS control mapping

Buyers

  • • One-line RFP clause: "BTS-Silver or higher required"
  • • Verify vendor claims with evidence, not marketing decks
  • • Public badge directory for due diligence

Responsible Disclosure & Revocation

Private Remediation Window

Companies holding a BTS badge receive private notification of gaps discovered in quarterly re-scans. You get 30 days to remediate before public disclosure.

Dispute Process

Challenge a finding. We re-scan. Outcome is logged. If you're right, we publish the correction. If you're wrong, the gap stands.

Critical Breach Protocol

Silent deanonymization vendor detected post-badge issuance? Consent gate bypassed? You have 72 hours to remediate or we suspend the badge and publish the evidence.

Join the Founding Cohort

We're inviting 25 companies to the BTS Founding Cohort. You get priority audit windows, quarterly re-checks, and early steering group invites. Your logo (optional) goes on the founding page.

What you provide: Runtime access for initial audit. Public commitment to disclosure parity.
What you get: Badge (if you pass), evidence pack, remediation roadmap, founding member status.

Apply to Founding Cohort

Click to fill out the application form on our main page

FAQ

Is this GDPR compliance?

We measure behavior. Timing + URLs. We don't provide legal opinions. Jurisdictional analysis happens in the evidence report.

What goes in the public directory?

Tier (Bronze/Silver/Gold), score (70–100), last verified date, and a link to your company-hosted manifest at /.well-known/blackout.json.

Can we lose the badge?

Yes—on critical breach. See Revocation Policy. Badges can be suspended or revoked.

What is the manifest?

A machine-readable file you host at /.well-known/blackout.json containing your disclosed subprocessor list, policy URL, and badge metadata.

Pricing?

Enterprise audit and cohort pricing on request.