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

Receivables Performance Management, LLC — April 2021 breach

Clustered 9 filings across 8 jurisdictions · filing window Oct 2, 2022 → Nov 21, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

3,766,573

First → last filing

Oct 2, 2022 → Nov 21, 2022

Merge confidence

100%

incident inc_982035f10e3b4ce2 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Apr 8, 2021–May 12, 2022, discovered May 12, 2021 — the first regulatory filing landed 508 days later (flagged late). 3,766,573 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 50-day schedule across 9 filings beginning Oct 2, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
508days

Discovered → first regulatory filing

Discovery variance
508days

Range of discovered_at dates across filings

Filing span
50days

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.

Regulatory clocksOregon✗ OR AG >45dWashington✗ WA AG >90dMaine⏱ ME AG >30d · 50dHawaii✓ HI CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 8, 2021breach begins
May 12, 2021discovered · members disagree
notification delay · 508 days
Oct 2, 2022first filing
Nov 21, 2022most 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. OCT 2DE AGDE AG noticefirst filing · no count statedday 0
  2. NOV 21CA AGCA AG noticeno count stated+50d
  3. NOV 21IN AGIN AG noticestates nationwide total 3,766,573+50d
  4. NOV 21HI AGHI AG notice8,529 HI residents+50d
  5. NOV 21DE AGDE AG noticeno count stated+50d
  6. NOV 21OR AGOR AG noticestates nationwide total 3,766,573+50d
  7. NOV 21ME AGME AG noticestates nationwide total 3,766,573+50d
  8. NOV 21MT AGMT AG notice6,255 MT residents+50d
  9. NOV 21WA AGWA AG noticemost recent · 48,252 WA residents+50d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 8, 2021 – May 12, 2021
DE AG
Discovered
May 12, 2021DE AG + CA AG + HI AG +2Oct 2, 2022OR AG + ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
DE AG + CA AG + HI AG +3
Attack vector
Ransomware
DE 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)

3,766,573

Sum of filed state slices

143,901· 3.8% of stated

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

US3,766,573
IN72,183
WA48,252
ME8,682
HI8,529
MT6,255

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

50 days

Cadence

~1 / 6.3d

vs. multi-state median

6.3× 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.