Westwood Country Club reported a data breach to the Indiana Attorney General. The breach occurred on 2024-10-09 and was reported on 2025-03-24. 8 Indiana residents were affected. 3,203 individuals affected in total.
Affected (this filing): 3,203
Clustered 2 filings across 2 jurisdictions · filed Mar 24, 2025. View entity profile → Other incidents for this victim →
incident inc_e952a6ccf10840d6 · 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 ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 9, 2024
When the intrusion reportedly occurred, per the linked filings
Mar 14, 2025
Reported by MAINE AG filing
Westwood Country Club reported a data breach to the Indiana Attorney General. The breach occurred on 2024-10-09 and was reported on 2025-03-24. 8 Indiana residents were affected. 3,203 individuals affected in total.
Affected (this filing): 3,203
Westwood Country Club reported an external system breach (hacking) that occurred on October 9, 2024, and was discovered on March 14, 2025. The breach affected 3,203 individuals in total, with one Maine resident impacted. Notification letters were sent to affected consumers on March 24, 2025, along with an offer for 24 months of complimentary credit monitoring and identity protection services.
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.