Foundation Wellness reported a data breach to the Montana Attorney General. The breach was reported on 2022-01-07. The breach occurred from 9/7/2021 to 10/4/2021. 10 Montana residents were affected.
Affected (this filing): 10
Clustered 2 filings across 2 jurisdictions · filing window Jan 7, 2022 → Jan 14, 2022. View entity profile → Other incidents for this victim →
incident inc_a299b262cfa145a5 · 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.
Identity (basic) · Financial account · Financial credentials
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 7, 2021
When the intrusion reportedly occurred, per the linked filings
Dec 8, 2021
Reported by MAINE AG filing
Foundation Wellness reported a data breach to the Montana Attorney General. The breach was reported on 2022-01-07. The breach occurred from 9/7/2021 to 10/4/2021. 10 Montana residents were affected.
Affected (this filing): 10
Foundation Wellness reported a data breach to the Maine Attorney General, indicating that an external system breach (hacking) occurred between September 7, 2021, and October 4, 2021. The breach was discovered on December 8, 2021. The incident affected 14 Maine residents, compromising their names and financial account numbers or credit/debit card numbers with associated security codes or PINs. Affected individuals were notified on January 7, 2022. Identity theft protection services were not offered.
Affected (this filing): 14
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.