Confirmed breach. Intrusion Dec 1, 2022–Dec 31, 2022, discovered Dec 1, 2022 — the first regulatory filing landed 257 days later (flagged late). 1 individuals reported across the linked filings.
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.
Regulatory clocksCalifornia✗ CA 60-day late · 253dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
1
Data types
—
Jurisdictions
2
CA MT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Dec 1, 2022
When the intrusion reportedly occurred, per the linked filings
Community Action Partnership of Madera County reported a data breach to the Montana Attorney General. The breach was reported on 2023-08-15. The breach occurred from 12/1/2022 to 12/31/2022. 1 Montana residents were affected.
Affected (this filing): 1
🐻California State AGMost recentlinked via multistate filing link · 100%
Community Action Partnership of Madera County (CAPMC) notified the California AG of a data breach discovered in December 2022. The incident involved a network disruption. Investigation concluded in June 2023 that personal information including name, address, DOB, SSN, driver's license, and health insurance info may have been impacted. CAPMC engaged cybersecurity experts and implemented additional security measures. Affected individuals are offered 12 months of credit monitoring.
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.