Clustered 2 filings across 2 jurisdictions · filing window May 11, 2026 → Jun 1, 2026. View entity profile → Other incidents for this victim →
incident inc_2ba169bcb3fb4be7 · merge_method deterministic · 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.
MA
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 29, 2026
When the intrusion reportedly occurred, per the linked filings
Apr 29, 2026
Reported by MASSACHUSETTS AG filing
Park Dental Research is a supplier of technologies and materials for dental laboratories and orthodontic clinics; however, when it comes to security, it has proven to be an unreliable partner. As a result of its negligence, partner and customer data, financial documents, and login credentials for various web resources were compromised and made publicly available on the Internet.
Park Dental Research Corporation notified Massachusetts residents of a data security incident occurring on or about April 29, 2026. The incident potentially exposed personal information including names, Social Security numbers, dates of birth, home addresses, compensation, bank account information, passports, I-9s, and driver's licenses. The company engaged professionals, notified law enforcement, and provided 24 months of identity theft protection services through IDX. No evidence of misuse was found at the time of notification.
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.