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

Renton School District — July 2023 breach

Clustered 10 filings across 8 jurisdictions · filing window Aug 3, 2023 → Feb 29, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

7

Affected · reported

30,373

First → last filing

Aug 3, 2023 → Feb 29, 2024

Merge confidence

100%

incident inc_87b56c6ea795471f · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings, 1 press report and 2 unverified claims. Intrusion Jul 13, 2023–Aug 3, 2023, discovered Aug 3, 2023 — the first regulatory filing landed 210 days later (flagged late). 30,373 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 6 more. Notifications rolled out on a 210-day schedule across 7 filings beginning Aug 3, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
210days

Discovered → first regulatory filing

Discovery variance
181days

Range of discovered_at dates across filings

Leak precedence
210days 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
210days

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 >180dVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Jul 13, 2023breach begins
Aug 3, 2023discovered · members disagree
notification delay · 210 days
Feb 29, 2024first filing
—watching for filings

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

Member cascade — every filing about this breach

  1. AUG 3Leak siteakira postfirst filing · attacker claim · unverifiedday 0
  2. AUG 30Leak siteakira postattacker claim · unverified+27d
  3. FEB 29ME AGME AG noticestates nationwide total 30,373+210d
  4. FEB 29NH AGNH AG notice3 NH residents+210d
  5. FEB 29MT AGMT AG notice26 MT residents+210d
  6. FEB 29IN AGIN AG noticestates nationwide total 30,373+210d
  7. FEB 29WA AGWA AG notice18,891 WA residents+210d
  8. FEB 29VT AGVT AG noticeno count stated+210d
  9. FEB 29MA AGMA AG noticemost recent · 10 MA residents+210d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 13, 2023
ME AG
Discovered
Aug 3, 2023NH AG + MT AG + WA AG +1Jan 31, 2024ME AGfilings disagree on discovery
Data types
Authentication · Credentials · Education · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
ME AG + NH AG + MT AG +3
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)

30,373

Sum of filed state slices

18,941· 62.4% of stated

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

US30,373
WA18,891
MT26
MA10
IN7
ME4
NH3

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

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

State AG / regulator filing7 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
human
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

210 days

Cadence

~1 / 23.3d

vs. multi-state median

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