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

ON Q FINANCIAL, LLC — February 2021 breach

Clustered 9 filings across 8 jurisdictions · filing window Mar 22, 2021 → Apr 20, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

191,628

First → last filing

Mar 22, 2021 → Apr 20, 2021

Merge confidence

100%

incident inc_866824fcaff04b91 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Feb 22, 2021–Feb 24, 2021, discovered Feb 24, 2021 — the first regulatory filing landed 26 days later. 191,628 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 29-day schedule across 9 filings beginning Mar 22, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
26days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
29days

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 clocksWashington✓ WA AG ≤30dOregon✓ OR AG ≤45dSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 22, 2021breach begins
Feb 24, 2021discovered
notification delay · 26 days
Mar 22, 2021first filing
Apr 20, 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 22WA AGWA AG noticefirst filing · 18,066 WA residentsday 0
  2. APR 1DE AGDE AG noticeno count stated+10d
  3. APR 2OR AGOR AG noticestates nationwide total 191,628+11d
  4. APR 12CA AGCA AG noticeno count stated+21d
  5. APR 12MT AGMT AG notice51 MT residents+21d
  6. APR 18IN AGIN AG noticestates nationwide total 191,628+27d
  7. APR 19SC AGSC AG notice14,818 SC residents+28d
  8. APR 19IN AGIN AG noticestates nationwide total 191,628+28d
  9. APR 20MA AGMA AG noticemost recent · 262 MA residents+29d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 22, 2021 – Feb 24, 2021
WA AG
Discovered
Feb 24, 2021· 2d undetected
WA AG + DE AG + OR AG +2
Data types
Financial · Financial account · Identity (basic) · Government ID · PII
WA AG + DE AG + CA AG +2
Attack vector
Misconfiguration
WA 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)

191,628

Sum of filed state slices

33,419· 17.4% of stated

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

US191,628
WA18,066
SC14,818
MA262
IN222
MT51

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

29 days

Cadence

~1 / 3.6d

vs. multi-state median

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