FCG Wealth Management reported a data breach to the Indiana Attorney General. The breach occurred on 2024-08-13 and was reported on 2024-11-12. 4 Indiana residents were affected. 361 individuals affected in total.
Affected (this filing): 361
Clustered 2 filings across 2 jurisdictions · filing window Nov 12, 2024 → Nov 13, 2024. View entity profile → Other incidents for this victim →
incident inc_6f35fc6183084c81 · 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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 13, 2024
When the intrusion reportedly occurred, per the linked filings
Aug 16, 2024
Reported by NEW HAMPSHIRE AG filing
FCG Wealth Management reported a data breach to the Indiana Attorney General. The breach occurred on 2024-08-13 and was reported on 2024-11-12. 4 Indiana residents were affected. 361 individuals affected in total.
Affected (this filing): 361
FCG Wealth Management notified the NH Attorney General of a data security incident where an employee's email mailbox was accessed without authorization between Aug 13-16, 2024. Suspicious activity was detected on Aug 16. One NH resident was notified on Nov 12, 2024. Client PII, including SSN and financial data, may have been exposed. No evidence of misuse was found. Credit monitoring was offered.
Affected (this filing): 1
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.