Confirmed breach. Intrusion Oct 16, 2023–Oct 21, 2023, discovered Mar 26, 2025 — the first regulatory filing landed 68 days later (flagged late). 76,253 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)
76,253
Data types
—
Jurisdictions
1
OR
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 16, 2023 → Oct 21, 2023
When the intrusion reportedly occurred, per the linked filings
Clark County, WA reported a data breach to the Oregon Attorney General. The breach was reported on 2025-06-02. The breach occurred during 10/16/2023 - 10/21/2023. The breach was discovered on 3/26/2025. 76,253 individuals were affected. Notice was sent on 5/19/2025.
Affected (this filing): 76,253
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.