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

VOLKSWAGEN GROUP OF AMERICA, INC. — August 2019 breach

Clustered 11 filings across 11 jurisdictions · filing window Jun 10, 2021 → Jun 14, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

3,300,000

First → last filing

Jun 10, 2021 → Jun 14, 2021

Merge confidence

100%

incident inc_0aec7691a3424060 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe a third-party compromise. Intrusion Aug 1, 2019–May 24, 2021, discovered Mar 10, 2021 — the first regulatory filing landed 92 days later (flagged late). 3,300,000 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
92days

Discovered → first regulatory filing

Discovery variance
75days

Range of discovered_at dates across filings

Filing span
4days

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 · 93dMaine✓ ME AG ≤30d · 17dSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueDate basis✓ Clock withheld · confirmation dateHawaii✓ HI CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 1, 2019breach begins
Mar 10, 2021discovered · members disagree
notification delay · 92 days
Jun 10, 2021first filing
Jun 14, 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. JUN 10ME AGME AG noticefirst filing · states nationwide total 90,184day 0
  2. JUN 10CA AGCA AG noticeno count statedday 0
  3. JUN 10SC AGSC AG notice22,212 SC residentsday 0
  4. JUN 10MA AGMA AG notice958 MA residentsday 0
  5. JUN 10OR AGOR AG noticestates nationwide total 90,184day 0
  6. JUN 10HI AGHI AG notice6,261 HI residentsday 0
  7. JUN 10ID AGID AG noticestates nationwide total 3,300,000day 0
  8. JUN 11IN AGIN AG noticestates nationwide total 90,184+1d
  9. JUN 11DE AGDE AG noticeno count stated+1d
  10. JUN 11MT AGMT AG notice3,064 MT residents+1d
  11. JUN 14NH AGNH AG noticemost recent · states nationwide total 3,300,000+4d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 1, 2019 – May 24, 2021
ME AG
Discovered
Mar 10, 2021CA AG + SC AG + ID AG +2May 24, 2021ME AG + OR AG + DE AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PCI · PII
ME AG + CA AG + SC AG +5
Attack vector
Third-Party / Supply Chain
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)

3,300,000

Sum of filed state slices

51,559· 1.6% of stated

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

US3,300,000
SC22,212
NH13,233
HI6,261
ID4,825
MT3,064
MA958
IN875
ME131

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

4 days

Cadence

~1 / 0.4d

vs. multi-state median

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