Confirmed breach. discovered Jun 26, 2026 — the first regulatory filing landed 18 days later (flagged late). 12,097 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 clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
12,097
Data types
2
Government ID · PII
Jurisdictions
2
TX VT
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach discoveredAG web form
Jun 26, 2026
Reported by TEXAS AG filing
🍁Vermont State AGFirst filinglinked via multistate filing link · 100%
Fiesta Insurance Franchise Corporation reported a data breach to the Vermont Attorney General. The breach was reported to the AGO on 2026-07-14. The reporting organization type is Insurance. 5 Vermont residents were affected. Categories of data breached: Social Security Numbers, Government ID Numbers.
Fiesta Insurance Franchise Corporation based in Las Vegas, Nevada, a insurance services entity reported a data breach to the Texas Attorney General. The breach was discovered on 2026-06-26 and reported on 2026-07-14. 12,097 Texas residents were affected. 160,151 individuals affected in total. Types of information involved: Name of individual;Address;Social Security Number Information;Driver’s License number;Financial Information (e.g. account number, credit or debit card number). Consumers were notified via Posted at company website or special website;U.S. Mail.
Affected (this filing): 12,097
Leak >180d
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.