Ark Naturals reported a data breach to the Montana Attorney General. The breach was reported on 2021-10-14. The breach occurred from 2/8/2021 to 2/23/2021. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Oct 14, 2021. View entity profile → Other incidents for this victim →
incident inc_70494fdff7c946cd · 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
Feb 8, 2021
When the intrusion reportedly occurred, per the linked filings
Sep 15, 2021
Reported by MAINE AG filing
Ark Naturals reported a data breach to the Montana Attorney General. The breach was reported on 2021-10-14. The breach occurred from 2/8/2021 to 2/23/2021. 1 Montana residents were affected.
Affected (this filing): 1
Ark Naturals, a pet wellness products company, reported a data breach affecting 3 Maine residents. The breach, which occurred between February 8, 2021, and February 23, 2021, and was discovered on September 15, 2021, resulted from a phishing incident. The compromised information includes names and financial account numbers or credit/debit card numbers with their corresponding security codes. The company offered 12 months of identity theft protection services through Experian to those affected.
Affected (this filing): 3
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.