DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed10 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 10 filings

Herff Jones, Inc. — August 2020 breach

Clustered 10 filings across 10 jurisdictions · filing window Jun 15, 2021 → Jun 21, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

1,091,049

First → last filing

Jun 15, 2021 → Jun 21, 2021

Merge confidence

100%

incident inc_1a4cdd67082d4c5f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Aug 16, 2020–Apr 29, 2021, discovered Apr 7, 2021 — the first regulatory filing landed 69 days later. 1,091,049 individuals reported across the linked filings. Data reported: Financial account, Identity (basic), PII, and 1 more. Notifications rolled out on a 6-day schedule across 10 filings beginning Jun 15, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
69days

Discovered → first regulatory filing

Discovery variance
48days

Range of discovered_at dates across filings

Filing span
6days

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 >30dOregon✓ OR AG ≤45dMaine✓ ME AG ≤30d · 23dHawaii✓ HI CRA notice dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Incident timeline

Aug 16, 2020breach begins
Apr 7, 2021discovered · members disagree
notification delay · 69 days
Jun 15, 2021first filing
Jun 21, 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. JUN 15DE AGDE AG noticefirst filing · no count statedday 0
  2. JUN 15IN AGIN AG noticestates nationwide total 1,091,049day 0
  3. JUN 15MT AGMT AG notice2,184 MT residentsday 0
  4. JUN 16CA AGCA AG noticeno count stated+1d
  5. JUN 16OR AGOR AG noticeno count stated+1d
  6. JUN 17MA AGMA AG notice13,658 MA residents+2d
  7. JUN 17ME AGME AG noticestates nationwide total 1,091,049+2d
  8. JUN 18WA AGWA AG notice17,316 WA residents+3d
  9. JUN 18HI AGHI AG notice3,373 HI residents+3d
  10. JUN 21SC AGSC AG noticemost recent · 17,709 SC residents+6d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 15, 2020
IN AG
Discovered
Apr 7, 2021DE AG + MT AG + CA AG +2May 25, 2021OR AG + ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · PCI · PII
DE AG + MT AG + CA AG +4
Attack vector
Unauthorized Access
DE 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)

1,091,049

Sum of filed state slices

101,549· 9.3% of stated

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

US1,091,049
IN46,994
SC17,709
WA17,316
MA13,658
HI3,373
MT2,184
ME315

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 filing10 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

6 days

Cadence

~1 / 0.7d

vs. multi-state median

1.3× faster

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.