KEVIN JOSEPH KELLY; KARRIEM BEY, On behalf of themselves and all others similarly situated v. REALPAGE INC., d/b/a ONSITE; RP ON SITE, LLC.
No. 21-1672
United States Court of Appeals for the Third Circuit
August 24, 2022
2022 Decisions 634
Before: GREENAWAY, JR., KRAUSE, and PHIPPS, Circuit Judges
PRECEDENTIAL. On Appeal from the District Court for the Eastern District of Pennsylvania (E.D. Pa. No. 2-19-cv-01706). United States District Judge: Honorable Joshua D. Wolson. Argued December 15, 2021.
James A. Francis
John Soumilas [ARGUED]
Francis Mailman Soumilas
1600 Market Street
Suite 2510
Philadelphia, PA 19103
Counsel for Appellants
Ronald I. Raether, Jr.
Troutman Pepper
5 Park Plaza
Suite 1400
Irvine, CA 92614
Misha Tseytlin [ARGUED]
Troutman Pepper
227 West Monroe Street
Suite 3900
Chicago, IL 60606
Counsel for Appellees
Mark W. Mosier
Covington & Burling
850 10th Street, N.W.
One City Center
Washington, DC 20001
Counsel for Amici Curiae Consumer Data Industry Association and Professional Background Screening Association
Mayer Brown
1999 K Street, N.W.
Washington, DC 20006
Counsel for Amicus Curiae Chamber of Commerce of the United States of America
OPINION
KRAUSE, Circuit Judge.
In late 2018, Appellants Kevin Kelly and Karriem Bey found themselves in just the sort of frustrating predicament the Fair Credit Reporting Act (“FCRA“),
I. FACTUAL AND PROCEDURAL BACKGROUND
To place the parties and their interactions in context, we begin with a brief overview of the FCRA before recounting the history of this case.
A. The Fair Credit Reporting Act
In the FCRA, Congress sought to address the problem of “inaccurate or arbitrary information” in consumer reports by requiring credit reporting agencies (“CRAs“)1 to “utilize accurate, relevant, and current information in a confidential and responsible manner.” Cortez v. Trans Union, LLC, 617 F.3d 688, 706 (3d Cir. 2010) (quoting Guimond v. Trans Union Credit Info. Co., 45 F.3d 1329, 1333 (9th Cir. 1995)); see also Bibbs v. Trans Union LLC, — F.4th —, 2022 WL 3149216, at *3 (3d Cir. 2022) (explaining that, in enacting the FCRA,
But the FCRA also sought to address another problem: the consumer‘s “lack of access to the information in [her] file [and] the difficulty in correcting inaccurate information.” Cortez, 617 F.3d at 706 (internal quotation marks omitted) (quoting S. Rep. No. 91–517, at 3 (1969)). To that end, it broadly defined “file” to mean “all of the information on th[e] consumer recorded and retained by a consumer reporting agency regardless of how the information is stored,”
B. RealPage‘s Rental Reports
RealPage is a CRA that specializes in providing property managers with consumer reports, which it terms “Rental Reports,” to help them evaluate their prospective tenants. See
Consistent with its obligations under the FCRA, RealPage also disclosed information in response to consumers’ direct requests for their files, which could be submitted in two ways. For one, a consumer could use a form on RealPage‘s website to request a “report and any of the disclosures required by the federal Fair Credit Reporting Act.” Appellants’ Br. 23 (emphasis omitted); Appellees’ Br. 47. In that case, the form would automatically generate an email sent to a dedicated email inbox maintained by RealPage, and RealPage would manually process the request. J.A. 80, 134, 180. Alternatively, a consumer could personally contact a RealPage representative by phone, letter, or email to request their information. J.A. 179–80.
As it turned out, however, regardless of whether a consumer downloaded her courtesy copy of a Rental Report requested by a property manager or initiated her own independent request for her information on file, RealPage provided the consumer with the exact same report, the Rental
C. The Parties
Appellants Kevin Kelly and Karriem Bey are two prospective tenants whose Rental Reports contained inaccuracies and who therefore sought information from RealPage to try to correct those errors. J.A. 5. After Kelly and Bey submitted lease applications for apartments at different properties, the respective property managers requested Appellants’ consumer reports from RealPage. In response, RealPage generated and sent their clients Appellants’ Rental
Upon learning of the inaccuracies in their reports, Kelly and Bey contacted RealPage, hoping to determine the sources of the errors and to correct them. Kelly made requests both using the form on RealPage‘s website that requested a “report and any of the disclosures required by the federal Fair Credit Reporting Act,” Appellants’ Br. 23 (emphasis omitted), and by mailing a written request to RealPage for “a copy of all of the information that [was] in [his] file.” J.A. 204, 144–45. Bey called RealPage to “let [him] get [his] file” so that he could “correct” the errors. J.A. 233–35. What both Appellants received was simply the Rental Report that RealPage provided to the property manager, J.A. 231–33, and neither Rental Report identified the third-party vendors that sourced the inaccurate records to RealPage. J.A. 33-43, 50-54. Yet without proof from accurate records, RealPage refused to alter the information on the Rental Reports, and without the identity of the third-party vendors, neither Kelly nor Bey could obtain that proof. See, e.g., J.A. 235–38.
Both Appellants attempted unsuccessfully to obtain proof elsewhere and both suffered adverse consequences. Bey
D. The Proceedings Below
In April 2019, Kelly and Bey initiated this putative class action against RealPage, alleging, among other things, willful and negligent violations of Section 1681g. See
After RealPage answered the complaint, Kelly and Bey moved to certify the following class and subclass:
- an “All Requests” class, including individuals “who had a Rental Report sent or caused to be sent to them by RealPage, Inc. through its On-Site operation which did not include the name of the private vendor source(s) from which public record information in the file was obtained” within the Class Period; and,
- a “Direct Requests” subclass consisting of individuals in the All Requests class who received a Rental Report “following a documented direct request by the consumer” to RealPage or On-Site.
J.A. 74–75.
These class definitions reflect the three different methods by which putative class members could have received their Rental Reports during the Class Period, i.e., as a courtesy copy of the property manager‘s report; through a consumer‘s
In deciding Appellants’ motion for class certification, the District Court first addressed the issue of standing. RealPage sought to have the motion denied and the complaint dismissed on the ground that Appellants had failed to allege a concrete injury. But the District Court rejected that argument, holding that the deprivation of information to which Appellants claimed to be legally entitled was a cognizable injury for purposes of Article III standing. J.A. 10.
On the merits of the class certification motion, however, the District Court sided with RealPage, declining to certify either the All Requests class or the Direct Requests subclass. Appellants, the Court recognized, had the burden to establish “the four requirements of Rule 23(a) of the Federal Rules of Civil Procedure,” i.e., “numerosity, commonality, typicality,
Here, the Court held that Appellants failed to establish predominance and superiority and that neither class was ascertainable. Fundamental to the District Court‘s analysis was its interpretation of Section 1681g(a) as imposing a disclosure obligation on CRAs only when (1) the consumer makes a direct request of the CRA, and (2) that consumer specifically requests her “file” and not merely her “report.” J.A. 12–13. Applying that interpretation, the Court held that individual questions regarding whether consumers’ requests were direct or indirect and whether consumers requested their “files” or “reports” would predominate over common questions, preventing the class action from being superior to individual actions. J.A. 19–23. The Court also concluded that neither the class nor the subclass was ascertainable because identifying class members would require determining which Rental Reports contained public record information and thus would require “[a] review of each individual file [which] is, of course, not administratively feasible.” J.A. 15–16.
Appellants also sought leave to redefine the subclass and to file a renewed motion for class certification to address the District Court‘s ascertainability and predominance concerns in light of the Court‘s novel interpretation of
Appellants then filed a petition for interlocutory review under
II. JURISDICTION AND STANDARD OF REVIEW
The District Court had jurisdiction under
We review an order denying class certification “for abuse of discretion, which occurs if the district court‘s decision rests upon a clearly erroneous finding of fact, an errant conclusion of law or an improper application of law to fact.” Marcus v. BMW of N. Am., LLC, 687 F.3d 583, 590 (3d Cir. 2012) (quoting In re Hydrogen Peroxide Antitrust Litig., 552 F.3d 305, 312 (3d Cir. 2009)). We review legal standards applied by the District Court de novo. Byrd, 784 F.3d at 161; see also McNair v. Synapse Grp. Inc., 672 F.3d 213, 222 n.9 (3d Cir. 2012) (standard of review for standing on Rule 23(f) appeal is plenary).
III. DISCUSSION
RealPage argues that Appellants lack a sufficiently concrete injury to satisfy the Supreme Court‘s standing requirements, while Appellants challenge the District Court‘s grounds for denying class certification. We first address whether Appellants established standing before discussing the District Court‘s rulings on predominance and ascertainability.
A. Standing7
The District Court held that RealPage‘s failure to disclose source information was cognizable as an
To establish standing, a plaintiff—whether acting in her individual capacity or as a putative class representative—bears the burden of establishing: “(1) an injury-in-fact; (2) that is fairly traceable to the defendant‘s challenged conduct; and (3) that is likely to be redressed by a favorable judicial decision.” St. Pierre v. Retrieval-Masters Creditors Bureau, Inc., 898 F.3d 351, 356 (3d Cir. 2018) (citing Lujan v. Defs. of Wildlife, 504 U.S. 555, 590 (1992)); see also Spokeo, 578 U.S. at 338 n.6. At issue here is the first element of injury-in-fact, and specifically, the requirement that the alleged injury be concrete—that is, “real” as opposed to “abstract,” TransUnion, 141 S. Ct. at 2204 (quoting Spokeo, 578 U.S. at 340), “even in the context of a statutory violation,” Spokeo, 578 U.S. at 341. We first consider what showing of concreteness is required under the Supreme Court‘s informational injury cases and then address whether, under that case law, Appellants have established such an injury.
a. The Informational Injury Doctrine
With the rapid onset of the Information Age, the Supreme Court‘s jurisprudence on standing to challenge the
change the personal jurisdiction question with respect to class actions.” (collecting cases)).
Drawing on the Court‘s most recent pronouncements in TransUnion, RealPage argues that Appellants fail to state an informational injury because they allege only a “bare procedural violation” and “identified no downstream consequences” from the omitted source information, Appellees’ Br. 26, 30 (quoting TransUnion, 141 S. Ct. at 2213–14).8 RealPage would have us hold that Appellants
But TransUnion did not cast doubt on the broader import of those decisions. In fact, the Court cited Public Citizen and Akins with approval, reaffirming their continued viability and putting TransUnion in context. See TransUnion, 141 S. Ct. at 2214. These earlier cases show that “a plaintiff suffers an ‘injury in fact’ when [she] fails to obtain information which must be publicly disclosed pursuant to a statute,” Akins, 524 U.S. at 21 (citing Public Citizen, 491 U.S. at 449), and that an informational injury is sufficiently concrete where the failure to disclose is “directly related to” to the purpose of the statute,
Spokeo, which immediately preceded TransUnion, made a similar point. Like the Court in TransUnion, the Spokeo Court cited Public Citizen and Akins with approval, explaining that a plaintiff “need not allege any additional harm beyond the one Congress has identified” in enacting the statute, contrasting the situation where, for example, a consumer reporting agency provided information that was “entirely accurate” and merely “fail[ed] to provide the required notice to a user of the agency‘s consumer information.” 578 U.S. at 342. That injury wouldn‘t be sufficiently concrete because, notwithstanding the
In TransUnion, the Supreme Court applied this framework to its passing analysis of informational injury. It rejected an argument that the plaintiffs had suffered an informational injury under Public Citizen and Akins when TransUnion allegedly failed to provide them with required disclosures in a format specified by the
Whether framed as “adverse effects” or a “downstream consequence[],” TransUnion, 141 S. Ct. at 2214, the upshot is the same: a plaintiff seeking to assert an informational injury must establish a nexus among the omitted information to which she has entitlement, the purported harm actually caused by the specific violation, and the “concrete interest” that Congress identified as “deserving of protection” when it created the disclosure requirement. Tailford v. Experian Info. Sols., Inc., 26 F.4th 1092, 1100 (9th Cir. 2022); see also TransUnion, 141 S. Ct. at 2214. Notably, in none of these cases were the plaintiffs required to allege or prove that they would do anything with the information once disclosed, nor did
In the wake of TransUnion, other Courts of Appeals have likewise concluded that “depriv[ation] of information to which [one] is legally entitled” constitutes a sufficiently concrete informational injury when that omission causes “adverse effects” and the information has “some relevance” to an interest of the litigant that the statute was intended to protect. Laufer v. Looper, 22 F.4th 871, 880-81 & n.6 (10th Cir. 2022) (quoting Griffin v. Dep‘t of Lab. Fed. Credit Union, 912 F.3d 649, 654 (4th Cir. 2019)); see also Harty v. W. Point Realty, Inc., 28 F.4th 435, 444 (2d Cir. 2022) (same); Laufer v. Arpan LLC, 29 F.4th 1268, 1280-82 (11th Cir. 2022) (Jordan, J., concurring) (describing Public Citizen and Akins as requiring an omission of information and concomitant “downstream consequences“). In the
In sum, rather than working a sea change to its informational injury jurisprudence, the Supreme Court in TransUnion simply reiterated the lessons of its prior cases: namely, to state a cognizable informational injury a plaintiff must allege that “they failed to receive . . . required information,” and that the omission led to “adverse effects” or other “downstream consequences,” TransUnion, 141 S. Ct. at 2214 (internal quotation omitted), and such consequences have
b. Appellants Have Standing
Applying these precepts here, Appellants have standing because they have made the requisite showing of (1) the omission of information to which they claim entitlement, (2) “adverse effects” that flow from the omission, and (3) the requisite nexus to the “concrete interest” Congress intended to protect.
As to the first requirement, the
Finally, RealPage‘s failure to disclose the third-party vendor information satisfied the third requirement by preventing Appellants from obtaining “fair and accurate reporting of their credit information,” Tailford, 26 F.4th at 1100, frustrating Congress‘s goal of empowering consumers to “correct[] inaccurate information” in their credit files and preventing them “from being unjustly damaged because of inaccurate or arbitrary information in [their] credit report[s],” Cortez, 617 F.3d at 706 (internal quotations omitted).
And contrary to RealPage‘s contention, whether Appellants would have taken action on the third-party vendor
Appellants have made those allegations here, so we uphold the District Court‘s determination that Appellants have standing.
B. Class Certification
Though we agree with the District Court‘s standing analysis, we disagree, at least in part, with its bases for denying class certification, predominance, and ascertainability.
a. Predominance11
We begin with predominance. To determine whether this requirement is satisfied, a court must engage in a “rigorous
1. Does Section 1681g(a) Require a Direct Request from a Consumer to Trigger Disclosure Obligations?
We have never addressed the question whether
The text of the
The text of
The enumerated categories of information that
Our construction of
Likewise, the
The sharp constraint on third parties’ participation in the
Finally, a comparison of
It is also telling that these other sections specify when the consumer‘s authorization is needed and when the consumer may request disclosure to third parties, whereas
Notably, the disclosures that can be requested by third party users are also far more circumscribed than those provided under
In sum, the text, context, and structure of the
2. Is Section 1681g(a)‘s Disclosure Obligation Triggered Only by a Request for a “File“?
We next consider RealPage‘s argument that
We read the statute differently. No doubt, the statute defines the terms, “file” and “consumer report” and gives them different meanings. Compare
We begin with the statutory text, which—at least in the context of describing disclosures—does not specify that the subject of the request even be the “file.” To the contrary,
To the contrary, it is apparent that Congress used the terms “consumer report” and “file” interchangeably in
Regulations promulgated under the
RealPage‘s construction is also at odds with the statutory goals identified by Congress. See
In short, when read as a whole, the statute is unambiguous in providing that any generalized “request” by a consumer for the
b. Ascertainability
In considering whether to certify a class, a court must perform a two-pronged “rigorous analysis” to determine whether ascertainability and Rule 23(b)(3)‘s requirements are satisfied. In re Hydrogen Peroxide, 552 F.3d at 309 (citation omitted). In determining whether the ascertainability requirement is satisfied, it must determine that the plaintiff has (1) “defined [the class] with reference to objective criteria,” and (2) identified a “reliable and administratively feasible mechanism for determining whether putative class members fall within the class definition.” Byrd, 784 F.3d at 163 (quoting Hayes, 725 F.3d at 355).19
Most of the facts relevant to ascertainability are undisputed: RealPage concedes that it has records of the relevant files, J.A. 131-32, 141, 154-55, 285-86; see Appellants’ Br. 21; Appellees’ Br. 49-54, that it produced only Rental Reports to consumers in response to consumers’ direct requests, J.A. 4, 117-18, 124, and that it always omitted third-party vendor information from Rental Reports that contained public information during the Class Period, J.A. 126, 131-32. All that remains to ascertain is: (1) which consumers directly requested their files, and (2) of the files directly requested, which contained public record information.
As for the first task, RealPage argues that because the records are kept in separate databases with no “unique identifier” used across both systems, it would be difficult to match its records on requests received via its website with its records on Rental Reports sent out in response to those requests. Appellees’ Br. 51. Yet, that matching of records is precisely the sort of exercise we have found sufficiently
But what of the second task? Is it administrable to identify which files contain public record information where that is clear from the face of each file but would require a file-by-file review? The District Court apparently took from our precedent a per se rule that “[a] review of each individual file is . . . not administratively feasible.” J.A. 16. But that is not the case, so we take this opportunity to clarify what our case law requires.
We first adopted the ascertainability requirement in Marcus v. BMW of North America, LLC, where we held a class is not ascertainable where “class members are impossible to identify without extensive and individualized fact-finding or ‘mini-trials.‘” 687 F.3d at 593. And in Marcus and our next two ascertainability cases, Hayes v. Wal-Mart Stores, Inc. and Carrera v. Bayer Corp., we explained that putative classes are not ascertainable where either a defendant‘s records do not contain the information needed to ascertain the class or the records do not exist at all, leading to the “mini-trials” that we disapproved of in Marcus. See Hayes, 725 F.3d at 355; Carrera v. Bayer Corp., 727 F.3d 300, 307-08 (3d Cir. 2013). But, as we qualified in Byrd v. Aaron‘s Inc., ascertainability does not mean that “no level of inquiry as to the identity of class members can ever be undertaken,” because that would make Rule 23(b)(3) class certification all but impossible. 784 F.3d at 171 (emphasis in original). We also cautioned that “the size of a potential class and the need to review individual files to identify its members are not reasons to deny class
We confirmed these parameters in Hargrove v. Sleepy‘s LLC, where we held that affidavits in combination with “thousands of pages of contracts, driver rosters, security gate logs, and pay statements” sufficed to ascertain a class of full-time drivers for Sleepy‘s, despite gaps in the records and the work required to synthesize “several distinct data sets.” 974 F.3d at 470, 480. Similarly, in City Select Auto Sales Inc. v. BMW of North America we held that “[a]ffidavits, in combination with records or other reliable and administratively feasible means,” could satisfy our ascertainability standard, 867 F.3d at 441, remanding to determine whether there were any gaps in a database not produced below that could make identifying putative class members unadministrable, id. at 442 & n.5.
Together, Byrd, Hargrove, and City Select instruct that a straightforward “yes-or-no” review of existing records to identify class members is administratively feasible even if it requires review of individual records with cross-referencing of voluminous data from multiple sources. And that is precisely what we have here. Verifying whether there is public record information in the file requires only an examination of the face of Rental Reports that are indisputably in RealPage‘s possession, J.A. 131-32, 141, 154-55, 285-86, and does not require the sort of mini-trial or individualized fact finding at issue in Marcus, Hayes, and Carrera. Indeed, the review required here is even more straightforward than in Byrd, Hargrove, and City Select, as Appellants have already identified the records they require, demonstrated they are in
To the extent RealPage‘s objection is to the number of records that must be individually reviewed, that is essentially an objection to the size of the class, which we stated explicitly in Byrd is not a reason to deny class certification. 784 F.3d at 171. To hold otherwise would be to categorically preclude class actions where defendants purportedly harmed too many people, which would “seriously undermine the purpose” of a class action to “vindicate meritorious individual claims in an
In sum, the District Court misapprehended our case law and therefore erred in denying certification of the Direct Requests subclass on the basis of ascertainability, as well as predominance.
IV. CONCLUSION
For the foregoing reasons, we will vacate the District Court‘s order denying class certification of the Direct Requests subclass and remand for the Court‘s reconsideration in light of this opinion.
Notes
However, we will not accept RealPage‘s request that we address the District Court‘s rulings on personal jurisdiction and partial summary judgment, Appellee‘s Br. 54–65; Appellee‘s May 26, 2021 Supp. Ltr. 1, because those two issues are beyond the scope of “Rule 23(f) inquiries.” McKowan Lowe & Co. v. Jasmine, Ltd., 295 F.3d 380, 390 (3d Cir. 2002). In any event, RealPage‘s personal jurisdiction argument, premised on the Supreme Court‘s recent decision in Bristol-Myers Squibb Co. v. Superior Ct., 137 S. Ct. 1773 (2017), is foreclosed by our recent decision in Fischer v. Fed. Express Corp., — F.4th —, 2022 WL 2922359, at *5 (3d Cir. 2022) (“[W]e agree with many of our colleagues across the appellate and trial benches who [have held] that Bristol-Myers did not
