Confirmed breach. Intrusion Jun 7, 2019, discovered Jun 7, 2019 — the first regulatory filing landed 18 days later. 580 individuals reported across the linked filings.
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.
Regulatory clocksOregon✓ OR AG ≤45dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
580
Data types
—
Jurisdictions
1
OR
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 7, 2019
When the intrusion reportedly occurred, per the linked filings
Rogue Valley Council of Governments reported a data breach to the Oregon Attorney General. The breach was reported on 2019-06-25. The breach occurred during 6/7/2019 - 6/7/2019. The breach was discovered on 6/7/2019. 580 individuals were affected. Notice was sent on 6/25/2019.
Affected (this filing): 580
OR AG ≤45d
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.