DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed7 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedrhysidahigh sensitivity
Merged incident · 7 records

Maryville Academy — July 2024 breach

Clustered 7 records across 5 jurisdictions: 6 filings and 1 leak-site claim · filing window Aug 23, 2024 → Sep 1, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 records

States

5

Affected · reported

513

First → last dated filing

Aug 23, 2024 → Sep 1, 2026

Merge confidence

100%

incident inc_0ebba8abc2e9402b · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jul 13, 2024, discovered Jul 15, 2024. 513 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 2 more. Notifications rolled out on a 739-day schedule across 5 dated filings beginning Aug 23, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
739days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dIowa✓ IA AG ≤5 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 13, 2024breach begins
Jul 15, 2024discovered
Aug 23, 2024first dated filing
Sep 1, 2026most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. AUG 1IL AGIL AG noticefiling day not on record · no count stated—
  2. AUG 5Leak siterhysida postfirst record · attacker claim · unverifiedday 0
  3. AUG 23IN AGIN AG noticestates nationwide total 513+18d
  4. SEP 13HHS OCRHHS OCR noticestates nationwide total 500+39d
  5. JUN 12MA AGMA AG notice33 MA residents+311d
  6. AUG 31IA AGIA AG notice15 IA residents+756d
  7. SEP 1VT AGVT AG noticemost recent · 1 VT residents+757d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 13, 2024
IN AG
Discovered
Jul 15, 2024· 2d undetected
IL AG + IA AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
IL AG + MA AG + IA AG +2
Attack vector
Unauthorized Access
HHS OCR

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)

513

Sum of filed state slices

50· 9.7% of stated

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

US513
MA33
IA15
IN1
VT1

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 report

No press coverage linked yet.

State AG / regulator filing6 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 Oct 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

739 days

Cadence

~1 / 184.8d

vs. multi-state median

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