Land Betterment Corporation reported a data breach to the Indiana Attorney General. The breach occurred on 2026-01-10 and was reported on 2026-02-03. 1 Indiana residents were affected. 9 individuals affected in total.
Affected (this filing): 9
Clustered 2 filings across 2 jurisdictions · filed Feb 3, 2026. View entity profile → Other incidents for this victim →
incident inc_7c8b3e811e89446f · 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
Jan 10, 2026
When the intrusion reportedly occurred, per the linked filings
Jan 10, 2026
Reported by MAINE AG filing
Land Betterment Corporation reported a data breach to the Indiana Attorney General. The breach occurred on 2026-01-10 and was reported on 2026-02-03. 1 Indiana residents were affected. 9 individuals affected in total.
Affected (this filing): 9
On January 10, 2026, an unknown individual(s) breached Land Betterment Corporation's HR information system (Paychex Flex), accessing personal employee information including names, Social Security numbers, bank account numbers, and pay rates. A total of 9 individuals were affected nationally, with 1 Maine resident impacted. Law enforcement was notified and remedial measures were implemented. No identity theft protection services were 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.