Bill Pollard, JR CPA reported a data breach to the Montana Attorney General. The breach was reported on 2022-06-27. The breach occurred on 3/31/2022. 7 Montana residents were affected.
Affected (this filing): 7
Clustered 2 filings across 2 jurisdictions · filing window Jun 27, 2022 → Jun 28, 2022. View entity profile → Other incidents for this victim →
incident inc_2ba8c3d5ca994eb2 · merge_method deterministic · 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.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 31, 2022
When the intrusion reportedly occurred, per the linked filings
Mar 31, 2022
Reported by CALIFORNIA AG filing
Bill Pollard, JR CPA reported a data breach to the Montana Attorney General. The breach was reported on 2022-06-27. The breach occurred on 3/31/2022. 7 Montana residents were affected.
Affected (this filing): 7
Bill Pollard, Jr CPA experienced a data breach discovered on March 31, 2022, involving malicious code in company software. Attackers exfiltrated a file containing personal information including names, addresses, SSNs, dates of birth, and bank account numbers. The company engaged forensic experts, implemented security enhancements (endpoint protection, firewalls, encryption), and notified law enforcement (FBI, IRS, CFTB). Affected individuals were offered two years of credit monitoring.
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.