DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed8 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 8 filings

Roosevelt University — May 2023 breach

Clustered 8 filings across 8 jurisdictions · filing window Jun 28, 2023 → Jul 3, 2023 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

47,877

First → last dated filing

Jun 28, 2023 → Jul 3, 2023

Merge confidence

100%

incident inc_f46fe2ed3e714ed6 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe unauthorized access. Intrusion May 1, 2023, discovered May 1, 2023. 47,877 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 5-day schedule across 7 dated filings beginning Jun 28, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
24days

Range of discovered_at dates across filings

Filing span
5days

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 clocksMaine⏱ ME AG >30d · 34dVermont⏱ VT AG >14 bdayMassachusetts✓ MA credit monitoring dueCalifornia✓ CA 60-day OK · 58dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 1, 2023breach begins
May 1, 2023discovered · members disagree
Jun 28, 2023first dated filing
Jul 3, 2023most 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 about this breach

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JUN 28MA AGMA AG noticefirst filing · 197 MA residentsday 0
  3. JUN 28ME AGME AG noticestates nationwide total 47,877day 0
  4. JUN 28VT AGVT AG noticeno count statedday 0
  5. JUN 28MT AGMT AG notice10 MT residentsday 0
  6. JUN 28CA AGCA AG noticeno count statedday 0
  7. JUN 28IN AGIN AG noticestates nationwide total 47,877day 0
  8. JUL 3NH AGNH AG noticemost recent · 39 NH residents+5d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 1, 2023
ME AG
Discovered
May 1, 2023VT AG + MT AG + CA AG +1May 25, 2023IL AG + ME AGfilings disagree on discovery
Data types
Education · Financial account · Identity (basic) · Government ID · PII
MA AG + ME AG + VT 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)

47,877

Sum of filed state slices

979· 2.0% of stated

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

US47,877
IN710
MA197
NH39
ME23
MT10

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

5 days

Cadence

~1 / 0.8d

vs. multi-state median

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