Clustered 2 filings across 2 jurisdictions · filing window May 25, 2016 → May 27, 2016. View entity profile → Other incidents for this victim →
incident inc_8be1557681cc4eee · 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.
MT OR
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 20, 2016
When the intrusion reportedly occurred, per the linked filings
Apr 27, 2016
Reported by OREGON AG filing
Kroger Co. reported a data breach to the Montana Attorney General. The breach was reported on 2016-05-25. The breach occurred from 1/20/2016 to 4/27/2016. 20 Montana residents were affected.
Affected (this filing): 20
The Kroger Co reported a data breach to the Oregon Attorney General. The breach was reported on 2016-05-27. The breach occurred during 1/31/2016. The breach was discovered on 4/27/2016. Notice was sent on 5/3/20165/5/20165/25/2016.
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.