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

Professional Finance Company — February 2022 breach

Clustered 10 filings across 9 jurisdictions · filing window May 3, 2022 → Jul 1, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

9

Affected · reported

1,972,699

First → last filing

May 3, 2022 → Jul 1, 2022

Merge confidence

100%

incident inc_cbb83e3e45a34d21 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Feb 22, 2022–Feb 26, 2022, discovered Feb 26, 2022 — the first regulatory filing landed 66 days later (flagged late). 1,972,699 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 3 more. Notifications rolled out on a 59-day schedule across 10 filings beginning May 3, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
66days

Discovered → first regulatory filing

Discovery variance
30days

Range of discovered_at dates across filings

Filing span
59days

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 clocksMaine✗ ME AG >90d · 95dWashington✗ WA AG >90dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 22, 2022breach begins
Feb 26, 2022discovered · members disagree
notification delay · 66 days
May 3, 2022first filing
Jul 1, 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. MAY 3IN AGIN AG noticefirst filing · states nationwide total 1,972,699day 0
  2. MAY 17MT AGMT AG notice1 MT residents+14d
  3. JUL 1ME AGME AG notice12,474 ME residents+59d
  4. JUL 1MT AGMT AG notice6,296 MT residents+59d
  5. JUL 1HHS OCRHHS OCR noticestates nationwide total 1,918,941+59d
  6. JUL 1WA AGWA AG notice18,346 WA residents+59d
  7. JUL 1MA AGMA AG notice4,224 MA residents+59d
  8. JUL 1OR AGOR AG noticeno count stated+59d
  9. JUL 1CA AGCA AG noticeno count stated+59d
  10. JUL 1SC AGSC AG noticemost recent · 38,696 SC residents+59d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 22, 2022
IN AG
Discovered
Feb 26, 2022MT AG + WA AG + CA AG +1Mar 28, 2022ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + HHS OCR + WA AG +4
Attack vector
Ransomware
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)

1,972,699

Sum of filed state slices

95,420· 4.8% of stated

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

US1,972,699
SC38,696
WA18,346
IN15,384
ME12,474
MT6,296
MA4,224

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

59 days

Cadence

~1 / 6.6d

vs. multi-state median

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