DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

How Zappos’ User Agreement Failed In Court and Left Zappos Legally Naked

Posted on October 10, 2012 by Dissent

Eric Goldman writes:

In January, Zappos (part of $AMZN) announced a massive data security breach affecting 24 million consumers.  As typically happens in these situations, plaintiffs’ class action lawyers swarmed over Zappos for the breach, filing dozens of lawsuits.  Zappos tried to send the lawsuits to arbitration based on an arbitration clause in its user agreement.  Recently, a federal court struck down Zappos.com’s user agreement, denying Zappos’ arbitration request.  This is an unfortunate ruling for Zappos, because its contract–now dead–would have been quite helpful in combating this high-profile and potentially very expensive data security breach lawsuit.   More importantly, the mistakes Zappos made in its user agreement–though common throughout the Internet–are completely and easily avoidable.  This post will make some suggestions for how to avoid Zappos’ fate.

Read more on Forbes.


Related:

  • Landmark civil penalty of AU$5.8 million issued under Australia’s Privacy Act
  • How many courts have had sealed and sensitive files exposed by one vendor's error?
  • Legal Aid Agency chief admits difficulties understanding impact of cyberattack
  • US company with access to biggest telecom firms uncovers breach by nation-state hackers
  • UK: FCA fines former employee of Virgin Media O2 for data protection breach
  • The 4TB time bomb: when EY's cloud went public (and what it taught us)
Category: Breach IncidentsBusiness SectorCommentaries and Analyses

Post navigation

← Feds arrests dozens in ID theft-tax fraud takedown in South Florida
Almost 280,000 to be notified of hack at Northwest Florida State College; ID theft reported →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.