Homeschool Legal Defense Association reported a data breach to the Montana Attorney General. The breach was reported on 2023-01-30. The breach occurred on 2/2/2022. 3 Montana residents were affected.
Affected (this filing): 3
Clustered 2 filings across 2 jurisdictions · filed Jan 30, 2023. View entity profile → Other incidents for this victim →
incident inc_ac18ab86a84040db · merge_method llm · confidence 44%
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.
Identity (basic) · Financial account · Financial credentials
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 2, 2022
When the intrusion reportedly occurred, per the linked filings
Feb 2, 2022
Reported by MAINE AG filing
Homeschool Legal Defense Association reported a data breach to the Montana Attorney General. The breach was reported on 2023-01-30. The breach occurred on 2/2/2022. 3 Montana residents were affected.
Affected (this filing): 3
Homeschool Legal Defense Association, a non-profit organization, experienced an external system breach (hacking) on January 31, 2022, which was discovered on February 2, 2022. The breach affected 5 Maine residents, compromising their names and financial account or credit/debit card numbers along with access codes. Affected individuals were notified on January 19, 2023, and offered 12 months of credit monitoring and identity restoration services through Equifax.
Affected (this filing): 5
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.