One linked filing — more sources may join as they report · filed Jan 14, 2020. View entity profile → Other incidents for this victim →
incident inc_8b0bef1cdc3a4099 · 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
Aug 30, 2019 → Oct 14, 2019
When the intrusion reportedly occurred, per the linked filings
Dec 16, 2019
Reported by OREGON AG filing
City of Bend reported a data breach to the Oregon Attorney General. The breach was reported on 2020-01-14. The breach occurred during 8/30/2019 - 10/14/2019. The breach was discovered on 12/16/2019. 5,171 individuals were affected. Notice was sent on 1/10/2020.
Affected (this filing): 5,171
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.