OK Foods, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2021-04-15. The breach occurred from 4/22/2020 to 4/30/2020. 7 Montana residents were affected.
Affected (this filing): 7
Clustered 2 filings across 2 jurisdictions · filing window Apr 15, 2021 → Apr 17, 2021. View entity profile → Other incidents for this victim →
incident inc_0ece2e9b8bfa4a42 · merge_method human · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 22, 2020
When the intrusion reportedly occurred, per the linked filings
Mar 18, 2021
Reported by MAINE AG filing
OK Foods, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2021-04-15. The breach occurred from 4/22/2020 to 4/30/2020. 7 Montana residents were affected.
Affected (this filing): 7
OK Foods, Inc. reported an external system breach that occurred from April 22, 2020, to April 30, 2020, and was discovered on March 18, 2021. The incident affected 34,654 individuals, including four Maine residents. The compromised information included names combined with financial account or credit/debit card numbers along with their access codes or PINs. The company provided written notifications to affected individuals on April 15, 2021, and offered 12 months of complimentary credit monitoring services.
Affected (this filing): 4
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.