Corner Computing Solutions v. Google LLC

[8] UNITED STATES DISTRICT COURT WESTERN DISTRICT OF WASHINGTON 9 AT SEATTLE [10] 11 CORNER COMPUTING SOLUTIONS CASE NO. 2:23-cv-00939-TL and DALE JAKE CORNER, 12 ORDER ON MOTION TO DISMISS Plaintiff, 13 v. FIRST AMENDED COMPLAINT 14 GOOGLE LLC, 15 Defendant. [16] 17 This is an action for breach of contract and breach of the covenant of good faith and fair 18 dealing, related to Defendant Google LLC’s allegedly improper response to Plaintiff Dale Jake 19 Corner’s complaints about negative online reviews of Corner Computing Solutions, his business. 20 Dkt. No. 23 at 1–2. This matter is before the Court on Defendant’s Motion to Dismiss First 21 Amended Complaint for Failure to State a Claim. Dkt. No. 25. Having reviewed the governing 22 law and relevant record, and finding oral argument unnecessary, see LCR 7(b)(4), the Court 23 GRANTS Defendant’s motion. [24] 1 I. BACKGROUND 2 A. Procedural History 3 Plaintiff is proceeding pro se (without an attorney). Plaintiff originally filed this action in 4 the Superior Court of the State of Washington for Snohomish County on May 1, 2023. Dkt. No. 5 1 at 1. On June 22, 2023, Defendant removed the case to federal court, based on diversity 6 jurisdiction. Id. at 1–2. On June 29, 2023, Defendant filed a motion to dismiss Plaintiff’s original 7 complaint (Dkt. No. 1-2) for failure to state a claim and insufficient service of process. Dkt. No. 8 10. Plaintiff did not file a response. On February 28, 2024, the Court granted the motion in part, 9 dismissing Plaintiff’s original complaint but allowing Plaintiff to file the First Amended 10 Complaint (“FAC”) as well as providing an opportunity for him to properly serve Defendant 11 with the FAC.1 Dkt. No. 20 at 6, 9. On April 1, 2024, Plaintiff filed the FAC. Dkt. No. 23. 12 Defendant filed the instant motion to dismiss on April 29, 2024. Dkt. No. 25. On May 16, 13 2024, Plaintiff filed a response. Dkt. No. 27. On May 28, 2024, Defendant filed a reply. Dkt. 14 No. 28. 15 B. The First Amended Complaint 16 There are two components to the FAC. First, the FAC alleges breach of contract and 17 breach of the covenant of good faith and fair dealing associated with “spurious” content posted 18 to the online profile of Plaintiff’s business. Dkt. No. 23 at 1–9. Second, the FAC alleges breach 19 of contract and breach of the covenant of good faith and fair dealing when Defendant “for 5 or 20 more months banned [his] Virus Total account without pre notification or communication.” 21 Id. at 9. [23] 1 Plaintiff also filed a motion seeking leave to amend his original complaint. Dkt. No. 21. This motion, while 24 granted, was unnecessary, given the Court’s ruling on the original motion to dismiss. See Dkt. Nos. 19, 22. 1 1. “Spurious” content allegations (FAC Claims 1–3) 2 The “spurious” content allegations comprise claims 1, 2, and 3 in Section 2 of the FAC. 3 Dkt. No. 23 at 1–9. While the FAC is somewhat unclear, these allegations appear to be based on 4 Defendant’s: (1) “refusing to remove spurious ‘Fake Engagement’ and or ‘Misrepresentation’ 5 reviews” and “refus[ing] to remove the ‘Prohibited and Restricted Content’ reviews” on a 6 business account with Defendant; and (2) “bann[ing] [Plaintiff’s] Virus Total account without 7 pre notification or communication” Id. at 1–2; see also id. at 15–50 (exhibits to complaint). More 8 specifically, Plaintiff alleges that Defendant breached its contract with Plaintiff by “outright 9 ignoring communication requests, requests for clarification, as well as ignoring the escalation 10 requests via their own online forms; and specifically not obeying their own policies regarding the 11 contract.” Id. at 2. 12 The FAC identifies the “Google Terms of Service” and the “Google LLC Maps User 13 Generated Content Policy” as the contract(s)2 that Defendant allegedly breached. According to 14 the policy identified by Plaintiff and reproduced as an exhibit to the FAC, “Fake engagement is 15 not allowed and will be removed.” Id. at 16. Among other things, “fake engagement” includes 16 “false or misleading accounts of the description or quality of a good or service” and “content that 17 has been posted by a competitor to undermine a business or product’s reputation.” Id. at 18–19. 18 Plaintiff alleges that his business’s account was beset by “1 Star reviews” that constituted “[f]ake 19 engagement” in violation of the policy. Id. at 3. He does not, however, specify why or how he 20 believes these reviews are, in fact, fake. The FAC identifies 10 such reviews that Defendant 21 allegedly refused to remove, despite having “been notified of the situation via their own forms [23] 2 As will be discussed more comprehensively below, see infra Section III.A., the “Google LLC Maps User Generated Content Policy” is just that—a policy. It is not a legally enforceable contract between Plaintiff and 24 Defendant. 1 and contact procedures and . . . given ample time to fix the issue.” Id. at 4–8, 9. The FAC thus 2 alleges that Defendant “could have fairly removed these . . . reviews via their own policy; dealt 3 fairly and in good faith with [Plaintiff] and has chosen not to.” Id. at 8. 4 2. Virus Total allegations (FAC Claim 4) 5 The Virus Total allegations appear in Claim 4 of the FAC. Dkt. No. 23 at 9. Plaintiff 6 alleges that, “Despite many contacts about the issue[,] [Defendant] refuses to ban the acting 7 spurious ‘Troll’ accounts on ‘Virus Total’ leaving spurious comments; and yet has banned 8 [Plaintiff’s] account instead.” Id. Plaintiff also asserts that Defendant did not “act[ ] in ‘The 9 Covenant Of Good Faith And Fair Dealing,’ resulting in a third breach of contract on those 10 grounds.” Id. at 9–10. In support of his claim, Plaintiff attached as an exhibit to his FAC what 11 appears to be his “user profile” for the service, as well as what the Court construes as excerpts of 12 online conversation(s) between Plaintiff and at least one other third party.3 Id. at 44–50. 13 II. LEGAL STANDARD 14 A defendant may seek dismissal when a plaintiff fails to state a claim upon which relief 15 can be granted. Fed. R. Civ. P. 12(b)(6). In reviewing a Rule 12(b)(6) motion to dismiss, the 16 Court takes all well-pleaded factual allegations as true and considers whether the complaint 17 “state[s] a claim to relief that is plausible on its face.” Ashcroft v. Iqbal, 556 U.S. 662 , 678 18 (2009) (quoting Bell Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007)). While “[t]hreadbare 19 recitals of the elements of a cause of action, supported by mere conclusory statements,” are 20 insufficient, a claim has “facial plausibility” when the party seeking relief “pleads factual content 21 that allows the court to draw the reasonable inference that the defendant is liable for the 22 misconduct alleged.” Iqbal, 556 U.S. at 672 . “When reviewing a dismissal pursuant to [23] 3 Without a primer on Virus Total terminology and functionality, it is difficult for the Court to ascertain the specific 24 nature of the material appended to the FAC as “Exhibit C.” 1 Rule . . . 12(b)(6), ‘we accept as true all facts alleged in the complaint and construe them in the 2 light most favorable to plaintiff[ ], the non-moving party.’” DaVinci Aircraft, Inc. v. United 3 States, 926 F.3d 1117, 1122 (9th Cir. 2019) (alteration in original) (quoting Snyder & Assocs. 4 Acquisitions LLC v. United States, 859 F.3d 1152 , 1156–57 (9th Cir. 2017)). 5 A pro se complaint must be “liberally construed” and held “to less stringent standards 6 than formal pleadings drafted by lawyers.” Florer v. Congregation Pidyon Shevuyim, N.A., 639 7 F.3d 916 , 923 n.4 (9th Cir. 2011) (quoting Erickson v. Pardus, 551 U.S. 89, 94 (2007)). Even so, 8 a court should “not supply essential elements of the claim that were not initially pled.” 9 Henderson v. Anderson, No. C19-789, 2019 WL 3996859 , at *1 (W.D. Wash. Aug. 23, 2019) 10 (quotation marks omitted) (quoting Bruns v. Nat’l Credit Union Admin., 122 F.3d 1251 , 1257 11 (9th Cir. 1997)); see also Khalid v. Microsoft Corp., 409 F. Supp. 3d 1023 , 1031 (W.D. Wash. 12 2019) (“[C]ourts should not have to serve as advocates for pro se litigants.” (quoting Noll v. 13 Carlson, 809 F.2d 1446, 1448 (9th Cir. 1987))). 14 “[I]t is axiomatic that pro se litigants, whatever their ability level, are subject to the same 15 procedural requirements as other litigants.” Muñoz v. United States, 28 F.4th 973 , 978 (9th Cir. 16 2022) (internal citations omitted). Still, “[a] district court should not dismiss a pro se complaint 17 without leave to amend unless ‘it is absolutely clear that the deficiencies of the complaint could 18 not be cured by amendment.’” Akhtar v. Mesa, 698 F.3d 1202, 1212 (9th Cir. 2012) (quoting 19 Schucker v. Rockwood, 846 F.2d 1202 , 1203–04 (9th Cir. 1988)). 20 III. DISCUSSION 21 Defendant argues that Plaintiff has failed to state a claim for relief for two reasons. First, 22 Defendant argues that Defendant is immune from liability under Section 230 of the 23 Communications Decency Act (“Section 230”), 47 U.S.C. § 230 (c)(1). Dkt. No. 25 at 13. Section 24 230 precludes liability “‘when the duty plaintiff alleges the defendant violated derives from the 1 defendant’s status or conduct as a publisher or speaker.’” Dkt. No. 25 at 13 (quoting Barnes v. 2 Yahoo!, Inc., 570 F.3d 1096, 1107 (9th Cir. 2009)). However, Defendant also admits, as it must, 3 that Section 230 is not a complete bar to liability if a provider of interactive services “has a 4 ‘manifest intention to be legally obligated to do something [such as] remov[e] material from 5 publication.’” Id. at 14 (quoting Barnes, 570 F.3d at 1108–09). 6 Second, Defendant argues that Plaintiff has failed to state a claim for either breach of 7 contract or breach of the covenant of good faith and fair dealing. Id. at 16. Plaintiff’s FAC 8 focuses entirely on what is essentially Defendant’s alleged manifest intention to act pursuant to a 9 contract with Plaintiff. Dkt. No. 23 at 1–9; see also Dkt. No. 27 at 1–2 (asserting that “[t]he case 10 is about how [Defendant] has a contractual obligation to adhere to its promises made in the 11 ‘Terms of Service’ . . . and has not done so”). Therefore, the Court limits its analysis herein to 12 Defendant’s contract law–based contention that Plaintiff has failed to adequately allege the 13 elements of a breach-of-contract claim. Dkt. No. 25 at 16. As will be discussed below, the Court 14 agrees with Defendant and finds that Plaintiff has failed to allege the elements of his contract 15 claims, in both the “spurious” content allegations—i.e., FAC claims 1, 2, and 3—and the “Virus 16 Total” allegations—i.e., FAC claim 4. 17 A. “Spurious” Content Allegations 18 With respect to Plaintiff’s allegations regarding Defendant’s nonremoval of the 19 “spurious” content, the FAC does not demonstrate a contractual obligation that required Google 20 to remove the one-star reviews. Consequently, Plaintiff has not sufficiently pleaded a breach 21 claim on those allegations. [24] 1 1. Initial Matters 2 a. Choice of Law 3 Defendant’s motion raises in a footnote that its “Terms of Service, which Plaintiff refers 4 to as the operative contract between the Parties, includes a California choice of law provision.” 5 Dkt. No. 25 at 17 n.6. While Defendant did not brief this potential choice-of-law issue, it cites 6 both California and Washington law in its motion to dismiss (Dkt. No. 25 at 17, 18). Likewise, 7 Plaintiff did not identify which law he believes should govern this action in either the FAC or his 8 response to Defendant’s motion to dismiss. See generally Dkt. Nos. 23, 27. However, the 9 elements of a breach-of-contract claim are essentially the same for both states: (1) existence of a 10 contract; (2) breach of that contract; and (3) damages. Compare Wall St. Network, Ltd. v. N.Y. 11 Times Co., 80 Cal. Rptr. 3d 6, 12 (Cal. Ct. App. 2008), with Univ. of Wash. v. Gov’t Emps. Ins. 12 Co., 200 Wn. App. 455 , 467, 404 P.3d 559 (2017). With respect to the covenant of good faith 13 and fair dealing, under Washington law, “If there is no contractual duty, there is nothing that 14 must be performed in good faith.” In re Amazon Serv. Fee Litig., 705 F. Supp. 3d 1255 , 1269 15 (W.D. Wash. 2023) (quoting U.S. Bank Nat’l Ass’n v. Tait, No. C16-767, 2016 WL 5141990 , at 16 *7 (W.D. Wash. Sept. 21, 2016) (internal quotation marks removed)). The same is true under 17 California law. See, e.g., Griffin v. Allstate Ins. Co., 920 F. Supp. 127, 130 (C.D. Cal. 1996) 18 (“[The covenant of good faith and fair dealing] does not have an existence independent of its 19 contractual underpinnings.”) (citing Waller v. Truck Ins. Exch., Inc., 900 P.2d 619 , 638–39 (Cal. 20 1995)). Therefore, where Plaintiff does not sufficiently allege a breach-of-contract claim, he 21 necessarily cannot allege a breach of the covenant of good faith and fair dealing. 22 b. Terms of Service 23 Although Plaintiff references Defendant’s Terms of Service in his FAC, he does not 24 provide a clear recitation of which specific provisions in this contract were allegedly breached, 1 or identify which version of the Terms of Service is at issue in this case. See Dkt. No. 23 at 2. 2 For its part, Defendant includes in its motion a link to a version of the Terms of Service effective 3 May 22, 2024. Dkt. No. 25 at 17. In his response, Plaintiff attaches as an exhibit a version of the 4 Terms of Service effective January 5, 2022. Dkt. No. 27 at 7–10. 5 On a motion to dismiss, a court may “consider certain materials—documents attached to 6 the complaint, documents incorporated by reference in the complaint, or matters of judicial 7 notice—without converting the motion to dismiss into a motion for summary judgment.” United 8 States v. Ritchie, 342 F.3d 903, 907 (9th Cir. 2003). Under incorporation by reference, a court 9 may “consider documents in situations where the complaint necessarily relies upon a document 10 or the contents of the document are alleged in a complaint, the document’s authenticity is not in 11 question and there are no disputed issues as to the document’s relevance.” Coto Settlement v. 12 Eisenberg, 593 F.3d 1031, 1038 (9th Cir. 2010). A document may be incorporated by reference 13 “if the plaintiff refers extensively to the document or the document forms the basis of the 14 plaintiff’s claim.” Ritchie, 342 F.3d at 908 . Here, Defendant’s Terms of Service form the basis of 15 Plaintiff’s claim. Dkt. No. 23 at 2. Therefore, the Court will consider them on the instant motion. 16 As Plaintiff does not provide any dates associated with the posting of the “spurious” 17 content, or with his reporting thereof to Defendant, it is not apparent which version of the Terms 18 of Service represents the controlling contract in this case. Assuming, arguendo, that the 19 complained-of conduct occurred within Washington’s six-year statute of limitations for causes of 20 action sounding in contract law (since Defendant did not raise the statute of limitations in its 21 motion), either the October 25, 2017; March 31, 2020; January 5, 2022; or May 22, 2024, 22 version would contain the operative language. See RCW 4.16.040(1). California’s statute of 23 limitations for contract-based causes of action is four years. Cal. Civ. Proc. Code § 337 (1). 24 Accordingly, the Court takes judicial notice of four versions of Defendant’s Terms of Service— 1 the version effective October 25, 2017; the superseding version effective March 31, 2020; the 2 superseding version effective January 5, 2022; and the superseding (and current) version 3 effective May 22, 2024—and considers them here. However, the Court also notes that the 4 outcome would be the same, regardless of which version controls. 5 2. Existence of a Contractual Obligation 6 Here, Plaintiff has not alleged the existence of a contractual provision that obligated 7 Defendant to remove the so-called “spurious” reviews. The FAC identifies two purported 8 contracts that Defendant allegedly breached: (1) Defendant’s Terms of Service; and (2) what 9 Plaintiff refers to as “Google LLC Maps User Generated Content Policy.” Dkt. No. 23 at 2 10 (internal quotation marks removed); see also Dkt. No. 27 at 2 (identifying “Terms of Service” as 11 “the contract in question” in this matter). 12 a. Defendant’s Terms of Service 13 With respect to Defendant’s Terms of Service, both Plaintiff and Defendant agree that 14 they are parties to a binding contract embodied by Terms of Service. See id.; Dkt. No. 25 at 8. 15 However, no version of the Terms of Service contains any contractual language that would have 16 obligated Defendant to do what Plaintiff alleges it should have done—namely, remove content 17 that allegedly constituted “Prohibited and Restricted Content.” See Dkt. No. 23 at 2. Rather, the 18 Terms of Service unambiguously describe the scope of their purview. In the 2017 Terms of 19 Service, Defendant does not make “any specific promises about [its] services” “other than as 20 expressly set out in these terms or additional terms” [October 25, 2017, version, 21 https://perma.cc/9FTA-H44C]. The latter three versions of the Terms of Service expressly limit 22 Defendant’s liability to, respectively: “losses caused by our breach of these terms or service23 specific additional terms” [March 31, 2020, version, https://perma.cc/H4CD-AA63]; and 24 “breaches of these terms or applicable service-specific additional terms” [January 5, 2022, 1 version, https://perma.cc/C6PY-Q27S; and May 22, 2024, version, https://perma.cc/QTP7-735S]. 2 Put another way, any viable breach claim here would need to be based on language contained 3 within the four corners of the Terms of Service, or on language contained within “service4 specific” terms of service.4 And in short, the claims brought in the FAC are not. 5 b. Prohibited and Restricted Content Policy 6 The FAC asserts that Defendant’s policy on “Prohibited and Restricted Content” is “part 7 of the contractual obligations of both parties.” Dkt. No. 23 at 8. In contrast, Defendant 8 characterizes this document as merely a “voluntary polic[y]” that does not “create a contractual 9 duty for [Defendant] to remove ‘spurious’ reviews.” Dkt. No. 25 at 17. Given the plain language 10 of the Terms of Service, the Court finds that it is Defendant who more accurately describes the 11 scope of the contractual agreement at issue in this case. 12 First, the unambiguous contractual provision limiting Defendant’s liability solely to 13 breaches of the express Terms of Service renders Plaintiff’s position untenable. See supra, 14 Section III.A.2.a. Second, Plaintiff’s own attachments make clear that the “Prohibited and 15 Restricted Content” policy is not part of the Terms of Service. Plaintiff’s attachment to his 16 response shows certain webpages that are clearly labeled under a tab titled “Terms of Service.” 17 Dkt. No. 27 at 7–10. But the material captioned “All Business Profile policies & guidelines,” 18 also attached to Plaintiff’s response—and which includes a link to content titled “Prohibited and 19 restricted content,” that, in turn, contains the statement “Fake engagement is not allowed and will 20 be removed”—is on a webpage labeled “Help Center.” Id. at 11–12. Similarly, the attachment to 21 Plaintiff’s FAC with the fake-engagement language is on a webpage labeled “Local Guides [22] 4 “Service-specific” terms of service refer to terms for individual Google products and services such as YouTube or [23] Google Maps. As discussed above, the FAC identifies “Google LLC Maps User Generated Content Policy” as a purported contract to which Plaintiff and Defendant are parties. Dkt. No. 23 at 2. But the FAC does not identify any 24 of Defendant’s service-specific terms of service as an applicable contract here. 1 Help.” Dkt. No. 23 at 17. As presented here, “Help Center” and “Local Guides Help” are 2 separate and distinct from the Terms of Service. 3 Finally, Plaintiff has not provided any authority stating that a company’s policies or 4 information placed on help pages are necessarily incorporated into its terms of service. And the 5 only caselaw the Court could locate supports a finding that, under both Washington and 6 California law, materials extraneous to a contractual terms of service are not considered part of 7 the contract absent some implicit incorporation. See, e.g., Marchand v. Northrop Grumman 8 Corp., No. C16-6825, 2017 WL 2633132 at *5 (N.D. Cal. June 19, 2017) (holding extraneous 9 document was incorporated into contract under California law only where, inter alia, contract’s 10 reference to that document was “clear and unequivocal”); Rodriguez v. Google LLC, No. C2011 4688, 2021 WL 6621070 , at *4 (N.D. Cal. Aug. 18, 2021) (noting that incorporation under 12 California law “compel[s] the primary document to at least reference the document sought to be 13 incorporated”); Double D Trade Co., LLC v. Lamex Foods, Inc., No. C09-919, 2009 WL 14 4927899, at *5 (W.D. Wash. Dec. 14, 2009) (“For a document to become part of a contract under 15 the incorporation by reference doctrine [under Washington law], the contract must explicitly 16 incorporate the other document.”). Nowhere in the contractual terms of service under 17 examination here are the policies at issue mentioned, let alone implicitly or explicitly 18 incorporated therein. 19 It may be misleading for Defendant to state in a policy that fake engagement will be 20 removed while admitting in its briefing that its policies are merely aspirational. Compare Dkt. 21 No. 27 at 12, with Dkt. No. 25 at 19. But that does not make Defendant’s actions here a breach of 22 contract. And in the absence of any binding contractual language that would have obligated 23 Defendant to remove the “spurious” one-star reviews, the Court finds that Plaintiff has not [24] 1 established the first element of a viable breach claim. Consequently, Plaintiff’s breach of 2 contract claim and breach of covenant of good faith and fair dealing claim must be dismissed. 3 The Court further finds that providing Plaintiff with a second opportunity to amend the 4 “spurious” content claims would be futile. See Mirmehdi v. United States, 689 F.3d 975, 985 (9th 5 Cir. 2012). (“[A] party is not entitled to an opportunity to amend his complaint if any potential 6 amendment would be futile.”). Plaintiff has identified Defendant’s Terms of Service as “the 7 contract in question” in this case (Dkt. No. 27 at 2), and the Court has found nothing in the 8 contractual language therein that would substantiate the “spurious” content–related breach claims 9 in the FAC. Therefore, claims 1, 2, and 3 of the FAC are DISMISSED WITH PREJUDICE. 10 B. “Virus Total” Allegations 11 As to the “Virus Total” allegations, the FAC does not identify any contractual language 12 that, on its face, has anything to do with an entity called Virus Total. The FAC’s recitation of the 13 allegations regarding his Virus Total account is thin and consists of a single paragraph. See Dkt. 14 No. 23 at 9. Plaintiff alleges that “[Defendant] for 5 or more months banned my Virus Total 15 account without pre notification or communication,” but he does not explain what a “Virus Total 16 account” is or, indeed, why (or how) Defendant was obligated not to ban it. See Dkt. No. 23 at 9. 17 The only allegation he makes in regard to any breach of contract is to state in a conclusory 18 fashion that Defendant was “again not acting in ‘The Covenant Of Good Faith And Fair Dealing’ 19 resulting in a third breach of contract on those grounds.” Id. at 9–10. 20 Plaintiff does not identify the contract or contractual provision that Defendant allegedly 21 breached by banning his Virus Total account, and he does not draw any connection between the 22 alleged conduct of the so-called “troll accounts” and Defendant’s action of banning his account. 23 Moreover, Defendant’s Terms of Service, discussed at length above, do not include the term 24 “Virus Total” (or link to a “service-specific” terms of service for Virus Total). Given that 1 Plaintiff has not identified any further contract that might or might not control Defendant’s 2 obligations to him with respect to his Virus Total account, the Court finds that Plaintiff has not 3 established the existence of a contract between Defendant and himself in this regard. Having 4 failed to establish the first element of a breach claim, then, Plaintiff’s “Virus Total” claim must 5 be dismissed. 6 Defendant urges the Court to dismiss these claims with prejudice. Dkt. No. 28 at 11. The 7 Court agrees. “The district court’s discretion to deny leave to amend is particularly broad where 8 plaintiff has previously amended the complaint.” Cafasso, U.S. ex rel. v. Gen. Dynamics C4 Sys., 9 Inc., 637 F.3d 1047, 1058 (9th Cir. 2011) (citation omitted). “When a pro se party fails to cure 10 deficiencies that the court has previously identified, the court may order dismissal without leave 11 to amend.” DiMaio v. Cnty. of Snohomish, No. C17-128, 2017 WL 5973067 , at *7 (W.D. Wash. 12 Dec. 1, 2017). The Court notes that the FAC represents Plaintiff’s second attempt to sufficiently 13 plead a breach-of-contract claim on the “Virus Total” allegations. Compare Dkt. No. 23 at 9, 14 with Dkt. No. 1-2 at 2. In its prior motion to dismiss, Defendant specifically pointed out that 15 “Plaintiff does not allege what specific contract it contends applies to its use of Virus Total, 16 whether such contract imposes any obligations on Google, and if so, what those obligations are.” 17 Dkt. No. 10 at 16. And the Court’s Order (Dkt. No. 20) on Defendant’s first motion to dismiss 18 (Dkt. No. 10) granted Plaintiff leave to re-file his complaint, noting that Plaintiff would need to 19 “identify the contractual provisions that were allegedly breached.” Dkt. No. 20 at 7. While the 20 FAC attempted to do just that for the “spurious” content claims, it did not for the “Virus Total” 21 claims. See Dkt. No. 23 at 1–8, 9. Accordingly, the Court finds it appropriate to DISMISS WITH 22 PREJUDICE Claim 4 of the FAC. 23 // 24 // ] IV. CONCLUSION 2 Accordingly, Defendant’s motion to dismiss (Dkt. No. 25) is GRANTED, and Plaintiff's 3 || First Amended Complaint (Dkt. No. 23) is DISMISSED WITH PREJUDICE. 4 Dated this 25th day of September 2024. 6 Tana Lin , United States District Judge [10] 1]