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

St. Joseph’s College of Maine — December 2023 breach

Clustered 12 filings across 12 jurisdictions · filing window Mar 21, 2025 → Mar 27, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

12

Affected · reported

132,610

First → last filing

Mar 21, 2025 → Mar 27, 2025

Merge confidence

100%

incident inc_38b5bf4c748142e1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. Intrusion Dec 15, 2023–Jan 24, 2024, discovered Jan 24, 2024 — the first regulatory filing landed 422 days later (flagged late). 132,610 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 6-day schedule across 12 filings beginning Mar 21, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
422days

Discovered → first regulatory filing

Discovery variance
393days

Range of discovered_at dates across filings

Filing span
6days

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 clocksWashington✗ WA AG >90dVermont⏱ VT AG >14 bdayOregon✓ OR AG ≤45dMaine✓ ME AG ≤30d · 29dMassachusetts✓ MA credit monitoring dueRhode Island✓ RI AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 15, 2023breach begins
Jan 24, 2024discovered · members disagree
notification delay · 422 days
Mar 21, 2025first filing
Mar 27, 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. MAR 21NE AGNE AG noticefirst filing · no count statedday 0
  2. MAR 21OR AGOR AG noticestates nationwide total 126,580day 0
  3. MAR 21CA AGCA AG noticeno count statedday 0
  4. MAR 21IN AGIN AG noticestates nationwide total 132,610day 0
  5. MAR 21MD AGMD AG notice1,462 MD residentsday 0
  6. MAR 21VT AGVT AG noticeno count statedday 0
  7. MAR 21WA AGWA AG notice728 WA residentsday 0
  8. MAR 21ME AGME AG noticestates nationwide total 126,580day 0
  9. MAR 21MT AGMT AG notice135 MT residentsday 0
  10. MAR 25NH AGNH AG notice4,810 NH residents+4d
  11. MAR 26MA AGMA AG notice8,938 MA residents+5d
  12. MAR 27RI AGRI AG noticemost recent · 902 RI residents+6d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 15, 2023
NE AG
Discovered
Jan 24, 2024WA AGFeb 20, 2025NE AG + OR AG + VT AG +4filings disagree on discovery
Data types
Education · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
CA AG + MD AG + VT AG +6
Attack vector
Unauthorized Access
VT 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)

132,610

Sum of filed state slices

40,626· 30.6% of stated

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

US132,610
ME23,203
MA8,938
NH4,810
MD1,462
RI902
WA728
IN448
MT135

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 filing12 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 Jun 12, 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

6 days

Cadence

~1 / 0.5d

vs. multi-state median

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