BlueForce, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2022-04-21. The breach occurred on 5/4/2021. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Apr 21, 2022. View entity profile → Other incidents for this victim →
incident inc_c23dd82961384424 · 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
May 4, 2021
When the intrusion reportedly occurred, per the linked filings
Mar 8, 2022
Reported by MAINE AG filing
BlueForce, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2022-04-21. The breach occurred on 5/4/2021. 1 Montana residents were affected.
Affected (this filing): 1
BlueForce, Inc. experienced an external system breach on May 4, 2021, which was discovered on March 8, 2022. The breach compromised the names and financial account or credit/debit card numbers (with access codes) of 2,138 individuals, including 4 Maine residents. The company began notifying affected individuals on April 21, 2022, and offered 12 months of credit monitoring and identity restoration services through Experian.
Affected (this filing): 4
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.