All data will be published on March 5, 2025.With over 300 GB of files stolen. During the 2019-20 season, the Houston Symphony celebrates its sixth season with Music Director Andrés Orozco-Estrada and continues its second century as one of Am ...
Clustered 2 filings across 2 jurisdictions · filing window Feb 28, 2025 → Aug 22, 2025. View entity profile → Other incidents for this victim →
incident inc_1ceeefd1a8c94696 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
TX
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
All data will be published on March 5, 2025.With over 300 GB of files stolen. During the 2019-20 season, the Houston Symphony celebrates its sixth season with Music Director Andrés Orozco-Estrada and continues its second century as one of Am ...
Jul 2, 2025
Reported by TEXAS AG filing
Houston Symphony Society based in Houston, Texas, a nonprofit organization entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-07-02 and reported on 2025-08-22. 1,874 Texas residents were affected. 2,617 individuals affected in total. Types of information involved: Social Security Number Information;Driver’s License number;Government-issued ID number (e.g. passport, state ID card);Financial Information (e.g. account number, credit or debit card number);Health Insurance Information;Date of Birth. Consumers were notified via U.S. Mail.
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.
Affected (this filing): 1,874