DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed5 records · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedinterlockcritical sensitivity
Merged incident · 5 records

Issaqueena Pediatric Dentistry — August 2025 breach

Clustered 5 records across 3 jurisdictions: 4 filings and 1 leak-site claim · filing window Feb 4, 2026 → Sep 3, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 records

States

3

Affected · reported

91,250

First → last dated filing

Feb 4, 2026 → Sep 3, 2026

Merge confidence

100%

incident inc_c4f48d9a06e64700 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filing describes unauthorized access. Intrusion Aug 24, 2025. 91,250 individuals reported across the linked filings. Data reported: Minor, Government ID, Health (basic), and 4 more. Notifications rolled out on a 211-day schedule across 3 dated filings beginning Feb 4, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Leak precedence
72days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
211days

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.

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Aug 24, 2025breach begins
Feb 4, 2026first dated filing
Sep 3, 2026most recent dated filing

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. NOV 24Leak siteinterlock postfirst record · attacker claim · unverifiedday 0
  2. FEB 4HHS OCRHHS OCR noticestates nationwide total 501+71d
  3. AUG 28IN AGIN AG noticestates nationwide total 91,250+276d
  4. SEP 1MA AGMA AG noticefiling day not on record · 21 MA residents—
  5. SEP 3SC AGSC AG noticemost recent · 55,251 SC residents+282d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 24, 2025
IN AG
Discovered
—
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PHI · PII
HHS OCR + MA AG + SC AG
Attack vector
Unauthorized Access
HHS OCR

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

91,250

Sum of filed state slices

55,286· 60.6% of stated

39% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US91,250
SC55,251
MA21
IN14

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing4 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed May 24, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

211 days

Cadence

~1 / 105.5d

vs. multi-state median

35.2× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.