Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksCalifornia✓ CA 60-day OK · 55dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
—
Data types
2
Credentials · PII
Jurisdictions
1
CA
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach discoveredletter-grounded
Jul 1, 2017
Reported by CALIFORNIA AG filing
Breach window
Jul 30, 2017
When the intrusion reportedly occurred, per the linked filings
In July 2017, Zazzle detected a brute force attack where unauthorized parties used credentials obtained from other breaches to attempt logins to Zazzle accounts. Usernames (email addresses) and passwords were potentially compromised. Zazzle reset affected passwords and implemented CAPTCHA to prevent automated logins.
CA 60-day OK · 55d
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.