Clustered 2 filings across 1 jurisdiction · filing window Jun 24, 2025 → Jul 17, 2025. View entity profile → Other incidents for this victim →
incident inc_06201b74d92f4efb · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Government ID · Identity (basic)
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
CA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 25, 2025
When the intrusion reportedly occurred, per the linked filings
Apr 25, 2025
Reported by CALIFORNIA AG filing
The California Franchise Tax Board disclosed an inadvertent data disclosure on April 25, 2025, caused by a programming error. An Order to Withhold Notice containing names, addresses, and Social Security Numbers was erroneously sent to a third-party payor. The FTB fixed the issue, instructed the payor to destroy the data, and offered free credit monitoring to affected individuals.
Jun 26, 2025
Reported by CALIFORNIA AG filing
The California Franchise Tax Board disclosed an inadvertent data incident on June 26, 2025, caused by a programming issue. An Order to Withhold Notice containing names, addresses, and Social Security Numbers was erroneously sent to a third-party payor. The FTB fixed the programming issue, instructed the payor to destroy the notice, and is offering free credit monitoring 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.