Confirmed breach. Intrusion Mar 8, 2021–Apr 26, 2021, discovered Apr 26, 2021 — the first regulatory filing landed 74 days later (flagged late). 212,910 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksOregon✗ OR AG >45dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
212,910
Data types
—
Jurisdictions
2
CA OR
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 8, 2021 → Apr 26, 2021
When the intrusion reportedly occurred, per the linked filings
49 days
Breach discoveredAG web form
Apr 26, 2021
Reported by OREGON AG filing
74 days
🦫Oregon State AGFirst filinglinked via same-victim cross-source · 100%
CSI Financial Services, LLC (“ClearBalance”) reported a data breach to the Oregon Attorney General. The breach was reported on 2021-07-09. The breach occurred during 3/8/2021 - 4/26/2021. The breach was discovered on 4/26/2021. 209,719 individuals were affected. Notice was sent on 7/9/2021.
Affected (this filing): 209,719
🐻CALIFORNIAHHS OCRMost recentlinked via same-victim cross-source · 100%
CSI Financial Services, LLC dba ClearBalance (CA), a business associate, reported to HHS on 2021-07-10 a Hacking/IT Incident affecting 3,191 individuals. Employees were victims of an email phishing scheme compromising ePHI including names, addresses, driver's license numbers, Social Security numbers, diagnoses, and financial information. The BA implemented email security controls, revised policies and procedures, and OCR provided technical assistance on its security management process. Breached information located on Email.
Affected (this filing):
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.