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

EyeMed Vision Benefits — June 2020 breach

Clustered 12 filings across 10 jurisdictions · filing window Sep 28, 2020 → Jan 27, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

12 filings

States

10

Affected · reported

2,329,942

First → last filing

Sep 28, 2020 → Jan 27, 2021

Merge confidence

100%

incident inc_06c08d351c26445f · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. Intrusion Jun 24, 2020–Jul 1, 2020, discovered Jul 1, 2020 — the first regulatory filing landed 89 days later; 2 later filings were flagged late. 2,329,942 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 4 more. Notifications rolled out on a 121-day schedule across 12 filings beginning Sep 28, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
89days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
121days

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 clocksOregon✗ OR AG >45dWashington✗ WA AG >90dMaine⏱ ME AG >30d · 89dCalifornia✓ CA 60-day OK · 44dMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Jun 24, 2020breach begins
Jul 1, 2020discovered
notification delay · 89 days
Sep 28, 2020first filing
Jan 27, 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. SEP 28ME AGME AG noticefirst filing · states nationwide total 54,266day 0
  2. SEP 28MT AGMT AG notice2,153 MT residentsday 0
  3. SEP 28CA AGCA AG noticeno count statedday 0
  4. SEP 28MA AGMA AG notice108,478 MA residentsday 0
  5. SEP 28HHS OCRHHS OCR noticestates nationwide total 1,474,000day 0
  6. OCT 12OR AGOR AG noticestates nationwide total 547,370+14d
  7. OCT 12WA AGWA AG notice19,625 WA residents+14d
  8. NOV 30ME AGME AG noticestates nationwide total 2,329,942+63d
  9. DEC 1NH AGNH AG notice33,745 NH residents+64d
  10. DEC 11DE AGDE AG noticeno count stated+74d
  11. DEC 11CA AGCA AG noticeno count stated+74d
  12. JAN 27SC AGSC AG noticemost recent · 219,518 SC residents+121d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 24, 2020 – Jul 1, 2020
ME AG
Discovered
Jul 1, 2020· 7d undetected
ME AG + MT AG + CA AG +4
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
ME AG + MA AG + HHS OCR +5
Attack vector
Unauthorized Access
ME 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)

2,329,942

Sum of filed state slices

406,576· 17.5% of stated

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

US2,329,942
SC219,518
MA108,478
NH33,745
ME23,057
WA19,625
MT2,153

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 filing12 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 22, 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

121 days

Cadence

~1 / 11d

vs. multi-state median

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