Borough of Haledon Police Department reported a data breach to the Montana Attorney General. The breach was reported on 2021-08-12. The breach occurred from 6/2/2020 to 7/10/2020. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filed Aug 12, 2021. View entity profile → Other incidents for this victim →
incident inc_8af9fabc7bdc4f76 · 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
Jun 2, 2020
When the intrusion reportedly occurred, per the linked filings
Mar 11, 2021
Reported by MAINE AG filing
Borough of Haledon Police Department reported a data breach to the Montana Attorney General. The breach was reported on 2021-08-12. The breach occurred from 6/2/2020 to 7/10/2020. 2 Montana residents were affected.
Affected (this filing): 2
The Borough of Haledon New Jersey Police Department reported an external system breach that occurred on June 2, 2020, and was discovered on March 11, 2021. The breach affected 5 Maine residents, compromising their names and Social Security numbers. Notification to affected individuals was sent on August 12, 2021.
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.