Greensboro College reported a data breach to the Montana Attorney General. The breach was reported on 2024-02-29. The breach occurred from 8/10/2023 to 8/21/2023. 11 Montana residents were affected.
Affected (this filing): 11
Clustered 2 filings across 2 jurisdictions · filed Feb 29, 2024. View entity profile → Other incidents for this victim →
incident inc_b35dede99c1b4211 · merge_method human · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 10, 2023
When the intrusion reportedly occurred, per the linked filings
Feb 5, 2024
Reported by MAINE AG filing
Greensboro College reported a data breach to the Montana Attorney General. The breach was reported on 2024-02-29. The breach occurred from 8/10/2023 to 8/21/2023. 11 Montana residents were affected.
Affected (this filing): 11
Greensboro College, an educational institution in North Carolina, reported an external system breach (hacking) occurring on August 10, 2023, discovered on February 5, 2024. The incident affected 52,569 individuals, including 46 Maine residents. Acquired data included names and financial account or credit/debit card numbers (with security codes/PINs). The College provided written notification on February 29, 2024, and offered 24 months of credit monitoring through Epiq/TransUnion.
Affected (this filing): 52,569
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.