DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed9 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 9 filings

Terrier Media Buyer, Inc. — June 2021 breach

Clustered 9 filings across 7 jurisdictions · filing window Oct 8, 2021 → Nov 5, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

30,709

First → last filing

Oct 8, 2021 → Nov 5, 2021

Merge confidence

100%

incident inc_1c2fcbe91f364a27 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Jun 3, 2021, discovered Jun 3, 2021 — the first regulatory filing landed 127 days later; 1 later filing was flagged late. 30,709 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 5 more. Notifications rolled out on a 28-day schedule across 9 filings beginning Oct 8, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
127days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
28days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksWashington✗ WA AG >90dMaine⏱ ME AG >30d · 152dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Jun 3, 2021breach begins
Jun 3, 2021discovered
notification delay · 127 days
Oct 8, 2021first filing
Nov 5, 2021most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. OCT 8MA AGMA AG noticefirst filing · 612 MA residentsday 0
  2. OCT 8IN AGIN AG noticestates nationwide total 30,709day 0
  3. OCT 8MT AGMT AG notice11 MT residentsday 0
  4. OCT 8CA AGCA AG noticeno count statedday 0
  5. OCT 18NH AGNH AG notice21 NH residents+10d
  6. OCT 28WA AGWA AG notice693 WA residents+20d
  7. NOV 2ME AGME AG noticestates nationwide total 30,709+25d
  8. NOV 2CA AGCA AG noticeno count stated+25d
  9. NOV 5NH AGNH AG noticemost recent · 7 NH residents+28d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 3, 2021
IN AG
Discovered
Jun 3, 2021
MT AG + NH AG + WA AG +1
Data types
Authentication · Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MA AG + NH AG + WA AG +3
Attack vector
Unauthorized Access
MT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

30,709

Sum of filed state slices

1,431· 4.7% of stated

95% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US30,709
WA693
MA612
IN84
NH21
MT11
ME10

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

28 days

Cadence

~1 / 3.5d

vs. multi-state median

4.7× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.