Clustered 2 filings across 2 jurisdictions · filing window Aug 5, 2025 → Aug 7, 2025. View entity profile → Other incidents for this victim →
incident inc_bd589c60bbf84c7a · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
ME TX
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.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 31, 2025
When the intrusion reportedly occurred, per the linked filings
May 25, 2025
Reported by MAINE AG, TEXAS AG filings
Nova Recovery Center experienced an external system breach on March 31, 2025, which was discovered on May 25, 2025. The breach affected 7,713 individuals, including 3 Maine residents. Notification to affected consumers was sent on August 1, 2025, and the company offered 24 months of identity theft protection services through Kroll.
Affected (this filing): 3
Nova Recovery LLC d/b/a Nova Recovery Center based in Wimberley, Texas, a healthcare – medical provider entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-05-25 and reported on 2025-08-07. 5,518 Texas residents were affected. 7,712 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);Medical Information;Health Insurance Information;Date of Birth. Consumers were notified via Notice by publication in print media;Posted at company website or special website;U.S. Mail.
Affected (this filing): 5,518
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.