Zoosk, Inc.
bd_a6b98a214f2ef77a · schema v1 · pii pii-v1
Full breach record for Zoosk, Inc. →Zoosk, Inc. reported that an unauthorized third party gained access to a database hosted by a third-party provider on or around January 12, 2020. The company discovered the incident on May 11, 2020, after being alerted to a potential compromise. The breach affected approximately 560,138 California residents, exposing names, email addresses, dates of birth, demographic information, and potentially passwords. Financial data and government IDs were not involved. Zoosk engaged forensic specialists, notified law enforcement, and implemented remediation measures including MFA and password rotation.
J jump to incidentP pin to compareR raw source
Incident timeline
Jan 12, 2020
Begins
May 11, 2020
Discovered
Jun 11, 2020
Filed
vs. sector median
14 wks faster
Linked disclosures
Why this link?Regulatory filings (4) · sorted by filing gap
- Oregon State AGbd_496bee33a76a04992020-06-11Verified
- Washington State AGbd_40aaf6755c696b582020-06-10 · +1dVerified
- Delaware State AGbd_55917fefd56d6a2a2020-06-03 · +8dVerified
- Illinois State AGbd_98c22dd75d7c290f2020-01-01 · +162dCandidate
Filing propagation · 5 filings · 5 states
View merged incident ↗Pattern: first filing Jan 1 (IL), last Jun 11 (CA) — a 162-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.