Clustered 3 filings across 3 jurisdictions · filing window May 9, 2023 → May 24, 2023. View entity profile → Other incidents for this victim →
incident inc_5c48d026f5864c80 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
Government ID · Identity (basic)
ME MT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 12, 2023 → Feb 24, 2023
When the intrusion reportedly occurred, per the linked filings
Apr 30, 2023
Reported by MAINE AG filing
Their mission - to teach, to learn, to create, to to inspire, to empower and to serve. We would add to disclose. Recently they have fulfilled a data mission. A 'best value' of national universities value it's students and teachers personal and it will be available for downloading in our soon. Our offer with a relatively affordable for saving their internal data was denied.
Mercer University reported an external system breach (hacking) occurring between February 12 and 24, 2023, discovered on April 30, 2023. The incident affected 93,512 individuals, including 21 Maine residents. Acquired data included names combined with driver's license numbers. The university provided written notification and offered one year of credit monitoring through Experian.
Affected (this filing): 93,512
Mercer University reported a data breach to the Montana Attorney General. The breach was reported on 2023-05-24. The breach occurred from 2/12/2023 to 2/24/2023. 15 Montana residents were affected.
Affected (this filing):
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.