Clustered 2 filings across 2 jurisdictions · filing window Sep 10, 2025 → Sep 23, 2025. View entity profile → Other incidents for this victim →
incident inc_7cd2bc2159894e0a · merge_method llm · confidence 45%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
Government ID · PHI · PII
IN TX
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 9, 2025
When the intrusion reportedly occurred, per the linked filings
Aug 25, 2025
Reported by TEXAS AG filing
Bosque County, Texas reported a data breach to the Indiana Attorney General. The breach occurred on 2025-07-09 and was reported on 2025-09-10. 1 Indiana residents were affected. 1,939 individuals affected in total.
Affected (this filing): 1,939
Bosque County, Texas based in Meridian, Texas, a governmental entity entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-08-25 and reported on 2025-09-23. 2,079 Texas residents were affected. 2,123 individuals affected in total. Types of information involved: Name of individual;Address;Social Security Number Information;Driver’s License number;Medical Information;Date of Birth. Consumers were notified via Posted at company website or special website;U.S. Mail.
Affected (this filing): 2,079
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.