Peter Brasseler Holdings, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2022-08-17. The breach occurred on 6/24/2022. 14 Montana residents were affected.
Affected (this filing): 14
Clustered 2 filings across 2 jurisdictions · filing window Aug 17, 2022 → Aug 19, 2022. View entity profile → Other incidents for this victim →
incident inc_ae91142164f34773 · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 24, 2022
When the intrusion reportedly occurred, per the linked filings
Jul 18, 2022
Reported by MAINE AG filing
Peter Brasseler Holdings, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2022-08-17. The breach occurred on 6/24/2022. 14 Montana residents were affected.
Affected (this filing): 14
Peter Brasseler Holdings, LLC and its subsidiaries, Brasseler U.S.A. Dental, LLC and Brasseler U.S.A. Medical, LLC, reported a data breach affecting 4 Maine residents. The breach, which was an external system hack, occurred on June 24, 2022, and was discovered on July 18, 2022. The compromised information included financial account numbers or credit/debit card numbers along with their security codes, access codes, passwords, or PINs. The company began notifying affected individuals on August 17, 2022, and offered 24 months of identity theft protection and 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.