Asheville Eye Associates is headquartered in Asheville, North Carolina. The offers services such as, cataract surgery, glaucoma and diabetic vision care, lasik and PRK surgery, full service optical services. The company was founded in 1986.
Clustered 2 filings across 2 jurisdictions · filing window Dec 28, 2024 → Jun 13, 2025. View entity profile → Other incidents for this victim →
incident inc_ebcfc3eef5214237 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
PII · PHI
ME
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 18, 2024
When the intrusion reportedly occurred, per the linked filings
Asheville Eye Associates is headquartered in Asheville, North Carolina. The offers services such as, cataract surgery, glaucoma and diabetic vision care, lasik and PRK surgery, full service optical services. The company was founded in 1986.
Apr 14, 2025
Reported by MAINE AG filing
On or around November 18, 2024, Asheville Eye Associates, PLLC experienced an external network security breach in which an unauthorized party gained access to and acquired files from their systems. The incident was fully investigated by April 14, 2025. Affected data may include name, address, Social Security Number, medical treatment information, and health insurance information. 147,116 individuals were affected total; 35 were Maine residents. Notifications were sent June 13, 2025.
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.
Affected (this filing): 35