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

20/20 Eye Care Network, Inc. — January 2021 breach

Clustered 11 filings across 10 jurisdictions · filing window Jan 1, 2021 → Jul 2, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

10

Affected · reported

4,142,440

First → last filing

Jan 1, 2021 → Jul 2, 2021

Merge confidence

100%

incident inc_e583ff4e8c7e4382 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Jan 11, 2021, discovered Jan 11, 2021. 4,142,440 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 182-day schedule across 11 filings beginning Jan 1, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
38days

Range of discovered_at dates across filings

Filing span
182days

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 >90dOregon✗ OR AG >45dMaine✗ ME AG >90d · 100dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 11, 2021breach begins
Jan 11, 2021discovered · members disagree
Jan 1, 2021first filing
Jul 2, 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JAN 1IL AGIL AG noticeno count statedday 0
  3. MAY 24HHS OCRHHS OCR noticestates nationwide total 4,142,440+143d
  4. MAY 28WA AGWA AG notice690 WA residents+147d
  5. MAY 28IN AGIN AG noticestates nationwide total 3,253,822+147d
  6. MAY 29OR AGOR AG noticestates nationwide total 3,253,822+148d
  7. MAY 29ME AGME AG noticestates nationwide total 3,253,822+148d
  8. MAY 29MA AGMA AG notice829 MA residents+148d
  9. JUN 4NH AGNH AG notice148 NH residents+154d
  10. JUL 2SC AGSC AG notice1,244 SC residents+182d
  11. JUL 2MT AGMT AG noticemost recent · 84 MT residents+182d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 11, 2021
WA AG
Discovered
Jan 11, 2021IL AG + WA AG + NH AG +2Feb 18, 2021OR AG + ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + WA AG + NH AG +4
Attack vector
Unauthorized Access
HHS OCR

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)

4,142,440

Sum of filed state slices

4,762· 0.1% of stated

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

US4,142,440
IN1,546
SC1,244
MA829
WA690
ME221
NH148
MT84

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

182 days

Cadence

~1 / 18.2d

vs. multi-state median

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