Confirmed breach. Intrusion Aug 9, 2024–Aug 22, 2024, discovered Oct 23, 2024 — the first regulatory filing landed 30 days later. 1,742 individuals reported across the linked filings.
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.
Regulatory clocksMaine⏱ ME AG >30d · 33dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
1,742
Data types
3
PII · Financial · Government ID
Jurisdictions
2
IN ME
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Aug 9, 2024
When the intrusion reportedly occurred, per the linked filings
75 days
Breach discovered
Oct 23, 2024
Reported by MAINE AG filing
30 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Ladies Professional Golf Association Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-08-09 and was reported on 2024-11-22. 14 Indiana residents were affected. 1,742 individuals affected in total.
An unauthorized actor accessed two LPGA employee email accounts between Aug 19–22, 2024. Discovered Oct 23, 2024, after review of potentially viewed messages confirmed the name, SSN, and financial account number of 2 Maine residents were exposed. Residents notified by mail Nov 22, 2024; one-year Experian IdentityWorks offered. LPGA is enhancing email security.
Affected (this filing): 2
ME AG >30d · 33d
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.