Platinum Performance, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2022-08-31. The breach occurred from 9/8/2021 to 5/6/2022. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filed Aug 31, 2022. View entity profile → Other incidents for this victim →
incident inc_49e1992194154e8e · 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
Sep 8, 2021
When the intrusion reportedly occurred, per the linked filings
May 6, 2022
Reported by MAINE AG filing
Platinum Performance, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2022-08-31. The breach occurred from 9/8/2021 to 5/6/2022. 2 Montana residents were affected.
Affected (this filing): 2
Platinum Performance, Inc. reported an external system breach (hacking) occurring on September 8, 2021, discovered on May 6, 2022. The incident compromised the names and Social Security Numbers of 295 individuals, including one Maine resident. Platinum Performance sent written notifications on August 31, 2022, and provided 24 months of identity theft monitoring services through Kroll to affected individuals.
Affected (this filing): 295
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.