Ivanhoe Club reported a data breach to the Indiana Attorney General. The breach occurred on 2024-10-11 and was reported on 2025-06-17. 26 Indiana residents were affected. 4,743 individuals affected in total.
Affected (this filing): 4,743
Clustered 2 filings across 2 jurisdictions · filing window Jun 17, 2025 → Jun 23, 2025. View entity profile → Other incidents for this victim →
incident inc_a34697b86f9943cc · 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
Oct 11, 2024
When the intrusion reportedly occurred, per the linked filings
Oct 11, 2024
Reported by NEW HAMPSHIRE AG filing
Ivanhoe Club reported a data breach to the Indiana Attorney General. The breach occurred on 2024-10-11 and was reported on 2025-06-17. 26 Indiana residents were affected. 4,743 individuals affected in total.
Affected (this filing): 4,743
Ivanhoe Club reported a data privacy incident on June 17, 2025, discovered on October 11, 2024. Unauthorized access to network files resulted in the exposure of names and Social Security numbers for one New Hampshire resident. Ivanhoe engaged law enforcement and third-party specialists, secured the network, and offered 12 months of credit monitoring.
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.