One linked filing — more sources may join as they report · filed Oct 30, 2020. View entity profile → Other incidents for this victim →
incident inc_67239b04cc094578 · 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
May 20, 2020
When the intrusion reportedly occurred, per the linked filings
Sep 29, 2020
Reported by OREGON AG filing
Ride Connection, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2020-10-30. The breach occurred during 5/20/2020. The breach was discovered on 9/29/2020. 293 individuals were affected. Notice was sent on 10/16/2020.
Affected (this filing): 293
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.