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

PRENTKE ROMICH COMPANY — August 2024 breach

Clustered 10 records across 9 jurisdictions: 9 filings and 1 leak-site claim · filing window Sep 12, 2024 → Sep 25, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 records

States

9

Affected · reported

51,627

First → last dated filing

Sep 12, 2024 → Sep 25, 2024

Merge confidence

100%

incident inc_8db1c69a659a4f24 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. Intrusion Aug 13, 2024–Aug 21, 2024, discovered Aug 21, 2024. 51,627 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Notifications rolled out on a 13-day schedule across 8 dated filings beginning Sep 12, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
13days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont⏱ VT AG >14 bdayWashington⏱ WA AG >30dMassachusetts✓ MA credit monitoring dueCalifornia✓ CA 60-day OK · 22dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 13, 2024breach begins
Aug 21, 2024discovered
Sep 12, 2024first dated filing
Sep 25, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. 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. SEP 1IL AGIL AG noticefiling day not on record · no count stated—
  2. SEP 12MT AGMT AG noticefirst filing · 45 MT residentsday 0
  3. SEP 12MA AGMA AG notice3 MA residentsday 0
  4. SEP 12NH AGNH AG noticeno count statedday 0
  5. SEP 12IN AGIN AG noticestates nationwide total 608day 0
  6. SEP 12VT AGVT AG noticeno count statedday 0
  7. SEP 18Leak sitefog postattacker claim · unverified+7d
  8. SEP 25CA AGCA AG noticeno count stated+13d
  9. SEP 25WA AGWA AG notice690 WA residents+13d
  10. SEP 25HHS OCRHHS OCR noticemost recent · states nationwide total 51,627+13d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 13, 2024 – Aug 21, 2024
MT AG
Discovered
Aug 21, 2024· 8d undetected
IL AG + MT AG + NH AG +3
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + NH AG + VT AG +4
Attack vector
Unauthorized Access
MT AG

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)

51,627

Sum of filed state slices

744· 1.4% of stated

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

US51,627
WA690
MT45
IN6
MA3

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 filing9 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 Aug 22, 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

13 days

Cadence

~1 / 1.9d

vs. multi-state median

2.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.