Clustered 4 filings across 3 jurisdictions · filing window Mar 31, 2025 → May 5, 2025. View entity profile → Other incidents for this victim →
incident inc_dca0b809fbea47ce · 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.
CA IN
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 20, 2025
When the intrusion reportedly occurred, per the linked filings
Mar 4, 2025
Reported by CALIFORNIA AG filing
Sonrisas Dental Health offers a range of pediatric services that focus on prevention, oral health education, and stress-free gentle care.
Sonrisas Dental Health reported to HHS on 2025-05-02 a Hacking/IT Incident affecting 15,644 individuals. Breached information located on Network Server. The cyberattack compromised PHI including clinical, demographic, and financial data. The entity provided credit monitoring, implemented security safeguards, and retrained staff.
Sonrisas Dental Health reported a data breach to the Indiana Attorney General. The breach occurred on 2025-01-20 and was reported on 2025-05-05. 3 Indiana residents were affected. 15,644 individuals affected in total.
Affected (this filing): 15,644
Sonrisas Dental Health notified the California Attorney General of a data breach affecting individuals whose personal information was subject to unauthorized access and acquisition. The incident occurred between January 20, 2025, and March 4, 2025, with suspicious activity first detected on March 4, 2025. Affected data may include names. The company secured systems, launched an investigation with third-party specialists, notified the FBI, and is offering credit monitoring and fraud assistance services.
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): 15,644