Clustered 2 filings across 2 jurisdictions · filing window Feb 23, 2017 → Mar 10, 2017. View entity profile → Other incidents for this victim →
incident inc_33840f70e03e4178 · 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.
MT OR
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 1, 2016
When the intrusion reportedly occurred, per the linked filings
Nov 28, 2016
Reported by OREGON AG filing
Bluemercury, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2017-02-23. The breach occurred from 2/1/2016 to 12/31/2016. 69 Montana residents were affected.
Affected (this filing): 69
Bluemercury, inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2017-03-10. The breach occurred during 2/1/2016 - 12/31/2016. The breach was discovered on 11/28/2016. Notice was sent on 2/23/2017.
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.