DisclosureLens
State AGConfirmed2 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 2 filings

RH (RH) — February 2020 breach

Clustered 2 filings across 2 jurisdictions · filed May 20, 2020. View entity profile → Other incidents for this victim →

✓ 0 discrepancies — filings agreeMerge100%

Determination

Confirmed

Members

2 filings

States

2

Affected · reported

823

First → last filing

May 20, 2020

Merge confidence

100%

incident inc_41eaf12b235948f9 · merged by deterministic · confidence 100%

Part of the PaperlessPay Corporation supply-chain incident (2020)at least 13 organizations filed notifications naming this third party.
Confirmed breach. One breach, 2 legal records. Intrusion Feb 18, 2020, discovered May 5, 2020 — the first regulatory filing landed 15 days later. 823 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
15days

Discovered → first regulatory filing

Filing span
0days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Sensitive data

identity_government

Incident timeline

Feb 18, 2020breach begins
May 5, 2020discovered
notification delay · 15 days
May 20, 2020first filing
watching for filings

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

Member cascade — every filing about this breach

  1. MAY 20MA AGMA AG noticefirst filing · 663 MA residentsday 0
  2. MAY 20NH AGNH AG noticemost recent · 160 NH residentsday 0
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 18, 2020
NH AG
Discovered
May 5, 2020· 77d undetected
NH AG
Data types
Identity (basic) · Government ID · Financial account
NH AG
Attack vector
Third-Party / Supply Chain
NH AG
Response
Engaged forensic investigation firm (Ankura) · Cooperated with DHS and FBI investigation · Secured TransUnion to provide identity monitoring
NH AG

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

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

0 days

vs. multi-state median

20.0× 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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.