Clustered 3 filings across 3 jurisdictions · filing window May 13, 2026 → May 14, 2026. View entity profile → Other incidents for this victim →
incident inc_539beb7e068e4593 · 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.
Health (basic) · Identity (basic)
FL IN TX
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 26, 2026
When the intrusion reportedly occurred, per the linked filings
Apr 3, 2026
Reported by TEXAS AG filing
Pivot Health reported to HHS on 2026-05-13 a Hacking/IT Incident affecting 5864 individuals. Breached information located on Network Server. Business Associate present.
Affected (this filing): 5,864
Pivot Health reported a data breach to the Indiana Attorney General. The breach occurred on 2026-02-26 and was reported on 2026-05-13. 92 Indiana residents were affected. 8,391 individuals affected in total.
Affected (this filing): 8,391
Pivot Health based in Miami, Florida, a insurance services entity reported a data breach to the Texas Attorney General. The breach was discovered on 2026-04-03 and reported on 2026-05-14. 1,172 Texas residents were affected. 8,391 individuals affected in total. Types of information involved: Name of individual;Financial Information (e.g. account number, credit or debit card number);Health Insurance Information. Consumers were notified via Posted at company website or special website;U.S. Mail.
Affected (this filing): 1,172
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.