Focus Financial Partners LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2026-01-30 and was reported on 2026-05-20. 8 Indiana residents were affected. 184 individuals affected in total.
Affected (this filing): 184
Clustered 2 filings across 2 jurisdictions · filing window May 20, 2026 → Jun 1, 2026. View entity profile → Other incidents for this victim →
incident inc_5e8557e69c9d43aa · merge_method deterministic · confidence 95%
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.
Identity (basic) · Government ID
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 30, 2026
When the intrusion reportedly occurred, per the linked filings
Jan 30, 2026
Reported by NEW HAMPSHIRE AG filing
Focus Financial Partners LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2026-01-30 and was reported on 2026-05-20. 8 Indiana residents were affected. 184 individuals affected in total.
Affected (this filing): 184
Focus Financial Partners, LLC notified the New Hampshire Attorney General of a data security incident. On January 30, 2026, suspicious activity was detected, leading to an investigation that determined an unauthorized individual accessed emails containing personal information, including names, Social Security numbers, driver's license numbers, and addresses. Two New Hampshire residents were notified on May 20, 2026, and offered credit monitoring services.
Affected (this filing): 2
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.