X Corp v. Center for Countering Digital Hate, Inc.

CourtDistrict Court, N.D. California
DecidedMarch 25, 2024
Docket3:23-cv-03836
StatusUnknown

This text of X Corp v. Center for Countering Digital Hate, Inc. (X Corp v. Center for Countering Digital Hate, Inc.) is published on Counsel Stack Legal Research, covering District Court, N.D. California primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
X Corp v. Center for Countering Digital Hate, Inc., (N.D. Cal. 2024).

Opinion

1 2 3 4 5 IN THE UNITED STATES DISTRICT COURT 6 FOR THE NORTHERN DISTRICT OF CALIFORNIA 7 8 X CORP., Case No. 23-cv-03836-CRB

9 Plaintiff,

ORDER GRANTING ECF MOTION 10 v. TO DISMISS

11 CENTER FOR COUNTERING DIGITAL HATE LTD. & STICHTING 12 EUROPEAN CLIMATE FOUNDATION, 13 Defendant. 14 Plaintiff X Corp., the social media company formerly known as Twitter, has sued 15 Defendants Center for Countering Digital Hate, Inc. (“CCDH U.S.”), Center for 16 Countering Digital Hate Ltd. (“CCDH U.K.”) (together, “CCDH”), Stichting European 17 Climate Foundation (“ECF”), and Does (collectively, “Defendants”) in connection with 18 CCDH’s actions “to improperly gain access to protected X Corp. data,” and then use that 19 data in publications critical of X Corp. FAC (dkt. 10) ¶ 1. Both CCDH and ECF have 20 filed motions—CCDH moves to dismiss pursuant to Rule 12(b)(6) of the Federal Rules of 21 Civil Procedure and moves to strike pursuant to California’s anti-SLAPP statute, 22 California Civil Procedure Code § 425.16, see MTD&S (dkt. 47), and ECF moves to 23 dismiss pursuant to Rules 12(b)(2) and 12(b)(6) of the Federal Rules of Civil Procedure, 24 see Mot. (dkt. 49). The Court addresses CCDH’s motion in a separate order. This order 25 pertains to ECF’s motion only. For the reasons described below, the Court GRANTS 26 ECF’s motion to dismiss on both grounds. 27 I. BACKGROUND 1 The Court includes a lengthier background section in its order adjudicating CCDH’s 2 motion and will not repeat it here. The most relevant facts1 pertaining to this motion are as 3 follows. 4 A. Parties 5 X Corp. is a corporation organized under the laws of the State of Nevada, with a 6 principal place of business in San Francisco, California. FAC ¶ 7. X Corp. provides a 7 real-time social media platform (“the X platform”) to its users, who can share ideas 8 through public posts. Id. 9 CCDH U.S. is a non-profit corporation organized under the laws of Washington, 10 D.C., with its principal place of business there as well. Id. ¶ 8. CCDH U.K. is a non-profit 11 organization formed under English law and headquartered in London, England. Id. ¶ 9. 12 CCDH U.S. and CCDH U.K. are affiliated corporate entities. Id. CCDH prepares and 13 publishes reports and articles about organizations and individuals who post on social media 14 platforms “on widely debated topics, included COVID-19 vaccinations, reproductive 15 healthcare, and climate change.” Id. ¶ 17. It then makes those reports “publicly available 16 and free.” Id. X Corp. alleges that CCDH’s reports use “flawed methodologies to advance 17 incorrect, misleading narratives,” cherry-picking data and labeling as “hate speech” 18 content that does not conform to its views. Id. ¶ 18. X Corp. maintains that “CCDH’s 19 reports and articles, coupled with its demands to entirely remove certain users from 20 platforms, are transparent efforts to censor viewpoints that CCDH disagrees with, and 21 reveal CCDH’s goal of leaving on the platforms only viewpoints that CCDH supports.” 22 Id. ¶ 20. Indeed, X Corp. alleges that CCDH is an “activist organization[] masquerading 23 as [a] research agenc[y].” Id. ¶ 1. 24 ECF is a non-profit foundation formed under Dutch law and headquartered in The 25 Hague, Netherlands. Id. ¶ 10. 26

27 1 For the purposes of this motion, the Court accepts as true the allegations from the B. CCDH Improperly Accessing Data from Brandwatch 1 The dispute between X Corp. and ECF is based on help that ECF provided to 2 CCDH in order to access X Corp. data held by a company called Brandwatch. 3 Brandwatch, “a trusted partner of X,” and notably not a defendant in this case, “provides 4 SaaS products2 that enable its customers to conduct brand monitoring on social media, 5 customer research on opinions and trends, campaign planning and campaign effectiveness 6 measurement, competitive analysis and risk management, influencer identification and 7 market research, and audience segmentation and analysis.” Id. ¶ 28. Brandwatch had 8 contracts with X Corp. and with ECF, both of which are relevant here. Id. ¶¶ 29, 35. 9 X Corp. entered into a contract with Brandwatch on May 1, 2020, called the 10 “Master License Agreement” (“the MLA”). Id. ¶ 29. Pursuant to the MLA, Brandwatch 11 could access certain data regarding X Corp., referred to as “‘Licensed Materials,’” which 12 included posts on the X platform, in order “to enable Brandwatch’s customers to use its 13 SaaS products to analyze posts and X/Twitter users.” Id. X Corp. would stream its 14 Licensed Materials from its servers, “including in California,” to “servers used by 15 Brandwatch [] located in the United States, which Brandwatch’s applications accessed to 16 enable [its] users with login credentials to analyze the data.” Id. Brandwatch agreed that it 17 would “‘not attempt to (and will not allow others to): . . . copy, sell, lease, sublicense, 18 distribute, redistribute, syndicate, create derivative works or assign or otherwise transfer or 19 provide access to, in whole or in part, the Licensed Material to any third party.’” Id. ¶ 31. 20 Brandwatch further agreed to keep “Twitter Content” secure. Id. 21 ECF was a subscriber to Brandwatch’s applications, and therefore also had a 22 contract with Brandwatch. Id. ¶ 35. X Corp. alleges that Brandwatch’s terms of service 23 (“Brandwatch ToS”), to which ECF must have agreed, must be similar to the ones publicly 24 available at https://www.brandwatch.com/legal/terms-and-conditions/. Id. Brandwatch 25 provided ECF with login credentials, which enabled ECF to log into Brandwatch’s 26

27 2 SaaS means “software as a service.” See What is SaaS Business Intelligence?, 1 applications to access the Licensed Materials. Id. ¶ 36. X alleges that ECF’s agreement 2 with Brandwatch prevented ECF from selling, reselling, licensing, sublicensing, or 3 otherwise making the Brandwatch service “available to anybody other than its Users” and 4 from distributing “Supplier Data to any non-User for any reason other than Customer’s (or 5 User’s) business purpose.” Id. ¶ 37. ECF further agreed “that it would ensure that its user 6 ID and password to use the Brandwatch applications were kept confidential” and that it 7 would “‘not share Customer Data with any other customer or third parties.’” Id.3 8 CCDH has never been a Brandwatch customer. Id. ¶ 39. X Corp. alleges that ECF 9 knew that CCDH was not authorized to access the Licensed Materials (or Brandwatch), 10 and knew that CCDH wanted to access those materials “to prepare its purported ‘research’ 11 reports and call for censorship and attacks on X Corp.” Id. ¶ 38. X Corp. alleges that “on 12 several occasions since at least early 2021,” ECF agreed to share its Brandwatch login 13 credentials with CCDH “to enable CCDH’s illegal access to the X Corp. data.” Id. CCDH 14 U.K. allegedly instructed CCDH U.S. to secure ECF’s login credentials and helped CCDH 15 U.S. determine how to use Brandwatch applications to search the X Corp. data and “how 16 to mischaracterize that data in the CCDH reports.” Id. CCDH then allegedly “accessed 17 the Licensed Materials improperly and without authorization.” Id. ¶ 41. 18 X Corp. further alleges that CCDH knew as of March 2021 that X Corp. and 19 Brandwatch are parties to agreements that “prohibit Brandwatch from allowing third 20 parties to, among other things, access, distribute, create derivative works from, or 21 otherwise transfer the Licensed Materials.” Id. ¶ 42. X Corp. also alleges that “CCDH 22 knew that . . . ECF’s agreement with Brandwatch prohibited ECF from, among other 23 things, sharing its login credentials [or] any of the Licensed Materials with CCDH.” Id. 24 Despite that alleged knowledge, X Corp. alleges, CCDH “induced and conspired with ECF 25 26 3 CCDH has submitted Brandwatch Service Terms dated October 15, 2022, see Kaplan Decl. Ex.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Hanson v. Denckla
357 U.S. 235 (Supreme Court, 1958)
World-Wide Volkswagen Corp. v. Woodson
444 U.S. 286 (Supreme Court, 1980)
Keeton v. Hustler Magazine, Inc.
465 U.S. 770 (Supreme Court, 1984)
Calder v. Jones
465 U.S. 783 (Supreme Court, 1984)
Burger King Corp. v. Rudzewicz
471 U.S. 462 (Supreme Court, 1985)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Brayton Purcell LLP v. Recordon & Recordon
606 F.3d 1124 (Ninth Circuit, 2010)
Goodyear Dunlop Tires Operations, S. A. v. Brown
131 S. Ct. 2846 (Supreme Court, 2011)
CollegeSource, Inc. v. AcademyOne, Inc.
653 F.3d 1066 (Ninth Circuit, 2011)
Mavrix Photo, Inc. v. Brand Technologies, Inc.
647 F.3d 1218 (Ninth Circuit, 2011)
Hans Oetiker v. Jurid Werke, G. M. B. H
556 F.2d 1 (D.C. Circuit, 1977)
United States v. Patrick Innie
7 F.3d 840 (Ninth Circuit, 1993)
Hallett v. Morgan
287 F.3d 1193 (Ninth Circuit, 2002)

Cite This Page — Counsel Stack

Bluebook (online)
X Corp v. Center for Countering Digital Hate, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/x-corp-v-center-for-countering-digital-hate-inc-cand-2024.