AxleHire Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2021-02-17. The breach occurred on 1/31/2021. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Feb 17, 2021. View entity profile → Other incidents for this victim →
incident inc_f0724d2de6bf4933 · 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
Jan 31, 2021
When the intrusion reportedly occurred, per the linked filings
Jan 31, 2021
Reported by CALIFORNIA AG filing
AxleHire Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2021-02-17. The breach occurred on 1/31/2021. 1 Montana residents were affected.
Affected (this filing): 1
AxleHire Inc. experienced a data security incident on January 31, 2021, caused by a software glitch during the preparation of 1099 tax forms. The error resulted in some drivers receiving incorrect 1099 forms containing other drivers' personal information, including names, addresses, and Social Security numbers. AxleHire fixed the software issue, sent corrected forms, contacted affected drivers to discard the erroneous documents, and offered two years of complimentary identity monitoring services.
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.