Confirmed breach. Intrusion Apr 11, 2024, discovered Apr 11, 2024 — the first regulatory filing landed 102 days later (flagged late). 4,109 individuals reported across the linked filings.
incident inc_c35f0fa610824660 · merge_method human · confidence 100%
Litigation Timing
Notification delay
102days
Discovered → first regulatory filing
Leak precedence
109days
Gap between first leak claim and first regulatory filing
Filing span
Regulatory clocksOregon✗ OR AG >45dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline
Leak SiteHHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmed
109days
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.
Sutton Dental Arts - a dental clinic providing a full range of dental services. Sutton Dental Arts corporate office is located in 1729 W Harvard Ave Ste 5, Roseburg, Oregon, 97471, United States and has 3 employees. The total amount of data leakage is 20.2 GB
Breach window
Apr 11, 2024
When the intrusion reportedly occurred, per the linked filings
Breach discoveredAG web form
Apr 11, 2024
Reported by OREGON AG filing
102 days
🦫Oregon State AGLeaked → filing gap · 4 molinked via operator-confirmed · 100%
Sutton Dental Arts reported a data breach to the Oregon Attorney General. The breach was reported on 2024-07-22. The breach occurred during 4/11/2024 - 4/11/2024. The breach was discovered on 4/11/2024. 4,109 individuals were affected. Notice was sent on 7/17/2024.
🦫OREGONHHS OCRMost recentLeaked → filing gap · 4 molinked via same-victim cross-source · 100%
Sutton Dental Arts reported to HHS on 2024-07-22 a Hacking/IT Incident affecting 4109 individuals. Breached information located on Network Server.
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.