Hebron Academy reported a data breach to the Montana Attorney General. The breach was reported on 2021-01-27. The breach occurred from 2/7/2020 to 5/20/2020. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Jan 27, 2021 → Feb 1, 2021. View entity profile → Other incidents for this victim →
incident inc_e2882334239b40b9 · 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
Feb 7, 2020
When the intrusion reportedly occurred, per the linked filings
Jan 5, 2021
Reported by MAINE AG filing
Hebron Academy reported a data breach to the Montana Attorney General. The breach was reported on 2021-01-27. The breach occurred from 2/7/2020 to 5/20/2020. 1 Montana residents were affected.
Affected (this filing): 1
Hebron Academy, an educational institution, reported a data breach affecting 103 Maine residents. The breach, which occurred between February 7, 2020, and May 20, 2020, was discovered on January 5, 2021. The incident was categorized as an external system breach or hacking, resulting in the compromise of names and Social Security numbers. Affected individuals were notified on January 28, 2021, and offered 24 months of complimentary credit monitoring services through CyberScout.
Affected (this filing): 103
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.