Confirmed breach. discovered Sep 26, 2025 — the first regulatory filing landed 52 days later (flagged late). 7,295 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksTexas✗ TX AG >30dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
7,295
Data types
1
PII
Jurisdictions
1
TX
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
CDS in Texas based in San Antonio, Texas, a other entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-09-26 and reported on 2025-11-17. 7,295 Texas residents were affected. Types of information involved: Name of individual;Other. Consumers were notified via Email.
Affected (this filing): 7,295
TX AG >30d
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.