DisclosureLens
State AGConfirmed7 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 7 filings

Quality CPR Care LLC — June 2020 breach

Clustered 7 filings across 7 jurisdictions · filing window Mar 15, 2021 Mar 22, 2021. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

7 filings

States

7

Affected · reported

13,689

First → last filing

Mar 15, 2021 Mar 22, 2021

Merge confidence

100%

incident inc_eefe4daa0c604ecf · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe unauthorized access. Intrusion Jun 1, 2020–Jun 1, 2021, discovered Nov 29, 2020 — the first regulatory filing landed 106 days later (flagged late). 13,689 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, and PCI. Notifications rolled out on a 7-day schedule across 7 filings beginning Mar 15, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
106days

Discovered → first regulatory filing

Discovery variance
47days

Range of discovered_at dates across filings

Filing span
7days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksOregon OR AG >45dMaine ME AG >30d · 59dFull clock table in Litigation Timeline

Incident timeline

Jun 1, 2020breach begins
Nov 29, 2020discovered · members disagree
notification delay · 106 days
Mar 15, 2021first filing
Mar 22, 2021most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. MAR 15OR AGOR AG noticefirst filing · states nationwide total 13,689day 0
  2. MAR 15IN AGIN AG noticestates nationwide total 13,689day 0
  3. MAR 15MT AGMT AG notice48 MT residentsday 0
  4. MAR 15ME AGME AG noticestates nationwide total 13,689day 0
  5. MAR 15CA AGCA AG noticeno count statedday 0
  6. MAR 15MA AGMA AG notice351 MA residentsday 0
  7. MAR 22NH AGNH AG noticemost recent · 40 NH residents+7d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 1, 2020Nov 15, 2020
OR AG
Discovered
Nov 29, 2020MT AG + CA AG + NH AGJan 15, 2021OR AG + ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · PCI
MT AG + ME AG + CA AG +2
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)

13,689

Sum of filed state slices

687· 5.0% of stated

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

US13,689
MA351
IN207
MT48
ME41
NH40

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing7 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 Jun 12, 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

7 days

Cadence

~1 / 1.2d

vs. multi-state median

1.1× faster

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.