DAVE INC.
bd_96afc6c3b4dc3c74 · schema v1 · pii pii-v1
Full breach record for DAVE INC. →Dave, Inc. experienced a data breach between June 23 and July 1, 2020, resulting from a compromise at a former third-party service provider. An unauthorized party accessed and stole customer data, including names, emails, phone numbers, hashed passwords, and encrypted Social Security numbers. The data was subsequently posted on illicit online marketplaces. Dave discovered the incident on July 1, 2020, secured systems, reset credentials, and engaged forensic experts and the FBI. Affected individuals were offered identity theft protection services.
J jump to incidentP pin to compareR raw source
Incident timeline
Jun 23, 2020
Begins
Jul 1, 2020
Discovered
Aug 20, 2020
Filed
vs. sector median
1 wks faster
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- Washington State AGbd_5e95299fb85377f62020-08-20Verified
- Oregon State AGbd_ea97508608d294232020-08-20Verified
- Indiana State AGbd_0a9d0fa37812e2742020-08-21 · +1dVerified
- New Hampshire State AGbd_d96b710b910f0da42020-08-21 · +1dVerified
Show 2 more filings ↓Show fewer ↑up to 232d gap
- Delaware State AGbd_e092890dc5d3fb2a2020-08-21 · +1dVerified
- Illinois State AGbd_f91f5bf7f513a8f62020-01-01 · +232dCandidate
Filing propagation · 7 filings · 7 states
View merged incident ↗Pattern: first filing Jan 1 (IL), last Aug 21 (DE) — a 233-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.