United States: Spokeo v. Robins: The U.S. Supreme Court Finds Concrete Injury Is Required Under Article III But Remands Back To The Ninth Circuit

Seyfarth Synopsis: In deciding Spokeo v. Robins, the U.S. Supreme Court reaffirmed that plaintiffs seeking to establish that they have standing to sue must show "an invasion of a legally protected interest" that is particularized and concrete — that is, the injury "must actually exist." Bare procedural violations are not enough.

Today, the U.S. Supreme Court issued its long awaited decision in Spokeo, Inc. v. Robins, No. 13-1339 (U.S. 2016), which we have been watching closely for its possible dramatic implications on the future of workplace class action litigation.

In a 6 to 2 opinion authored by Justice Samuel A. Alito, Jr., the Supreme Court held that the Ninth Circuit's injury-in-fact analysis under Article III was incomplete. According to the Supreme Court, of the two required elements of injury in fact, the Ninth Circuit addressed only "particularization," but not "concreteness," which requires a plaintiff to allege a "real" and not "abstract" injury. Nevertheless, the Supreme Court took no position on the correctness of the Ninth Circuit's ultimate conclusion: whether Robins adequately alleged an injury in fact.

Based on its conclusion, the Supreme Court vacated the Ninth Circuit's ruling and remanded for further consideration consistent with the Opinion. Justice Thomas concurred, while Justice Ginsburg (joined by Justice Sotomayor) dissented.

Given the stakes and the subject matter, the ruling is a "must read" for corporate counsel and all employers.

The Case's Background

This ruling is likely to have substantial impact on class action litigation overall, as we have discussed in our prior posts here, here, and here.

In Spokeo, the issues focused on the Fair Credit Reporting Act ("FCRA"), which requires that consumer reporting agencies ("CRAs") follow reasonable procedures to assure maximum possible accuracy of its consumer reports (15 U.S.C. § 1681e(b)), issue specific notices to providers and users of information (1681e(d)), and post toll-free phone numbers to allow consumers to request their consumer reports (1681b(e)).

The purported CRA in this case was Spokeo, Inc. ("Spokeo"), which operates a "people search engine" — it aggregates publicly available information about individuals from phone books, social networks, marketing surveys, real estate listings, business websites, and other sources, which it organizes into comprehensive, easy-to-read profiles. Notably, Spokeo specifically states that it "does not verify or evaluate each piece of data, and makes no warranties or guarantees about any of the information offered . . .," and warns that the information is not to be used for any purpose addressed by the FCRA, such as determining eligibility for credit, insurance, employment, etc.

In July 2010, Plaintiff Thomas Robins filed a putative class action alleging that Spokeo violated the FCRA because it presented inaccurate information about him. He alleged that Spokeo reported that he had a greater level of education and more professional experience than he in fact had, that he was financially better off than he actually was, and that he was married (he was not) with children (he did not have any). But beyond identifying the inaccuracies, he did not allege any actual damages. Instead, he argued that Spokeo's alleged FCRA violation was "willful" and therefore he sought statutory damages of between $100 and $1,000 for himself, as well as for each member of the purported nationwide class.

The district court dismissed the case, finding that "where no injury in fact is properly pled" a plaintiff does not have standing to sue. In February 2014, the U.S. Court of Appeals for the Ninth Circuit reversed, holding that the "violation of a statutory right is usually a sufficient injury in fact to confer standing" and that "a plaintiff can suffer a violation of the statutory right without suffering actual damages."

In its petition for certiorari, Spokeo posed the following question to the Supreme Court: "Whether Congress may confer Article III standing upon a plaintiff who suffers no concrete harm and who therefore could not otherwise invoke the jurisdiction of a federal court, by authorizing a private right of action based on a bare violation of a federal statute." Spokeo highlighted a circuit split, as the Fifth, Sixth, and Seventh Circuits previously lined up with the Ninth Circuit's approach, while the Second, Third, and Fourth Circuits generally disagreed and required an actual, concrete injury.

After being granted certiorari, Spokeo argued that the Ninth Circuit's holding was inconsistent with the Supreme Court's precedents, the Constitution's text and history, and principles of separation of powers. More specifically, Spokeo argued that Robin's bare allegations of FCRA violations, without any accompanying concrete or particularized harm, were insufficient to establish an injury in fact, and thus failed to establish Article III standing.

Robins responded that the Supreme Court's precedent established that Congress may create private rights of action to vindicate violations of statutory rights that are redressable through statutory damages.

The U.S. Solicitor General also weighed in, appearing as an amicus in support of Robins, and argued that the Supreme Court should focus on the specific alleged injury — the public dissemination of inaccurate personal information — and, specifically, the FCRA. The Government argued that the FCRA confers a legal right to avoid the dissemination of inaccurate personal information, which is sufficient to confer standing under Article III.

The Supreme Court's Decision

Writing for the majority on the Supreme Court, Justice Alito held that Ninth Circuit failed to consider both aspects of the injury-in-fact requirement under Article III when analyzing Robin's alleged injury, therefore its Article III standing analysis was incomplete. Slip. Op. at *8. The Supreme Court determined that to establish injury in fact under Article III, a plaintiff must show that he or she suffered "an invasion of a legally protected interest" that is both "concrete and particularized." Slip. Op. at *7. For an injury to be "particularized," it "must affect the plaintiff in a personal and individual way." Id. "Concreteness," the Supreme Court found "is quite different from particularization." Id. at *8. A concrete injury must "actually exist" and must be "real" and not "abstract." Id.

The Supreme Court further stated that concreteness includes both easy to recognize tangible injuries as well as intangible injuries. Id. at 8-9. The Supreme Court instructed that when considering intangible injuries, "both history and the judgment of Congress play important roles." Id. In particular, Congress may identify intangible harms which meet Article III's minimum requirements. Id. Nevertheless, the Supreme Court cautioned that plaintiffs do not "automatically" meet the injury-in-fact requirement where the violation of a statutory right provides a private right of action. Id. Thus "Robins could not, for example, allege a bare procedural violation divorced from any concrete harm, and satisfy the injury-in-fact requirement of Article III." Id. The Supreme Court also added that the "risk of real harm" may also satisfy the concreteness requirement, where harms "may be difficult to prove or measure." Id.

Viewing the FCRA in light of these principles, the Supreme Court recognized that while Congress "plainly sought to curb the dissemination of false information by adopting procedures designed to decrease that risk . . .[,] Robins cannot satisfy the demands of Article III by alleging a bare procedural violation." For example, the Supreme Court noted it would be "difficult to imagine how the dissemination of an incorrect zip code, without more, could work any concrete harm." Id. at * 11.

Justice Thomas concurred, reviewing the historical development of the law of standing and its application to public and private rights of action, finding the standing requirement a key component to separation of powers.

Justice Ginsberg, joined by Justice Sotomayor, largely agreed with the majority, but nevertheless dissented. She departed from the majority's reasoning on the issue of concreteness, but based on the injury alleged, not on the fact that concrete harm wasn't required. Id. at *3 (Ginsberg, J., dissenting). Under her analysis, Justice Ginsberg would have found that the nature of Robin's injury was sufficiently concrete because of his allegation that the misinformation caused by Spokeo "could affect his fortune in the job market." Id. at *3-5 (Ginsberg, J., dissenting).

Implications For Employers

Spokeo can be interpreted as a compromise – with some useful language and reasoning for employers to use in future cases. While the Supreme Court avoided a broader question of Congress's ability to create private rights of action and other weighty separation of powers issues, it announced the proper analytic framework for assessing the injury-in-fact requirement under Article III. The Supreme Court provided some good news for employers, consumer reporting agencies, and other corporate defendants, as well as potential plaintiffs with respect to class action litigation under a variety of federal statutes, including the FCRA. In particular, the Supreme Court was clear that alleged injuries must be both particular and concrete, meaning that injuries must be "real" and not "abstract." Thus, a mere procedural violation without any connection to concrete harm cannot satisfy the injury-in-fact requirement of Article III.

However, the Supreme Court may not have shut the door on lawsuits alleging intangible injuries based on violations of statutory rights. While the Supreme Court's opinion today may discourage some consumer, workplace, and other types of class actions seeking millions in statutory damages, potential litigants will likely have to be more creative in how they frame alleged injuries tied to violations of statutory rights.

Spokeo also transcends the employment context, as the constitutional requirement of Article III applies in all civil litigation. Plaintiffs seeking to file lawsuits in other regulated areas, such as under ERISA, the Americans with Disabilities Act, as well as a host of other statutes are likewise affected by today's decision. Without particularized, concrete injury, federal jurisdiction is beyond the reach of plaintiffs seeking statutory damages for technical violations.

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
Gerald L. Maatman Jr.
 
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.