DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed2 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 2 filings

PracticeMax — April 2021 breach

Clustered 2 filings across 1 jurisdiction · filing window Oct 15, 2021 → Oct 19, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge85%

Determination

Confirmed

Members

2 filings

States

1

Affected · reported

—

First → last filing

Oct 15, 2021 → Oct 19, 2021

Merge confidence

85%

incident inc_26a91be9423a456a · merged by deterministic · confidence 85%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filings describe a ransomware attack. Intrusion Apr 17, 2021–May 5, 2021, discovered May 1, 2021 — the first regulatory filing landed 167 days later. Data reported: Government ID, PHI, Health (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
167days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
4days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

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.