One linked filing — more sources may join as they report · filed Mar 2, 2016. View entity profile → Other incidents for this victim →
incident inc_181964fc6cde47a0 · merge_method deterministic
Discovered → first regulatory filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
OR
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 25, 2015 → Jan 13, 2016
When the intrusion reportedly occurred, per the linked filings
Jan 11, 2016
Reported by OREGON AG filing
Baileys reported a data breach to the Oregon Attorney General. The breach was reported on 2016-03-02. The breach occurred during 9/25/2015 - 1/13/2016. The breach was discovered on 1/11/2016. 15,000 individuals were affected.
Affected (this filing): 15,000
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.