Connor Group reported a data breach to the Montana Attorney General. The breach was reported on 2021-03-19. The breach occurred from 8/8/2020 to 9/11/2020. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Mar 19, 2021 → Mar 20, 2021. View entity profile → Other incidents for this victim →
incident inc_0f785d0a14da4844 · 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 8, 2020
When the intrusion reportedly occurred, per the linked filings
Feb 18, 2021
Reported by MAINE AG filing
Connor Group reported a data breach to the Montana Attorney General. The breach was reported on 2021-03-19. The breach occurred from 8/8/2020 to 9/11/2020. 1 Montana residents were affected.
Affected (this filing): 1
Connor Group, a commercial entity, experienced an external system breach that occurred from August 8, 2020, to September 11, 2020. The breach was discovered on February 18, 2021. The compromised information includes names and Social Security Numbers. A total of 18,424 individuals were affected, including 3 Maine residents. The company provided written notification to the affected Maine residents on March 19, 2021, and offered 12 months of identity theft protection services through Kroll.
Affected (this filing): 3
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.