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

U.S.Vision, Inc., — April 2021 breach

Clustered 7 filings across 6 jurisdictions · filing window Sep 3, 2021 → Mar 21, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

412,565

First → last dated filing

Sep 3, 2021 → Mar 21, 2024

Merge confidence

100%

incident inc_fc175299cf284893 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. Intrusion Apr 20, 2021–May 17, 2021, discovered Apr 20, 2021 — the first regulatory filing landed 136 days later; 3 later filings were flagged late. 412,565 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 930-day schedule across 6 dated filings beginning Sep 3, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
136days

Discovered → first regulatory filing

Discovery variance
22days

Range of discovered_at dates across filings

Filing span
930days

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 clocksCalifornia✗ CA 60-day late · 534dWashington✗ WA AG >90dOregon✗ OR AG >45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 20, 2021breach begins
Apr 20, 2021discovered · members disagree
notification delay · 136 days
Sep 3, 2021first dated filing
Mar 21, 2024most 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. SEP 3DE AGDE AG noticefirst filing · no count statedday 0
  2. NOV 30CA AGCA AG noticeno count stated+453d
  3. MAR 1IL AGIL AG noticefiling day not on record · no count stated—
  4. MAR 19CA AGCA AG noticeno count stated+928d
  5. MAR 20WA AGWA AG notice8,308 WA residents+929d
  6. MAR 20OR AGOR AG noticestates nationwide total 412,565+929d
  7. MAR 21SC AGSC AG noticemost recent · no count stated+930d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 20, 2021 – May 17, 2021
DE AG
Discovered
Apr 20, 2021IL AGMay 12, 2021DE AG + CA AG + WA AG +2filings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
DE AG + CA AG + WA AG +1
Attack vector
Unauthorized Access
DE 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)

412,565

Sum of filed state slices

8,308· 2.0% of stated

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

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 filing7 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 23, 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

930 days

Cadence

~1 / 186d

vs. multi-state median

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