Marr and Company, P.C. reported a data breach to the Montana Attorney General. The breach was reported on 2021-06-02. The breach occurred from 6/19/2020 to 6/23/2020. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Jun 2, 2021 → Jun 13, 2021. View entity profile → Other incidents for this victim →
incident inc_746693a0056a41e1 · 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 19, 2020
When the intrusion reportedly occurred, per the linked filings
May 7, 2021
Reported by MAINE AG filing
Marr and Company, P.C. reported a data breach to the Montana Attorney General. The breach was reported on 2021-06-02. The breach occurred from 6/19/2020 to 6/23/2020. 1 Montana residents were affected.
Affected (this filing): 1
Marr & Company, P.C., a financial services firm, reported a data breach affecting 3,046 individuals. The incident, an external system breach (hacking), occurred between June 19, 2020, and June 23, 2020, but was not discovered until May 7, 2021. The compromised data included names and financial account numbers or credit/debit card numbers along with their security codes, access codes, passwords, or PINs. Affected individuals were notified on June 2, 2021, and those whose Social Security numbers were impacted were offered 12 months of credit monitoring services.
Affected (this filing): 3,046
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.