1 2 3 4 5 6 7 8 UNITED STATES DISTRICT COURT 9 SOUTHERN DISTRICT OF CALIFORNIA 10 11 Case No.: 21-CV-1485 JLS (BLM) GUILLERMO MATA, individually and
12 on behalf of all others similarly situated, ORDER GRANTING IN PART AND 13 Plaintiff, DENYING IN PART DEFENDANT’S 14 v. MOTION TO DISMISS AND DISMISSING PLAINTIFF’S 15 DIGITAL RECOGNITION NETWORK, COMPLAINT FOR LACK OF INC., a Delaware corporation, STANDING 16 Defendant. 17 (ECF No. 4)
18 19
21 Presently before the Court is Defendant Digital Recognition Network, Inc.’s 22 (“Defendant” or “DRN”) Motion to Dismiss (“Mot.,” ECF No. 4). Plaintiff Guillermo 23 Mata (“Plaintiff”) has filed an Opposition to (“Opp’n,” ECF No. 9), and Defendant has 24 filed a Reply in support of (“Reply,” ECF No. 10), the Motion. The Court took this matter 25 under submission without oral argument pursuant to Civil Local Rule 7.1(d)(1). See ECF 26 No. 6. Having carefully reviewed Plaintiff’s Complaint (“Compl.,” ECF No. 1-3), the 27 Parties’ arguments, and the law, the Court GRANTS IN PART AND DENIES IN PART 28 Defendant’s Motion and DISMISSES Plaintiff’s Complaint for lack of standing. 1 BACKGROUND 2 Defendant is a corporation organized and existing under the laws of Delaware with 3 its principal place of business located in Fort Worth, Texas. See Compl. ¶ 10. Defendant 4 operates an automated or automatic license plate reader (“ALPR”) system within the state 5 of California that collects photographs of vehicles as well as their license plate numbers. 6 Compl. ¶¶ 14, 18–19, 49; see also Cal. Civ. Code § 1798.90.5(a). Defendant uses vehicle- 7 mounted ALPR cameras to collect these photographs, and additionally records the 8 camera’s location and the date and time of the photograph. Id. ¶ 19; see also id. Fig. 2. 9 Defendant uses this data “to provide its customers real-time vehicle location data.” Id. 10 ¶ 18. Defendant’s website states that “[its] platform can build a full, historical story on a 11 vehicle and owner. . . . [Defendant’s] realternative data—license plate recognition data 12 paired with our powerful, exclusive analytics platform—helps build the full vehicle stories 13 our users need to solve their portfolio management, collections, recovery and fraud 14 challenges.” Id. ¶¶ 21–22. Because Defendant operates and uses an ALPR system within 15 California, Plaintiff alleges that it must comply with California Civil Code §§ 1798.90.5 et 16 seq. (the “ALPR statute”), but that it has failed to do so. See generally Compl. 17 Specifically, Plaintiff pleads that Defendant “deliberately collected Plaintiff’s and 18 the putative Class’s ALPR information and disclosed that information to its 1,000 clients 19 allowing them to identify locations visited by Plaintiff and each putative Class member’s 20 vehicles.” Id. ¶ 54. Plaintiff alleges that Defendant’s conduct violates certain notice, 21 privacy, security, and proper-use requirements in the ALPR statute. See generally id. 22 Plaintiff further claims that Defendant “tracked [Plaintiff’s] vehicle, thus gaining access to 23 his home and work address and other sensitive information such as the time he typically 24 leaves and comes home and where he likes to spend his free time,” thereby “disparaging 25 the privacy rights of California citizens,” including Plaintiff. Id. ¶ 8. 26
27 1 The facts alleged in Plaintiff’s Complaint are accepted as true for purposes of Defendant’s Motion. See 28 Vasquez v. Los Angles Cty., 487 F.3d 1246, 1249 (9th Cir. 2007) (holding that, in ruling on a motion to 1 Plaintiff initiated this putative class action on May 26, 2021, in the Superior Court 2 of the State of California for the County of San Diego, asserting a single cause of action 3 against Defendant for violation of the ALPR statute. See generally ECF No. 1 (“Notice of 4 Removal”). On August 8, 2021, Defendant removed to this District based on diversity 5 jurisdiction. See generally id. The instant Motion followed. See Mot. 6 REQUEST TO CONSIDER MATERIALS INCORPORATED BY REFERENCE 7 As an initial matter Plaintiff’s Opposition makes a passing request that the Court 8 take judicial notice of Defendant’s website. Opp’n at 7 n.1 (citing Declaration of Lily E. 9 Hough (“Hough Decl.,” ECF No. 9-1) Ex. A (the “Website,” ECF No. 9-2)). 10 “Generally, district courts may not consider material outside the pleadings when 11 assessing the sufficiency of a complaint under Rule 12(b)(6) of the Federal Rules of Civil 12 Procedure.” Khoja v. Orexigen Therapeutics, Inc., 899 F.3d 988, 998 (9th Cir. 2018) 13 (citation omitted). “There are two exceptions to this rule,” including the incorporation-by- 14 reference doctrine. Id. “Even if a document is not attached to a complaint, it may be 15 incorporated by reference into a complaint if the plaintiff refers extensively to the 16 document or the document forms the basis of the plaintiff’s claim.” United States v. 17 Ritchie, 342 F.3d 903, 908 (9th Cir. 2003) (citations omitted). “‘[T]he mere mention of 18 the existence of a document is insufficient to incorporate the contents of a document’ 19 under Ritchie.” Khoja, 899 F.3d at 1002 (citation omitted). Nonetheless, a document may 20 still form the basis of the plaintiff’s claim where “the claim necessarily depended on 21 the[ document].” Id. (citation omitted). When a document is incorporated by reference, 22 “the district court may treat such a document as part of the complaint, and thus may assume 23 that its contents are true for purposes of a motion to dismiss under Rule 12(b)(6).” Ritchie, 24 342 F.3d at 908. However, “it is improper to assume the truth of an incorporated document 25 if such assumptions only serve to dispute facts stated in a well-pleaded complaint.” Khoja, 26 899 F.3d at 1003. 27 Here, the Court finds that Plaintiff’s claim “necessarily depend[s] on [Defendant’s 28 Website]” and that his Complaint “refers extensively” to Defendant’s Website, Khoja, 899 1 F.3d at 1002 (citation omitted); thus, the Website is incorporated by reference into the 2 Complaint. Indeed, the Complaint not only “mention[s] . . . the existence” of the Website, 3 id. at 1002 (citation omitted), but quotes portions of it throughout, see, e.g., Compl. ¶¶ 18– 4 22, 30–35. Further, the bulk of Plaintiff’s allegations revolve around the alleged failure of 5 Defendant’s policy, posted on the Website, to adhere to the requirements of the ALPR 6 statute. See, e.g., Compl. ¶¶ 55–56. Defendant does not object to Plaintiff’s request, but 7 rather also refers extensively to its Website in its briefing on the Motion. Accordingly, the 8 Court GRANTS Plaintiff’s request to find Defendant’s Website incorporated by reference 9 into the Complaint. 10 MOTION TO DISMISS AND/OR STRIKE 11 I. Legal Standards 12 A. Rule 12(b)(6) Motion to Dismiss 13 Federal Rule of Civil Procedure 12(b)(6) permits a party to raise by motion the 14 defense that the complaint “fail[s] to state a claim upon which relief can be granted,” 15 generally referred to as a motion to dismiss. The Court evaluates whether a complaint 16 states a cognizable legal theory and sufficient facts in light of Federal Rule of Civil 17 Procedure 8(a), which requires a “short and plain statement of the claim showing that the 18 pleader is entitled to relief.” Although Rule 8 “does not require ‘detailed factual 19 allegations,’ . . . it [does] demand more than an unadorned, the-defendant-unlawfully- 20 harmed-me accusation.” Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009) (quoting Bell Atl. 21 Corp. v. Twombly, 550 U.S. 544, 555 (2007)). In other words, “a plaintiff’s obligation to 22 provide the ‘grounds’ of his ‘entitle[ment] to relief’ requires more than labels and 23 conclusions, and a formulaic recitation of the elements of a cause of action will not do.” 24 Twombly, 550 U.S. at 555 (citing Papasan v. Allain, 478 U.S. 265, 286 (1986)). A 25 complaint will not suffice “if it tenders ‘naked assertion[s]’ devoid of ‘further factual 26 enhancement.’” Iqbal, 556 U.S. at 677 (citing Twombly, 550 U.S. at 557). 27 To survive a motion to dismiss, “a complaint must contain sufficient factual matter, 28 accepted as true, to ‘state a claim to relief that is plausible on its face.’” Id. (quoting 1 Twombly, 550 U.S. at 570); see also Fed. R. Civ. P. 12(b)(6). A claim is facially plausible 2 when the facts pled “allow the court to draw the reasonable inference that the defendant is 3 liable for the misconduct alleged.” Iqbal, 556 U.S. at 677 (citing Twombly, 550 U.S. at 4 556). That is not to say that the claim must be probable, but there must be “more than a 5 sheer possibility that a defendant has acted unlawfully.” Id. Facts “‘merely consistent 6 with’ a defendant’s liability” fall short of a plausible entitlement to relief. Id. (quoting 7 Twombly, 550 U.S. at 557). This review requires context-specific analysis involving the 8 Court’s “judicial experience and common sense.” Id. at 675 (citation omitted). “[W]here 9 the well-pleaded facts do not permit the court to infer more than the mere possibility of 10 misconduct, the complaint has alleged—but it has not ‘show[n]’—‘that the pleader is 11 entitled to relief.’” Id. 12 “In reviewing a Rule 12(b)(6) motion to dismiss, a district court must accept as true 13 all facts alleged in the complaint, and draw all reasonable inferences in favor of the 14 plaintiff.” Wi-LAN Inc. v. LG Elecs., Inc., 382 F. Supp. 3d 1012, 1020 (S.D. Cal. 2019) 15 (citing Retail Prop. Trust v. United Bhd. of Carpenters & Joiners of Am., 768 F.3d 938, 16 945 (9th Cir. 2014)). Where a complaint does not survive 12(b)(6) analysis, the Court will 17 grant leave to amend unless it determines that no modified contention “consistent with the 18 challenged pleading . . . [will] cure the deficiency.” DeSoto v. Yellow Freight Sys., Inc., 19 957 F.2d 655, 658 (9th Cir. 1992) (quoting Schreiber Distrib. Co. v. Serv-Well Furniture 20 Co., 806 F.2d 1393, 1401 (9th Cir. 1986)). 21 B. Rule 12(f) Motion to Strike 22 Federal Rule of Civil Procedure 12(f) provides that a court “may strike from a 23 pleading an insufficient defense or any redundant, immaterial, impertinent, or scandalous 24 matter.” “The function of a [Rule] 12(f) motion to strike is to avoid the expenditure of 25 time and money that must arise from litigating spurious issues by dispensing with those 26 issues prior to trial.” Whittlestone, Inc. v. Handi-Craft Co., 618 F.3d 970, 973 (9th Cir. 27 2010) (quoting Fantasy, Inc. v. Fogerty, 984 F.2d 1524, 1527 (9th Cir. 1993), rev’d on 28 other grounds, 510 U.S. 517 (1994)). 1 “Motions to strike are ‘generally disfavored because they are often used as delaying 2 tactics and because of the limited importance of pleadings in federal practice.’” Cortina v. 3 Goya Foods, Inc., 94 F. Supp. 3d 1174, 1182 (S.D. Cal. 2015) (quoting Rosales v. Citibank, 4 133 F. Supp. 2d 1177, 1180 (N.D. Cal. 2001)). “[M]otions to strike should not be granted 5 unless it is clear that the matter to be stricken could have no possible bearing on the subject 6 matter of the litigation.” Colaprico v. Sun Microsys., Inc., 758 F. Supp. 1335, 1339 (N.D. 7 Cal. 1991). “When ruling on a motion to strike, this Court ‘must view the pleading under 8 attack in the light most favorable to the pleader.’” Id. (citing RDF Media Ltd. v. Fox Broad. 9 Co., 372 F. Supp. 2d 556, 561 (C.D. Cal. 2005)). “Unless it would prejudice the opposing 10 party, courts freely grant leave to amend stricken pleadings.” Roe v. City of San Diego, 11 289 F.R.D. 604, 608 (S.D. Cal. 2013) (citing Fed. R. Civ. P. 15(a)(2); Wyshak v. City Nat’l 12 Bank, 607 F.2d 824, 826 (9th Cir. 1979)). 13 II. Analysis 14 Plaintiff’s sole cause of action asserts that Defendant violates the ALPR statute. See 15 Compl. ¶¶ 54–60. Plaintiff alleges that DRN is an “ALPR operator” as defined by the 16 ALPR statute because it “operates an ALPR system.” Cal. Civ. Code § 1798.90.5(c); 17 Compl. ¶¶ 49–51. Additionally, DRN is an “ALPR end-user” because it “accesses or uses 18 an ALPR system.” Cal. Civ. Code § 1798.90.5(a); Compl. ¶ 52. 19 Per the ALPR statute, ALPR operators and end-users must “[m]aintain reasonable 20 security procedures and practices, including operational, administrative, technical, and 21 physical safeguards, to protect ALPR information from unauthorized access, destruction, 22 use, modification, or disclosure.” Cal. Civ. Code § 1798.90.51(a) (ALPR operators); id. 23 § 1798.90.53(a) (ALPR end-users). This, Plaintiff contends, is the statute’s “Security 24 Requirement.” Compl. ¶ 15(i). 25 Among such safeguards, ALPR operators must “[i]mplement a usage and privacy 26 policy to ensure that the collection, use, maintenance, sharing, and dissemination of ALPR 27 information is consistent with respect for individuals’ privacy and civil liberties.” Cal. Civ. 28 Code § 1798.90.51(b)(1). Similarly, ALPR end-users must “[i]mplement a usage and 1 privacy policy in order to ensure that the access, use, sharing, and dissemination of ALPR 2 information is consistent with respect for individuals’ privacy and civil liberties.” Id. 3 § 1798.90.53(b)(1). This, Plaintiff contends, is the statute’s “Privacy Requirement.” 4 Compl. ¶ 15(ii). 5 “The usage and privacy policy shall be available to the public in writing, and, if the 6 ALPR [operator and/or end-user] has an Internet Web site, the usage and privacy policy 7 shall be posted conspicuously on that Internet Web site.” Cal. Civ. Code 8 §§ 1798.90.51(b)(1) (ALPR operators), 1798.90.53(b)(1) (ALPR end-users). The usage 9 and privacy policy is required to include, at a minimum, specified information that varies 10 depending on whether the person in question is an ALPR operator or end-user. Id. 11 §§ 1798.90.51(b)(2) (ALPR operators), 1798.90.53(b)(2) (ALPR end-users). This, 12 Plaintiff contends, is the statute’s “Notice Requirement.” Compl. ¶ 15(iii). 13 Additionally, ALPR operators who access or provide access to ALPR information 14 must maintain detailed records of such access. Cal. Civ. Code § 1798.90.52(a). This, 15 Plaintiff contends, is the statute’s “Audit Requirement.” Compl. ¶ 16(i). Finally, ALPR 16 operators must “[r]equire that ALPR information only be used for the authorized purposes 17 described in the usage and privacy policy.” Cal. Civ. Code § 1798.90.52(b). This, Plaintiff 18 contends, is the statute’s “Proper Use Requirement.” Compl. ¶ 16(ii). 19 The ALPR statute authorizes “an individual who has been harmed by a violation of 20 this title” to bring a civil action. Cal. Civ. Code § 1798.90.54(a). A plaintiff in such an 21 action may seek a combination of actual damages (not less than liquidated damages in the 22 amount of $2,500); punitive damages “upon proof of willful or reckless disregard of the 23 law”; attorneys’ fees and costs; and preliminary or equitable relief. Id. § 1798.90.54(b). 24 Plaintiff contends that DRN has failed to comply with the ALPR statute’s Notice, 25 Privacy, Security, and Proper Use Requirements, and that he and the Class have been 26 harmed by these violations “because their private and sensitive personal information has 27 been improperly collected and used without their notice or consent.” See Compl. ¶¶ 54– 28 60. 1 Defendant argues that Plaintiff fails to state a claim because he fails to allege 2 sufficient plausible facts to establish that he has suffered any actionable harm as a result of 3 a violation of the ALPR statute. See Mot. at 5–7. Defendant further seeks to dismiss or 4 strike Plaintiff’s claim for punitive damages for failure to allege sufficiently egregious 5 conduct. See id. at 7–8. 6 The Court analyzes each of Defendant’s arguments in turn. 7 A. Sufficiency of the Complaint’s Allegations 8 Defendant argues that “[Plaintiff] fails to allege the existence of any actionable 9 ‘harm’ that he or any members of his purported class may have suffered.” Mot. at 5. 10 Plaintiff responds that “DRN frames this argument as going to the merits, though it uses 11 the language of Article III standing.” Opp’n at 10. Nonetheless, Plaintiff argues that 12 “under either a constitutional or statutory analysis it is clear that Plaintiff alleges precisely 13 the type of harm the statute was designed to prevent: intrusions upon his individual privacy 14 rights.” Id. at 2. Plaintiff elaborates that, “because DRN failed to embrace the safeguards 15 outlined by the ALPR statute, [Plaintiff’s] privacy interests have been jeopardized,” thus 16 satisfying both statutory and constitutional standing. Id. at 13 (footnote omitted). Plaintiff 17 alternatively contends that, “[i]f the Court has any doubts about whether Plaintiff was 18 injured, this action must be remanded to California Superior Court.” Id. at 2. In its Reply, 19 Defendant claims not to challenge Plaintiff’s Article III standing, but contends that 20 “Plaintiff has failed to allege any specific violation of the ALPR law tied to the alleged 21 harm, which is purely a statutory question and properly decided by this Court under Rule 22 12(b)(6) standards.” Reply at 6–7 n.5 (citing Maya v. Centex Corp., 658 F.3d 1060, 1067 23 (9th Cir. 2011)). 24 1. Standing 25 As an initial matter, regardless of whether Defendant raised the issue, “[f]ederal 26 district courts are courts of limited jurisdiction that ‘may not grant relief absent a 27 constitutional or valid statutory grant of jurisdiction’ and are ‘presumed to 28 lack jurisdiction in a particular case unless the contrary affirmatively appears.’” Cooper v. 1 Tokyo Elec. Power Co., 990 F. Supp. 2d 1035, 1038 (S.D. Cal. 2013) (quoting A-Z Int’l v. 2 Phillips, 323 F.3d 1141, 1145 (9th Cir. 2003)). Thus, “[f]ederal courts are required sua 3 sponte to examine jurisdictional issues such as standing.” Chapman v. Pier 1 Imports 4 (U.S.) Inc., 631 F.3d 939, 954 (9th Cir. 2011) (quoting Bernhardt v. Cty. of Los Angeles, 5 279 F.3d 862, 868 (9th Cir. 2002)) (citing United States v. Hays, 515 U.S. 737, 742 (1995)). 6 “Standing . . . requires a plaintiff to demonstrate the now-familiar elements of injury 7 in fact, causation, and redressability.” Lance v. Coffman, 549 U.S. 437, 439 (2007) (per 8 curiam) (citing Lujan v. Defenders of Wildlife, 504 U.S. 555, 573–74 (1992)). To satisfy 9 the requirements of “injury in fact,” a plaintiff must show that he suffered “an invasion of 10 a legally protected interest which is (a) concrete and particularized, and (b) actual or 11 imminent, not conjectural or hypothetical.” Lujan, 504 U.S. at 560 (internal quotation 12 marks and citations omitted). In other words, the injury must be “concrete in both a 13 qualitative and temporal sense” such that a plaintiff “must allege an injury to himself that 14 is distinct and palpable.” Whitmore v. Arkansas, 495 U.S. 149, 155 (1990) (internal 15 quotation marks and citations omitted). “A plaintiff does not necessarily meet the concrete 16 injury requirement ‘whenever a statute grants a person a statutory right and purports to 17 authorize that person to sue to vindicate that right.’” Patel v. Facebook, Inc., 932 F.3d 18 1264, 1270 (9th Cir. 2019) (quoting Spokeo, Inc. v. Robins, 578 U.S. 330, 341 (2016), as 19 revised (May 24, 2016)). In assessing “whether the violation of a statute causes a concrete 20 injury,” courts within the Ninth Circuit “ask ‘(1) whether the statutory provisions at issue 21 were established to protect [the plaintiff’s] concrete interests (as opposed to purely 22 procedural rights), and if so, (2) whether the specific procedural violations alleged in this 23 case actually harm, or present a material risk of harm to, such interests.’” Id. at 1270–71 24 (quoting Robins v. Spokeo, Inc., 867 F.3d 1108, 1113 (9th Cir. 2017)). 25 Even assuming that “‘the statutory provisions at issue’ in [the ALPR statute] were 26 established to protect an individual’s ‘concrete interests’ in privacy, not merely procedural 27 rights,” the Court finds that the Complaint, as presently pleaded, fails to adequately 28 establish that “the specific procedural violations alleged in this case actually harm, or 1 present a material risk of harm to, such interests.” Id. at 1274 (citation omitted). Accepting 2 the factual allegations of the Complaint as true, Plaintiff alleges that “[he] is one of millions 3 of individuals who has fallen victim to DRN’s pervasive surveillance network. DRN 4 tracked [Plaintiff]’s vehicle, thus gaining access to his home and work address and other 5 sensitive information.” Compl. ¶ 8. Plaintiff “is concerned to whom and for what reasons 6 [Defendant] may have disclosed [Plaintiff’s] sensitive license plate data together with his 7 vehicle’s location. Worst of all, [Plaintiff] is concerned how this information can be 8 misused.” Id. ¶ 41. 9 As the allegations of the Complaint make clear, however, the purported harm to 10 Plaintiff’s privacy interests relies heavily on speculation; thus, any harm appears not to be 11 “actual or imminent,” but rather “conjectural or hypothetical.” Lujan, 504 U.S. at 560. For 12 example, Plaintiff pleads that DRN’s collection of his data “allowed DRN to identify” 13 aspects of Plaintiff’s personal life—such as the identity his former employer, where he 14 spends his time after work, and the school “his family member attended”—but Plaintiff 15 does not plead that Defendant actually used the data it collected to identify said information 16 about Plaintiff. Compl. ¶ 38 (emphasis added). Further, Plaintiff alleges he “is concerned” 17 about to whom, and for what reasons, Defendant “may have disclosed” Plaintiff’s license 18 plate information, but Plaintiff does not plead that Defendant actually disclosed his data to 19 anyone at all. Id. ¶ 40 (emphasis added). In the same vein, Plaintiff claims that he “is 20 concerned [about] how this information can be misused,” but he does not plead that the 21 information in fact was misused. Id. (emphasis added). Thus, although Plaintiff has listed 22 various possibilities as to how Defendant’s data theoretically could be misused, Plaintiff 23 fails to allege that any of these eventualities have occurred or are likely to occur. 24 Thus, as presently pleaded, the Court finds that Plaintiff has not adequately alleged 25 standing and thus DISMISSES Plaintiff’s Complaint. Nonetheless, because the Court 26 finds that Plaintiff could allege facts in an amended complaint to establish standing and 27 solidify this Court’s jurisdiction, the Court finds that remand is not required at this time. 28 See Maya, 658 F.3d at 1060. 1 The Court now turns to Defendant’s arguments. 2 2. The Notice Requirement 3 Plaintiff alleges that “Defendant’s conduct violates the Notice Requirement under 4 Cal. Civ. Code §§ 1798.90.51(b)(1) & [1798.90.]53(b)(1) because the company does not 5 make a meaningful usage and/or privacy policy available to the public, nor does it 6 conspicuously post any information about usage and/or privacy on its website.” Compl. 7 ¶ 56. 8 Defendant argues that the ALPR statute does not contain a provision requiring it “to 9 individually provide notice to or obtain consent from anyone before photographing vehicle 10 license plates in public spaces. Indeed, the terms ‘notice’ and ‘consent’ appear nowhere in 11 the ALPR statute.” Mot. at 5. While that is true, the argument misses the mark. Plaintiff’s 12 claim is that, “even if one somehow becomes aware of the collection [of one’s ALPR 13 information], the company responsible for doing it and the address of its website, DRN 14 takes pains to hide its policy, burying it in small dark font against a dark background at the 15 very bottom of its website.” Opp’n at 9 (citing Compl. ¶¶ 36, 56). Thus, “DRN’s hollow 16 disclosures fail to comport with the statute’s notice requirements,” given that the Website 17 posting is not “conspicuous.” Id. at 15. 18 Having found the Website to be incorporated by reference into the Complaint, the 19 Court finds, subject to the standing deficiency noted supra, that the Complaint plausibly 20 alleges a claim for violation of the Notice Requirement. Although Defendant has a link to 21 its “California ALPR Policy” on its homepage, the link appears in small words at the very 22 bottom of its website. One must scroll all the way to the bottom, and accept a pop-up 23 notification about cookies, to even see the link. One plausibly could infer that this is not 24 “posted conspicuously” as required by the ALPR statute. See Cal. Civ. Code 25 §§ 1798.90.51(b)(1) & 1798.90.53(b)(1). Accordingly, the Court DENIES Defendant’s 26 Motion on this ground. 27 / / / 28 / / / 1 3. The Privacy, Security, and Proper Use Requirements 2 Plaintiff acknowledges that Defendant maintains a privacy policy on its Website but 3 claims that it only does so to “maintain the appearance of adhering to the law.” Compl. 4 ¶ 30. Ultimately, Defendant violates the Privacy Requirement, according to Plaintiff, 5 because its policy is “illusory,” see Opp’n at 15–16, as it does not “ensure that [DRN’s] 6 collection, use, maintenance, sharing, and dissemination of ALPR information is consistent 7 with respect for individuals’ privacy and civil liberties,” Compl. ¶ 57. Plaintiff alleges that 8 Defendant violates the Security Requirement “because it expressly disclaims the highly 9 sensitive nature and serious privacy implications of its ALPR data, and as a result fails to 10 conduct the security procedures and practices reasonably necessary to protect such 11 sensitive information from unauthorized access, destruction, use, modification, or 12 disclosure.” Id. ¶ 58. Finally, Plaintiff pleads that ALPR operators must “require that 13 ALPR information only be used for the authorized purposes described in the usage and 14 privacy policy,” but Defendant violates this Proper Use Requirement by “allow[ing], and 15 indeed encourag[ing] its customers to use its ALPR system for the unauthorized purpose 16 of tracking and locating individuals.” Id. ¶¶ 15, 59 (citing Cal. Civ. Code § 1798.90.52(b)). 17 Defendant argues that Plaintiff fails to allege an actionable violation of the ALPR 18 statute because he does not plausibly allege: (1) “that DRN actually failed to maintain 19 reasonable security procedures and practices,” (2) “that the usage and privacy policy does 20 not disclose the information required by the statute,” (3) that “any unauthorized access to 21 DRN’s ALPR data has ever occurred,” or (4) “that DRN fails to limit access to its ALPR 22 data to the ‘authorized purposes’ described in its usage and privacy policy.” Mot. at 6. 23 Further, Defendant argues that the ALPR statute does not mandate that its security 24 procedures be set forth in its published usage and privacy policy. Reply at 6. 25 In response, Plaintiff argues that he “need not prove a specific breach of ALPR’s 26 [sic] system” because “it is a reasonable inference to draw from the fact that DRN uses 27 ambiguous language to describe how its system will be monitored for security purposes, 28 appears to have no concrete security procedures beyond ‘periodically audit[ing]’ usage 1 logs, and disclaims the security needs of that information altogether.” Opp’n at 16 (citing 2 Compl. ¶¶ 35, 58). Plaintiff points to the marketed possible uses of Defendant’s system 3 for mailing campaigns and debt collection purposes as improper uses of ALPR data, 4 according to Defendant’s policy, to track individuals rather than vehicles. Compl. ¶¶ 31– 5 33; see also Opp’n at 16. 6 The Court finds that the Complaint at present fails to adequately plead any violation 7 of the ALPR statute’s Privacy, Security, or Proper Use Requirements. Plaintiff concedes 8 that the privacy policy on Defendant’s Website “appears to track the topics outlined by the 9 ALPR law.” Opp’n at 7. To the extent Plaintiff argues that Defendant does not properly 10 implement its own usage and privacy policy or that said policy is “illusory,” Plaintiff relies 11 on hypotheticals about what could happen if the data fell into the wrong hands and how 12 this would infringe on his privacy and civil liberties, see Compl. ¶¶ 24–25, but Plaintiff 13 fails to allege any facts tending to show that Defendant indeed did violate its policy, and 14 therefore the ALPR statute. Similarly, Plaintiff offers no facts to support his bald assertion 15 that Defendant has not implemented reasonable security procedures and practices 16 necessary to protect its ALPR data. Id. ¶ 58. Rather, by outlining the content of the usage 17 logs Defendant keeps in the “Monitoring and Compliance” section of its usage and privacy 18 policy, Defendant appears to facially comply with the requirement that it provide “a 19 description of how the ALPR system will be monitored to ensure the security of the 20 information accessed or used, and compliance with all applicable privacy laws, and a 21 process for periodic system audits.” See Cal. Civ. Code §§ 1798.90.51(b)(2)(c) & 22 1798.90.53(b)(2)(c); see also Website at 2. Finally, the allegedly unauthorized uses of 23 ALPR information facially appear to fall within the permissible uses outlined in 24 Defendant’s policy. Defendant makes clear that possible users and uses of the system and 25 data include “[f]inancial services companies and other businesses that have a legitimate 26 commercial interest in locating or identifying a vehicle.” Website at 2. As Defendant 27 argues in its Reply, that the location of a vehicle can be used to validate other data about a 28 person, such as his address or possible location, does not necessarily mean that the ALPR 1 data is being accessed and used in contravention of Defendant’s policy. Accordingly, the 2 threadbare allegations of the Complaint and the unfounded inferences Plaintiff invites the 3 Court to draw, see Opp’n at 16, are inadequate to state a claim. 4 Because Plaintiff has failed to allege specific and plausible facts to support his broad 5 and unsubstantiated claim that Defendant has violated the Privacy, Security or Proper Use 6 Requirements of the ALPR statute, the Court finds that Plaintiff fails to plead a violation 7 of those requirements and GRANTS Defendant’s Motion on these grounds. 8 B. Punitive Damages Request 9 Plaintiff requests “an award of liquidated damages, punitive damages, costs, and 10 attorneys’ fees” for Defendant’s alleged violations of the ALPR Statute. Compl. at 15 11 (“Prayer”). Defendant argues that Plaintiff’s request for punitive damages should be 12 stricken and/or dismissed because Plaintiff has failed to plead “any facts that would 13 establish entitlement to punitive damages.” Mot. at 7. Specifically, Defendant contends 14 that punitive damages are available “only upon clear and convincing evidence that 15 defendant’s conduct is ‘so vile, base, contemptible, miserable, wretched or loathsome that 16 it would be looked down upon or despised by ordinary decent people’ or ‘[having] the 17 character of outrage frequently associated with crime.’” Mot. at 7 (citing Tomaselli v. 18 Transamerica Ins. Co., 25 Cal. App. 4th 1269, 1287 (1994)). Plaintiff counters that, under 19 the ALPR statute, punitive damages may be awarded upon a lesser showing: “proof of 20 willful or reckless disregard of the law.” Opp’n at 16–17 (citing Cal. Civ. Code 21 § 1798.90.54(b)(2)). Plaintiff argues that Defendant “violated the law despite knowing or 22 perceiving the risk that its conduct would violate the statute” by “expressly disclaim[ing] 23 the highly sensitive nature and serious privacy implications of [Defendant’s] ALPR data” 24 while “impersonating compliance as a way to ‘pay lip service to privacy laws.’” Id. at 17 25 (citing Compl. ¶¶ 34, 55, 58). In its Reply, Defendant maintains that Plaintiff “failed to 26 allege any meaningful violation of the ALPR law at all, much less a willful or reckless 27 violation of the statute,” and accordingly urges the Court to strike Plaintiff’s punitive 28 damages claim. Reply at 7 (emphasis in original). 1 A growing number of district courts have concluded that Rule 12(b)(6) is generally 2 ||inapplicable to damage prayers. See, e.g., Sturm v. Rasmussen, Case No.: 18-CV-01689- 3 || W-BLM, 2019 WL 626167, at *3 (S.D. Cal. Feb. 14, 2019) (collecting cases). Nor does 4 ||the Court find that Defendant establishes that Plaintiff's prayer for punitive damages is 5 || “redundant, immaterial, impertinent, or scandalous matter” properly stricken under Rule 6 || 12(f). Fed. R. Civ. P. 12(f). Rather, Plaintiff’s request for punitive damages goes directly 7 || to the relief to which Plaintiff may be entitled, assuming he can establish standing and a 8 || violation of the ALPR statute. Accordingly, striking Plaintiff's claim for punitive damages 9 || would be improper at this stage and the Court DENIES Defendant’s request. 10 CONCLUSION 1] In light of the foregoing, the Court GRANTS IN PART AND DENIES IN PART 12 || Defendant’s Motion to Dismiss (ECF No. 4) and DISMISSES Plaintiff's Complaint for 13 || lack of standing. Because the Court finds it is possible Plaintiff could amend his Complaint 14 cure the deficiencies noted herein, however, said dismissal is WITHOUT 15 || PREJUDICE. Plaintiff MAY FILE an amended complaint within thirty (30) days of the 16 |/date on which this Order is electronically docketed. Should Plaintiff elect to file an 17 ||amended complaint, it must cure the deficiencies noted herein and must be complete in 18 itself without reference to Plaintiffs prior Complaint. See S.D. Cal. CivLR 15.1. Should 19 || Plaintiff fail to file an amended complaint within thirty (30) days of the date on which this 20 || Order is electronically docketed, the Court will enter a final order dismissing this civil 21 || action based on Plaintiff's failure to prosecute in compliance with a court order requiring 22 ||amendment. See Lira v. Herrera, 427 F.3d 1164, 1169 (9th Cir. 2005) (“If a plaintiff does 23 ||not take advantage of the opportunity to fix his complaint, a district court may convert the 24 || dismissal of the complaint into dismissal of the entire action.’’). 25 IT IS SO ORDERED. 26 || Dated: March 25, 2022 . tt 27 pon Janis L. Sammartino 28 United States District Judge