DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed12 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedbianlianhigh sensitivity
Merged incident · 12 filings

Dordt University — April 2024 breach

Clustered 12 filings across 11 jurisdictions · filing window May 16, 2024 → Jul 15, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

10

Affected · reported

34,251

First → last filing

May 16, 2024 → Jul 15, 2025

Merge confidence

100%

incident inc_01f984d13594471b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Apr 21, 2024–May 16, 2024, discovered Apr 21, 2024 — the first regulatory filing landed 446 days later (flagged late). 34,251 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 425-day schedule across 10 filings beginning May 16, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
446days

Discovered → first regulatory filing

Discovery variance
424days

Range of discovered_at dates across filings

Leak precedence
421days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
425days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 21, 2024breach begins
Apr 21, 2024discovered · members disagree
notification delay · 446 days
Jul 11, 2025first filing
Jul 15, 2025most 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. MAY 16Leak sitebianlian postfirst filing · attacker claim · unverifiedday 0
  2. JUN 13Leak sitebianlian postattacker claim · unverified+29d
  3. JUL 11IA AGIA AG notice10,709 IA residents+421d
  4. JUL 11VT AGVT AG noticeno count stated+421d
  5. JUL 11CA AGCA AG noticeno count stated+421d
  6. JUL 11ME AGME AG noticestates nationwide total 34,251+421d
  7. JUL 11MT AGMT AG notice342 MT residents+421d
  8. JUL 11NE AGNE AG noticeno count stated+421d
  9. JUL 11WA AGWA AG notice3,711 WA residents+421d
  10. JUL 11IN AGIN AG noticestates nationwide total 34,251+421d
  11. JUL 12MA AGMA AG notice96 MA residents+422d
  12. JUL 15TX AGTX AG noticemost recent · states nationwide total 34,251+425d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 21, 2024 – May 16, 2024
IA AG
Discovered
Apr 21, 2024NE AGMay 16, 2024IA AG + MT AGMay 28, 2024WA AGJun 19, 2025ME AG + TX AGfilings disagree on discovery
Data types
Education · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI
IA AG + VT AG + CA AG +6
Attack vector
Unauthorized Access
IA 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)

34,251

Sum of filed state slices

16,110· 47.0% of stated

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

US34,251
IA10,709
WA3,711
TX716
IN513
MT342
MA96
ME23

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 claim2 members

Attacker assertion only. Establishes: claim date, group, alleged victim.

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 May 24, 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

425 days

Cadence

~1 / 38.6d

vs. multi-state median

53.1× 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.