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

Paysafe Group Holdings Limitedd — May 2018 breach

Clustered 9 filings across 9 jurisdictions · filing window Dec 16, 2020 → Jan 19, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

91,706

First → last filing

Dec 16, 2020 → Jan 19, 2021

Merge confidence

100%

incident inc_17f06f22e8f04700 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion May 13, 2018–Nov 24, 2020, discovered Nov 6, 2020 — the first regulatory filing landed 40 days later (flagged late). 91,706 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 34-day schedule across 9 filings beginning Dec 16, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
40days

Discovered → first regulatory filing

Discovery variance
27days

Range of discovered_at dates across filings

Filing span
34days

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 >30dMaine⏱ ME AG >30d · 40dSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 13, 2018breach begins
Nov 6, 2020discovered · members disagree
notification delay · 40 days
Dec 16, 2020first filing
Jan 19, 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. DEC 16CA AGCA AG noticefirst filing · no count statedday 0
  2. DEC 16WA AGWA AG notice1,877 WA residentsday 0
  3. DEC 16SC AGSC AG notice1,383 SC residentsday 0
  4. DEC 18MT AGMT AG notice218 MT residents+2d
  5. DEC 18IN AGIN AG noticestates nationwide total 91,706+2d
  6. DEC 21NH AGNH AG notice178 NH residents+5d
  7. DEC 23MA AGMA AG notice1,113 MA residents+7d
  8. JAN 12ME AGME AG noticestates nationwide total 91,706+27d
  9. JAN 19OR AGOR AG noticemost recent · no count stated+34d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 13, 2018 – Nov 24, 2020
CA AG
Discovered
Nov 6, 2020CA AG + WA AG + SC AG +3Dec 3, 2020ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID
CA AG + WA AG + SC AG +4
Attack vector
Unauthorized Access
CA 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)

91,706

Sum of filed state slices

6,299· 6.9% of stated

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

US91,706
WA1,877
SC1,383
MA1,113
IN1,045
ME485
MT218
NH178

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

34 days

Cadence

~1 / 4.3d

vs. multi-state median

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