Jose Pena v. Experian Information Solutions, Inc.

• Court: District Court, C.D. California
• Decided: October 24, 2022
• Docket: 8:22-cv-01222
• Status: Unknown

Opinion

Case 8:22-cv-01222-SSS-ADS Document 44 Filed 10/24/22 Page 1 of 6 Page ID #:286

1 2 3 4 5 6 7 8 UNITED STATES DISTRICT COURT 9 FOR THE CENTRAL DISTRICT OF CALIFORNIA 10 11 JOSE PENA, individually, and on Case No. 8:22-cv-01222-SSS-ADSx behalf of all other similarly situated 12 consumers, ORDER DENYING PLAINTIFF’S 13 Plaintiff, MOTION TO REMAND CASE TO 14 STATE COURT [DKT. 22] v. 15 EXPERIAN INFORMATION 16 SOLUTIONS, INC., and DOES 1 17 through 10, inclusive,

18 Defendants. 19 20 21 22 23 24 25 26 27 28 Case 8:22-cv-01222-SSS-ADS Document 44 Filed 10/24/22 Page 2 of 6 Page ID #:287

1 Before the Court is Plaintiff Jose Pena’s Motion to Remand Case to State 2 Court. [Dkt. 22]. The Court has reviewed the Parties’ submissions and, for the 3 reasons below, DENIES Plaintiff’s motion. 4 I. BACKGROUND 5 Plaintiff filed this action on behalf of a putative class against Experian 6 Information Solutions, Inc. (“Experian”) in Orange County Superior Court 7 alleging Experian willfully violated the federal Fair Credit Reporting Act, 8 15 U.S.C. § 1681 et seq. (the “FCRA”) and the California Consumer Credit 9 Reporting Agencies Act, Cal. Civ. Code § 1785 et seq., by failing to inform 10 consumers that the consumer reports Experian sells to its customers associate 11 said consumers with the U.S. Department of Treasury’s Office of Foreign 12 Assets Control (“OFAC”) watchlist of terrorists, narcotics traffickers, money 13 launderers, arms dealers, and other criminals subject to U.S. government 14 sanctions. Experian removed the action to this Court on June 27, 2022. [Dkt. 15 1]. Plaintiff now seeks to remand the action to state court, arguing that he and 16 the putative class lack Article III standing to be heard in federal court. 17 II. LEGAL STANDARD 18 “Standing is a constitutional requirement for the exercise of subject 19 matter jurisdiction over disputes in federal court.” Tailford v. Experian 20 Information Solutions, Inc., 26 F.4th 1092 (9th Cir. 2022) (citing Spokeo, Inc. v. 21 Robins, 578 U.S. 330, 339 (2016)). A key component of standing is satisfaction 22 of the injury-in-fact requirement: that Plaintiff has “suffered ‘an invasion of a 23 legally protected interest’ that is ‘concrete and particularized’ and ‘actual or 24 imminent, not conjectural or hypothetical.’” Id. 25 “As the party invoking the federal judicial power, Experian has the 26 burden of establishing the facts necessary to support standing ‘with the manner 27 and degree of evidence required at the successive stages of the litigation.’” Id. 28 (citing Lujan v. Defenders of Wildlife, 504 U.S. 555, 561 (1992)). “At the -2- Case 8:22-cv-01222-SSS-ADS Document 44 Filed 10/24/22 Page 3 of 6 Page ID #:288

1 pleading stage, general factual allegations of injury resulting from the 2 defendant’s conduct may suffice, for on a motion to dismiss we ‘presum[e] that 3 general allegations embrace those specific facts that are necessary to support the 4 claim.’” Id. 5 III. DISCUSSION 6 The Ninth Circuit has adopted a two-step framework to determine 7 whether alleged FCRA violations are sufficiently concrete to confer standing: 8 “(1) whether the statutory provisions at issue were established to protect [a 9 plaintiff's] concrete interests (as opposed to purely procedural rights), and if so, 10 (2) whether the specific procedural violations alleged in this case actually harm, 11 or present a material risk of harm to, such interests.” Id. (citing Robins v. 12 Spokeo, Inc. 867 F.3d 1108, 1113 (9th Cir. 2017)). 13 The first prong is satisfied because Plaintiff alleges Experian violated 14 Section 1681g of the FCRA, which was “established to protect concrete 15 interests of privacy and accuracy in the reporting of consumer credit 16 information, and not merely procedural rights.” Tailford, 26 F.4th at 1099. One 17 principal reason for the enactment of the FCRA was the protection of 18 consumers’ interests in “fair and accurate credit reporting” and to “protect 19 consumer privacy,” which “resemble[] other reputation and privacy interests 20 that have long been protected in the law.” Id. (citation omitted). 21 The second prong is also satisfied because Plaintiff alleges non-disclosure 22 of information which presents a material risk of harm to his concrete interest in 23 fair and accurate credit reporting. See Tailford, 26 F.4th at 1100. Indeed, 24 Plaintiff alleges that Defendant published consumer reports to third parties 25 containing false OFAC hit information about Plaintiff and that he “suffered 26 harm in that Defendant falsely associated him with a criminal on the OFAC list 27 and deprived Plaintiff of the information necessary to discover and rectify 28 Defendant’s harmful error.” [Dkt. 1-1 ¶ 51–56]. According to the complaint, -3- Case 8:22-cv-01222-SSS-ADS Document 44 Filed 10/24/22 Page 4 of 6 Page ID #:289

1 Plaintiff thus had no knowledge or opportunity to rectify the provision of false 2 OFAC information to third parties, which violated Plaintiff’s reputation and 3 privacy interests. See Tailford, 26 F.4th at 1100. 4 Plaintiff argues Experian has failed to establish standing because it has 5 not alleged concrete injury required for standing under the FCRA. Plaintiff 6 relies on the Supreme Court’s decision in TransUnion LLC v. Ramirez, 141 S. 7 Ct. 2190 (2021), claiming it “held that the exact claim Plaintiff brings here 8 cannot be heard in federal court.” [Dkt. 22-1 at 13]. Plaintiff is incorrect.1 9 TransUnion did not involve the exact claim Plaintiff brings here. In 10 TransUnion, the plaintiffs alleged TransUnion violated Section 1681g(a)(1) 11 because it sent the plaintiffs copies of their credit files that omitted the 12 plaintiffs’ potential match on the OFAC list, and only included the OFAC 13 information in a second separate mailing. TransUnion, 141 S. Ct. at 2213. 14 Plaintiffs argued they had standing because “the TransUnion mailings were 15 formatted incorrectly and deprived them of their right to receive information in 16 the format required by the statute.” Id. The Supreme Court, however, found the 17 plaintiffs did not have standing because they did not demonstrate that the 18

19 1 Plaintiff cites multiple recent cases alleging FCRA disclosure violations that 20 were remanded to state court. [Dkt. 22-1 at 15–16]. However, all of those cases are inapposite here because none involve allegedly inaccurate information that 21 was excluded from a plaintiff’s disclosure that the plaintiff would have tried to 22 correct had the information been included in the disclosure. Moreover, none of the cases Plaintiff cites alleged the omission of inaccurate information on a 23 consumer disclosure or any “downstream consequences’ from failing to receive required information. See, e.g., Muha v. Experian Info. Sols., Inc., No. 24 CV2200077, 2022 WL 1223635, at *1 (C.D. Cal. Apr. 25, 2022); Grabner v. 25 Experian Info. Sols., Inc., No. CV2200078, 2022 WL 1223636, at *1 (C.D. Cal. Apr. 22, 2022); Mayorga v. Carter’s Inc., No. CV 22-1467, 2022 WL 1190350, 26 at *1 (C.D. Cal. Apr. 21, 2022); Williams v. Nichols Demos, Inc., No. 5:17-CV- 07101, 2018 WL 3046507, at *2 (N.D. Cal. June 20, 2018); Kirkland v. Estes 27 Forwarding Worldwide LLC, No. 18-cv-07324 at ECF 15 (N.D. Cal. Jan. 13, 2019 order remanding); Rivera v. Wells Fargo Bank, N.A., No. 17-cv-06885 at 28 ECF 40 (N.D. Cal. Feb. 11, 2019 order remanding). -4- Case 8:22-cv-01222-SSS-ADS Document 44 Filed 10/24/22 Page 5 of 6 Page ID #:290

1 improper format caused harm with a close relationship to a harm traditionally 2 recognized as providing a basis for a lawsuit in American courts. Id. As an 3 example, the Court noted the plaintiffs did not provide evidence “that the 4 plaintiffs would have tried to correct their credit files—and thereby prevented 5 dissemination of a misleading report—had they been sent the information in the 6 proper format.” Id. The Court thus held that the plaintiffs’ assertions regarding 7 improper format were “bare procedural violation[s], divorced from any concrete 8 harm” and did not suffice to establish standing. Id. 9 Here, in contrast, Plaintiff alleges concrete harm sufficient to establish 10 standing. While it is true that Plaintiff here alleges a violation of the same 11 FCRA provision at issue in TransUnion, namely Section 1681g(a), Plaintiff 12 alleges here what the TransUnion plaintiffs did not. Unlike the TransUnion 13 plaintiffs, who did not assert that they would have tried to correct their credit 14 files and thereby prevent dissemination of a misleading report, TransUnion, 15 141 S. Ct. at 2213, Plaintiff alleges his inaccurate credit report was sent to third 16 parties [Dkt. 1-1 ¶¶ 46–47, 53–55] and that he would have tried to correct his 17 consumer file if his disclosure had been accurately provided to him. [Dkt. 1-1 18 ¶¶ 52, 56]. Moreover, Plaintiff further alleges that the entire putative class was 19 “deprive[d] . . . of the information necessary to rectify any errors concerning 20 their consumer reports,” implying that the putative class would have rectified 21 the errors in the consumer reports were they not deprived of the necessary 22 information. [Dkt. 1-1 ¶ 79]. 23 Additionally, “[u]nlike the [P]laintiff[] here, who allege[s] that certain 24 information was missing from Experian’s § 1681g disclosures, the plaintiffs in 25 TransUnion lacked standing because their only allegation of non-disclosure was 26 improper formatting of the information.” Tailford, 26 F.4th at 1100 (emphasis 27 in original) (citing TransUnion, 141 S. Ct. at 2214 (“The plaintiffs did not allege 28 that they failed to receive any required information. They argued only that they -5- Case 822-cv-01222-SSS-ADS Document 44 Filed 10/24/22 Page6of6 Page ID#:291

1 | received it in the wrong format.’)). Further, the TransUnion plaintiffs failed to 2|| identify “downstream consequences” from failing to receive the required 3] information, such as an inability to correct erroneous information. TransUnion, 4] 1418S. Ct. at 2214. In contrast, Plaintiff has alleged exactly that type of 5 || downstream consequence—that Experian’s omission of the OFAC information 6 || “deprived Plaintiff of the opportunity to rectify Defendant’s error by disputing 7 || that information so that Defendant could properly investigate then correct the 8 || error.” [Dkt. 1-1 7 52]. 9] IV. CONCLUSION 10 Experian has therefore satisfied its burden and established that, at this 11 || stage of the case, Plaintiffs allegations are sufficiently concrete to establish 12 || Article III standing. The Court thus DENIES Plaintiffs motion to remand. 13 14 IT IS SO ORDERED. ( 15 16 || Dated: October 24, 2022 SUNSHINE S¥SYKES 17 United States District Judge 18 19 20 21 22 23 24 25 26 27 28 -6-