Onondaga County Chapter, NYSARC, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2021-11-30. The breach occurred from 8/15/2021 to 9/21/2021. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Nov 30, 2021. View entity profile → Other incidents for this victim →
incident inc_9b519c8c28de41b7 · 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) · Government ID
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 15, 2021
When the intrusion reportedly occurred, per the linked filings
Nov 16, 2021
Reported by MAINE AG filing
Onondaga County Chapter, NYSARC, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2021-11-30. The breach occurred from 8/15/2021 to 9/21/2021. 1 Montana residents were affected.
Affected (this filing): 1
Onondaga County Chapter, NYSARC, Inc. reported an external system breach that was discovered on November 16, 2021. The incident, which occurred on August 15, 2021, affected 2 Maine residents. The compromised information included names and Social Security numbers. Affected individuals were notified on November 30, 2021, and offered 12 months of identity protection and credit monitoring services through Equifax.
Affected (this filing): 2
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.