Carriage Purchaser, Inc. d/b/a PS Logistics reported a data breach to the Montana Attorney General. The breach was reported on 2024-12-19. The breach occurred from 02/20/2024 to 02202024. 5 Montana residents were affected.
Affected (this filing): 5
Clustered 2 filings across 2 jurisdictions · filing window Dec 19, 2024 → Dec 20, 2024. View entity profile → Other incidents for this victim →
incident inc_eb2f7e36e77b45bc · 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.
MT VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 20, 2024
When the intrusion reportedly occurred, per the linked filings
Feb 20, 2024
Reported by VERMONT AG filing
Carriage Purchaser, Inc. d/b/a PS Logistics reported a data breach to the Montana Attorney General. The breach was reported on 2024-12-19. The breach occurred from 02/20/2024 to 02202024. 5 Montana residents were affected.
Affected (this filing): 5
Carriage Purchase, Inc. d/b/a PS Logistics notified consumers of a data breach occurring on February 20, 2024. Unauthorized access to the network resulted in the removal of files containing personal information, including names, SSNs, and financial account numbers. PS Logistics engaged external cybersecurity professionals for forensic investigation and is offering 12 months of complimentary identity theft protection services through Equifax to affected individuals.
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.