One linked filing — more sources may join as they report · filed Dec 13, 2024. View entity profile → Other incidents for this victim →
incident inc_4e8064ef5a5c4937 · 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
Jun 17, 2024 → Jul 11, 2024
When the intrusion reportedly occurred, per the linked filings
Oct 30, 2024
Reported by OREGON AG filing
Saif reported a data breach to the Oregon Attorney General. The breach was reported on 2024-12-13. The breach occurred during 6/17/2024 - 7/11/2024. The breach was discovered on 10/30/2024. 3,002 individuals were affected. Notice was sent on 12/13/2024.
Affected (this filing): 3,002
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.