DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SitePressState AGConfirmed7 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedinterlockhigh sensitivity
Merged incident · 7 filings

Kalamazoo Public School District — April 2025 breach

Clustered 7 filings across 6 jurisdictions · filing window Apr 26, 2025 → Jul 14, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

5

Affected · reported

8,592

First → last filing

Apr 26, 2025 → Jul 14, 2025

Merge confidence

100%

incident inc_791e6b56a6214789 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings, 1 press report and 1 unverified claim. The filings describe unauthorized access. Intrusion Apr 30, 2025, discovered Apr 30, 2025 — the first regulatory filing landed 69 days later. 8,592 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 79-day schedule across 5 filings beginning Apr 26, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
69days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
73days 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
79days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine⏱ ME AG >30d · 69dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 30, 2025breach begins
Apr 30, 2025discovered
notification delay · 69 days
Jul 8, 2025first filing
Jul 14, 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. APR 26Leak siteinterlock postfirst filing · attacker claim · unverifiedday 0
  2. JUL 8ME AGME AG notice2 ME residents+73d
  3. JUL 8IN AGIN AG noticestates nationwide total 8,592+73d
  4. JUL 8MA AGMA AG notice14 MA residents+73d
  5. JUL 8NE AGNE AG noticeno count stated+73d
  6. JUL 14NH AGNH AG noticemost recent · 1 NH residents+79d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 30, 2025
ME AG
Discovered
Apr 30, 2025
ME AG + NE AG + NH AG
Data types
Identity (basic) · Government ID
ME AG + NE AG + NH AG +1
Attack vector
Unauthorized Access
ME 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)

8,592

Sum of filed state slices

100· 1.2% of stated

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

US8,592
IN83
MA14
ME2
NH1

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 claim1 member

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

Press / market report1 member

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing5 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 Aug 22, 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

79 days

Cadence

~1 / 13.2d

vs. multi-state median

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