Clustered 2 filings across 1 jurisdiction · filing window Mar 30, 2026 → Mar 31, 2026. View entity profile → Other incidents for this victim →
incident inc_4c7fb57d88314b9a · merge_method deterministic · confidence 100%
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
TX
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 30, 2025
Reported by TEXAS AG filing
Austin Plastic and Reconstructive Surgery reported to HHS on 2026-03-30 a Hacking/IT Incident affecting 4266 individuals. Breached information located on Network Server.
Affected (this filing): 4,266
Austin Plastic and Reconstructive Surgery based in Bloomfield Hills, Michigan, a healthcare – medical provider entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-06-30 and reported on 2026-03-31. 4,041 Texas residents were affected. 4,266 individuals affected in total. Types of information involved: Name of individual;Address;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);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;Broadcast on Texas-wide Media.
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): 4,041