Clustered 3 filings across 2 jurisdictions · filed Oct 16, 2025. View entity profile → Other incidents for this victim →
incident inc_f04c0a9573cf4635 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
Health (basic) · Identity (basic)
OR VT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 8, 2025
When the intrusion reportedly occurred, per the linked filings
Sep 8, 2025
Reported by VERMONT AG filing
Oct 1, 2025
Reported by OREGON AG filing
River City Eye Care, LLC notified Vermont AG of a data breach occurring around September 8, 2025. Unauthorized access resulted in the copying of files containing names and government identifiers. The company engaged federal law enforcement and offered credit monitoring services. Investigation completed October 1, 2025.
River City Eye Care, LLC (Oregon) reported a Hacking/IT Incident to HHS OCR on 2025-10-16 affecting 6,588 individuals. Breached information was located on a Network Server. No business associate was identified as present. No further detail is available from the HHS web description.
Affected (this filing): 6,588
River City Eye Care, LLC reported a data breach to the Oregon Attorney General. The breach was reported on 2025-10-16. The breach occurred during 9/8/2025 - 9/8/2025. The breach was discovered on 10/1/2025. 6,588 individuals were affected. Notice was sent on 10/16/2025.
Affected (this filing): 6,588
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.