United States: 5 Big Developments In Privacy Class Actions In 2015, And 3 To Look For In 2016

Last Updated: January 6 2016
Article by Paul Karlsgodt

The burgeoning area of privacy class action litigation showed no signs of slowing down in 2015. Here are some of the most significant developments from the past year, as well as some things to watch for in the coming year. For purposes of this article, we include in the definition of "privacy" class action litigation class actions arising out of data security breaches; litigation involving the collection, use, or transfer of consumer information; and litigation involving alleged intrusions upon privacy interests.

Five Significant Developments in 2015

  1. The Seventh Circuit Court of Appeals Chips Away at Article III Standing as a First Line of Defense

Immediately after the Supreme Court issued its decision in Clapper v. Amnesty International USA, 133 S. Ct. 1138 (2013), defense lawyers began to cite it in data breach cases for the proposition that the mere risk of future identity theft was never an injury in fact sufficient to give rise to Article III standing. Several early lower court decisions accepted this argument, but more recently, lower courts have begun to find ways to distinguish Clapper, resulting in a trend toward pre-Clapper jurisprudence that, at least in some instances, the risk of future harm is an injury in fact. The most prominent of these decisions was the Seventh Circuit's decision in Remijas v. Neiman Marcus Group, LLC, 794 F. 3d 688 (7th Cir. 2015), where the panel held that the alleged facts supported the conclusion that the risk of harm in the form of identity theft was not just possible but was actually "certainly impending," distinguishing it from the facts at issue in Clapper.

While certainly a victory for data breach plaintiffs, the victory may ultimately turn out to be a hollow one. The Remijas panel refused to consider the related argument of whether the alleged future harm was a cognizable injury sufficient to satisfy the elements of the plaintiffs' claims on the merits, holding that the issue had been waived because the defendant had not cross-appealed. In the primary Seventh Circuit case decided before Clapper involving standing in the data breach context, Pisciotta v. Old Nat'l Bancorp, 499 F.3d 629, 639-40 (7th Cir. 2007), the court had reached the second issue and had ruled that although the plaintiff had standing, he had not stated a claim for relief on the merits. A similar result had been reached in the Ninth Circuit's primary pre-Clapper standing decision, Krottner v. Starbucks Corp., 628 F.3d 1139 (9th Cir. 2010). In light of these trends, look for the battleground to shift from standing to early attacks on plaintiffs' claims on the merits.

  1. Class Certification Granted in Target Issuing Bank Litigation

In September, U.S. District Judge Paul Magnuson granted class certification in the consolidated MDL proceeding brought on behalf of issuing banks claiming damages resulting from Target's 2013 payment card hacking incident. In re: Target Corporation Customer MDL, No. 14-2522 (D. Minn., Sept. 15, 2015). The decision was significant as one of the first to grant class certification in a class action arising out of a data breach. However, it is important to understand the context of the decision in evaluating its potential future legacy. In particular, in reasoning that variations in injury and causation did not prevent class certification, Judge Magnuson distinguished the issuing bank case from the class actions brought on behalf of individual consumers arising from the same breach, observing that the injuries allegedly suffered by issuing banks were not potential future injuries but rather expenses already incurred for, among other things, reissuing cards compromised in the incident. He went on to reason that the individualized issues regarding causation and injury were not present with regard to the financial institutions' claims, and that any issues regarding variations in the amount of damages did not prevent class certification. This distinction means that the decision will be of limited value to plaintiffs in consumer data breach class actions.

  1. High-Profile Data Breach Settlements Remain (Mostly) Limited to Payment Card Breaches

We will never know whether the distinctions between the issuing banks' claims and consumer claims would have been enough to make a difference in Judge Magnussen's analysis of class certification in the consumer action, because the parties had already reached a settlement of the consumer claims before the case reached the contested class certification phase. The Target settlement calls for Target to pay $10 million into a fund against which class members can make claims for compensation for certain out-of-pocket expenses, but it also requires Target to pay for administration and an attorney's fee award in addition to that amount, so the overall cost of the settlement to Target is closer to $20 million. The Target settlement is the latest in a trend in which defendants in payment card data breach cases have settled at an early stage. The individual benefits available to claimants are similar to other payment card data breach settlements, such as the settlements reached in class actions brought against T.J.Maxx, Heartland, Michaels, and Schnuck Markets. However, the Target settlement differs from those other settlements in that the $10 million amount is not a cap but rather a nonreversionary fund which Target has to pay even if less than $10 million is actually claimed.

Outside the context of payment card breaches, data breach class action settlements have been rare so far. One notable exception in 2015 was Sony's settlement of the lawsuits brought on behalf of employees arising out of the highly publicized hacking incident said by the U.S. government to have been committed by North Korea in retaliation for Sony's production of the film The Interview. It remains to be seen whether the Sony settlement will influence other settlements in cases involving hacking of information other than payment cards, but the unique facts underlying the Sony case make that settlement an unlikely model for other data hacking cases.

Earlier in the year, Adobe reached an individual settlement with the named plaintiffs and their attorneys in a would-be class action lawsuit arising out of a hacking incident in which consumers' payment card numbers and other personal information were allegedly exposed. The plaintiffs agreed to the settlement after discovery apparently revealed no evidence that any data had actually been misused. The Adobe settlement is significant in that it illustrates a way in which a data breach class action can be resolved without the defendant having to provide monetary benefits to every member of a proposed class. Of course, by settling on an individual basis, the defendant does not receive a release of all putative class members' claims. As a result, this settlement structure will not work as a practical matter when the defendant is likely to continue to face suits by other plaintiffs and their attorneys after settling with a given set of plaintiffs and attorneys.

  1. Customer Data Collection Class Actions Continue to Hit Roadblocks, but Plaintiffs Are Persistent

As technological advances make the collection, storage, and analysis of ever-larger amounts of data less and less expensive, we are starting to see an increase in class actions attacking the ways in which companies collect, store, sell, and transfer information about their customers or other consumers. As with data breach cases, however, the challenge that plaintiffs in these cases face is in articulating some cognizable injury resulting from the use or sale of information about them. That inability to establish any injury, among other things, led to the failure of several putative class actions in 2015, most notably in a series of cases alleging that companies allowed personally identifiable information about customer Internet browsing history to be collected and sent to the social media site Facebook. In re: Hulu Privacy Litigation, — F. Supp. 3d —-, No. 3:11-cv-03764 (N.D. Cal. Mar. 31, 2015) (granting summary judgment); Carlsen v. GameStop, Inc., — F. Supp. 3d —-, 2015 WL 3538906, at *6 (D. Minn. June 4, 2015) (granting motion to dismiss); Austin-Spearman v. AARP and AARP Services, Inc., — F. Supp. 3d —-, 2015 WL 4555098 (D.D.C. July 28, 2015) (same).

Notwithstanding these recent setbacks, expect plaintiffs to continue to pursue lawsuits arising out of the collection, use, and transfer of personally identifiable information in the years to come, as technological advances allow companies to become more creative in what they can do to profit from this information.

  1. The TCPA Litigation Explosion Continues, for Now

Class actions arising out of alleged violations of the Telephone Consumer Protection Act continue to be filed in droves. The potential recovery of between $500 and $1,500 in statutory damages per violation, combined with the fact that many cases involve hundreds, thousands, or even millions of calls in connection with a particular telemarketing or debt collection effort, make this statute a gold mine for entrepreneurial plaintiffs' firms, and hundreds of firms have taken advantage of the opportunity. The strategies employed by these firms can vary greatly, with some firms looking for a quick nuisance settlement and others holding out for large class settlements.

Companies continue to lobby Congress and the FCC for changes to what many see as a draconian law that excessively punishes companies for mere technical violations and offers a potential jackpot to plaintiffs and their attorneys. But so far, those efforts have not been successful. As discussed below, however, there is a case pending before the Supreme Court this term that could give defense attorneys a powerful procedural weapon to fight class actions under the TCPA and other federal laws that provide for statutory damages.

Three Things to Watch for in 2016

  1. Will we start to see more settlements in nonpayment card cases?

As noted above, so far, most defendants (and their insurers) have been holding strong in refusing to settle data breach class actions not involving thefts of payment cards. This is due in large part to the fact that defendants have generally been successful in defending these cases at the early stages, either on standing arguments or Rule 12(b)(6) motions. However, given the volume of data breach class actions that continue to be filed, the plaintiffs' bar seems to be banking on the fact that this trend will change, perhaps as more cases survive initial standing challenges.

  1. Will more data breach cases reach the class certification stage?

With more courts finding ways to distinguish Clapper, one common line of defense is weaker than it was a few years ago, so it is natural to presume that more cases in the future will reach the class certification phase. Look for more decisions on class certification in data breach cases over the next couple of years.

  1. How will pending Supreme Court cases impact privacy class action litigation going forward?

There are at least three cases pending this term in the United States Supreme Court that could have an impact on privacy class action litigation going forward.

The first is Spokeo, Inc. v. Robins, No. 13-1339. In its broadest sense, Spokeo presents the issue of whether Congress can enact a statute that confers Article III standing to sue for statutory damages to a person who has not suffered any actual injury. If the Court actually addresses this broad issue in its decision, Spokeo could have a significant impact on privacy litigation, where plaintiffs often raise novel theories of liability based on alleged technical statutory violations as a means to overcome the common problem of not being able to show a present injury. However, the questions posed by the Court during oral argument suggest that the Court's analysis may ultimately be more narrowly tailored to the plain language and congressional intent behind the Fair Credit Reporting Act, the particular federal statute at issue in Spokeo.

A second case, Campbell-Ewald Co. v. Gomez, No. 14-857, presents the question of whether an offer of complete relief to a named plaintiff has the effect of mooting both the individual claims and any proposed class claims brought by the named plaintiff. The circuit courts of appeals were initially split on this question but recently have come into alignment in concluding that an unaccepted offer of settlement does not moot a named plaintiff's claims. The questions posed during oral argument in Campbell-Ewald suggest that the Court is split, with Justice Kennedy appearing to be the likely swing vote. If the Court does ultimately go against the circuit courts and hold that an unaccepted offer moots both individual and class claims, the decision could create a significant tool for defendants in avoiding exposure in a variety of consumer class actions, including privacy class actions.

The final case that has a potential to impact privacy class actions is Tyson Foods, Inc. v. Bouaphakeo, No. 14-1146, in which the questions presented include the extent to which individual differences in the harm suffered by class members can be ignored and statistical methods be used instead in deciding whether to certify a case as a class action. However, comments made by several justices during oral argument reflect that this case will likely be resolved on FLSA-specific grounds rather than on any more general examination of the class certification requirements of Rule 23 of the Federal Rules of Civil Procedure. If the decision does involve an examination of the types of statistical evidence that can justify class certification under Rule 23, however, it may be impactful as more privacy cases reach the class certification phase. This is because, just as in wage and hour litigation, statistical methods have been proposed as a way of resolving the problem of variation of injury and causation between class members in data privacy cases, most notably in the Hannaford payment card data breach litigation. See In re: Hannaford Brothers Co. Customer Data Breach Litigation, 293 F.R.D. 21, 30-32 (D. Me. 2013).

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
 
In association with
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.