Cooper Aerobics Enterprises, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2024-01-05. The breach occurred on 2/3/2023. 93 Montana residents were affected.
Affected (this filing): 93
Clustered 2 filings across 2 jurisdictions · filed Jan 5, 2024. View entity profile → Other incidents for this victim →
incident inc_de3a8505fe334229 · 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
Feb 3, 2023
When the intrusion reportedly occurred, per the linked filings
Feb 3, 2023
Reported by CALIFORNIA AG filing
Cooper Aerobics Enterprises, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2024-01-05. The breach occurred on 2/3/2023. 93 Montana residents were affected.
Affected (this filing): 93
Cooper Aerobics Enterprises, Inc. notified the California AG of a cybersecurity incident where unauthorized access occurred on February 3, 2023. The company became aware of the incident on the same date. Forensic investigation confirmed potential access or removal of sensitive data, including personal and medical information. The threat was contained by disabling unauthorized access. The company engaged external cybersecurity professionals and conducted a manual review of impacted servers. Affected individuals are offered credit monitoring and identity theft protection 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.