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

Volusion — September 2019 breach

Clustered 11 filings across 11 jurisdictions · filing window Apr 20, 2020 → Apr 22, 2020 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

541,000

First → last dated filing

Apr 20, 2020 → Apr 22, 2020

Merge confidence

100%

incident inc_038298d7e30643b1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe malware. Intrusion Sep 7, 2019–Mar 20, 2020, discovered Oct 8, 2019. 541,000 individuals reported across the linked filings. Data reported: PCI, Financial account, Identity (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
164days

Range of discovered_at dates across filings

Filing span
2days

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 >90dHawaii✓ HI CRA notice dueDate basis✓ Clock withheld · confirmation dateSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentials

Incident timeline

Sep 7, 2019breach begins
Oct 8, 2019discovered · members disagree
Apr 20, 2020first dated filing
Apr 22, 2020most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. APR 20MA AGMA AG noticefirst filing · 11,673 MA residentsday 0
  3. APR 20HI AGHI AG notice1,480 HI residentsday 0
  4. APR 20DE AGDE AG noticeno count statedday 0
  5. APR 20WA AGWA AG notice14,111 WA residentsday 0
  6. APR 20IN AGIN AG noticestates nationwide total 541,000day 0
  7. APR 20CA AGCA AG noticeno count statedday 0
  8. APR 20MT AGMT AG notice1,944 MT residentsday 0
  9. APR 21OR AGOR AG noticestates nationwide total 54,100+1d
  10. APR 21SC AGSC AG notice12,358 SC residents+1d
  11. APR 22NH AGNH AG noticemost recent · 3,170 NH residents+2d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 7, 2019 – Oct 8, 2019
HI AG
Discovered
Oct 8, 2019IL AG + HI AG + DE AG +4Mar 20, 2020OR AGfilings disagree on discovery
Data types
Authentication · Financial account · Financial credentials · Identity (basic) · PCI
MA AG + HI AG + DE AG +4

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)

541,000

Sum of filed state slices

52,650· 9.7% of stated

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

US541,000
WA14,111
SC12,358
MA11,673
IN7,914
NH3,170
MT1,944
HI1,480

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

2 days

Cadence

~1 / 0.2d

vs. multi-state median

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