`
`UNITED STATES DISTRICT COURT
`FOR THE DISTRICT OF COLUMBIA
`
`
`STATE OF NEW YORK, et al.,
`
` Plaintiffs,
`
`
`
`
`
`v.
`
` Civil Action No. 20-3589 (JEB)
`
`
`FACEBOOK, INC.,
`
`
`Defendant.
`
`
`
`
`
`MEMORANDUM OPINION
`
`As the pillars of our national economy have shifted from the concrete to the virtual, so
`
`too have the targets of government antitrust actions. Where railroads and oil companies were
`
`alleged to be early violators, over the past decades, providers of telecommunications (AT&T)
`
`and computer operating systems (Microsoft) have been the defendants. In the internet age, not
`
`surprisingly, Facebook finds itself in the spotlight, as both federal and state regulators contend,
`
`in two separate actions before this Court, that it is now the one violating the antitrust laws. The
`
`company, they allege, has long had a monopoly in the market for what they call “Personal Social
`
`Networking Services.” And it has allegedly maintained that monopoly, in violation of Section 2
`
`of the Sherman Act, through two different kinds of actions: first, by acquiring firms that it
`
`believed were well positioned to erode its dominance — most notably, Instagram and WhatsApp;
`
`and second, by adopting policies preventing interoperability between Facebook and certain other
`
`apps that it saw as threats, thereby impeding their growth into viable competitors. The State
`
`Plaintiffs in this action further contend that Facebook’s purchases of Instagram and WhatsApp
`
`violated Section 7 of the Clayton Act, which prohibits acquisitions “the effect of [which] may be
`
` 1
`
`
`
`Case 1:20-cv-03589-JEB Document 137 Filed 06/28/21 Page 2 of 67
`
`substantially to lessen competition, or to tend to create a monopoly.” 15 U.S.C. § 18. Both suits
`
`seek equitable remedies for these alleged antitrust violations, including forced “divestiture or
`
`reconstruction of illegally acquired businesses and/or divestiture of Facebook assets or business
`
`lines.” ECF No. 4 (Redacted Compl.) at 75. (The Court cites a version of the States’ Complaint
`
`that has minor redactions to protect confidential business information, and it mentions certain
`
`redacted facts only with the parties’ permission.)
`
`Facebook now separately moves to dismiss both actions. This Opinion resolves its
`
`Motion as to the States’ Complaint, and the Court analyzes the Federal Trade Commission’s
`
`largely parallel claims in its separate Opinion in No. 20-3590. Although the Court does not
`
`agree with all of Defendant’s contentions here, it ultimately concurs with Facebook’s bottom-
`
`line conclusion: none of the States’ claims may go forward. That is so for two main reasons.
`
`First, the States’ Section 2 and Section 7 attacks on Facebook’s acquisitions are barred by
`
`the doctrine of laches, which precludes relief for those who sleep on their rights. Although
`
`Defendant purchased Instagram in 2012 and WhatsApp in 2014, Plaintiffs’ suit — which seeks,
`
`in the main, to have Facebook divest one or both companies — was not filed until December
`
`2020. The Court is aware of no case, and Plaintiffs provide none, where such a long delay in
`
`seeking such a consequential remedy has been countenanced in a case brought by a plaintiff
`
`other than the federal government, against which laches does not apply and to which the federal
`
`antitrust laws grant unique authority as sovereign law enforcer. If laches is to mean anything, it
`
`must apply on these facts, even in a suit brought by states.
`
`Second, the States’ Section 2 challenge to Facebook’s policy of preventing
`
`interoperability with competing apps fails to state a claim under current antitrust law, as there is
`
`nothing unlawful about having such a policy. While it is possible that Facebook’s
`
` 2
`
`
`
`Case 1:20-cv-03589-JEB Document 137 Filed 06/28/21 Page 3 of 67
`
`implementation of that policy as to certain specific competitor apps may have violated Section 2,
`
`the Court does not reach that question because all such revocations of access occurred over five
`
`years before the filing of the Complaint. Such long-past violations cannot furnish a basis for the
`
`injunctive relief that Plaintiffs seek here.
`
`The Court, consequently, will grant Facebook’s Motion and dismiss the case.
`
`
`
`
` 3
`
`
`
`Case 1:20-cv-03589-JEB Document 137 Filed 06/28/21 Page 4 of 67
`
`Table of Contents
`
`I. Background ............................................................................................................................. 5
`
`A. Social Networking .............................................................................................................. 5
`
`B. Facebook Blue .................................................................................................................... 6
`
`C. Alleged Monopoly Maintenance......................................................................................... 7
`
` Acquisitions .................................................................................................................... 8
`
`
`
`Interoperability Permissions ......................................................................................... 11
`
`a. Facebook Platform .................................................................................................... 11
`
`b. Conditioning Access ................................................................................................. 13
`
`D. Procedural History ............................................................................................................ 15
`
`II. Legal Standard ...................................................................................................................... 17
`
`III. Analysis ................................................................................................................................. 17
`
`A. Standing ............................................................................................................................ 18
`
`B. Platform Policies ............................................................................................................... 21
`
` Refusal to Deal .............................................................................................................. 23
`
`a. Legal Framework ...................................................................................................... 23
`
`b. Application ................................................................................................................ 28
`
`i.
`
`Facebook Policies ................................................................................................. 28
`
`ii. Specific Refusals ................................................................................................... 31
`
` Conditional Dealing ...................................................................................................... 35
`
`C. Acquisitions ...................................................................................................................... 40
`
` Legal Framework .......................................................................................................... 40
`
` Application .................................................................................................................... 43
`
` Counterarguments ......................................................................................................... 47
`
`a. Applicability of Laches ............................................................................................. 47
`
`b. Ongoing Violation .................................................................................................... 51
`
`c. Prospective Relief ..................................................................................................... 57
`
`d. Course of Conduct .................................................................................................... 58
`
`e. Procedural Posture .................................................................................................... 65
`
`IV. Conclusion ............................................................................................................................ 67
`
`
`
` 4
`
`
`
`Case 1:20-cv-03589-JEB Document 137 Filed 06/28/21 Page 5 of 67
`
`I.
`
`Background
`
`A. Social Networking
`
`At the dawn of our century, in the much earlier days of the internet, a number of websites
`
`began to offer services that, in hindsight, were precursors to the sort that Facebook provides.
`
`Those websites provided users a platform for creating a unique webpage, personalized with
`
`photos and messages, that could then be used to interact with the pages of other “friends.” See
`
`Redacted Compl., ¶ 58. Interactions were initially limited to email, using services such as
`
`America Online (AOL). Id., ¶¶ 58–59. Eventually, new online services emerged that allowed
`
`users to organize their profiles into a specific network and communicate with that network, such
`
`as Classmates.com and SixDegrees.com. Id., ¶ 59. Friendster and Myspace, both launched in
`
`2002, built further on this trend, offering the first of what came to be known as “social
`
`networking” services. Id., ¶ 60. Although the precise definition of a “Personal Social
`
`Networking Service” (the main market in which Facebook allegedly operates) is disputed, it can
`
`be summarized here as one that enables users to virtually connect with others in their network
`
`and to digitally share their views and experiences by posting about them in a shared, virtual
`
`social space. Id., ¶¶ 1, 28, 70. For example, users might view and interact with a letter-to-the-
`
`editor-style post on politics by a neighbor, pictures from a friend’s recent party, or a birth
`
`announcement for a newborn cousin. Id., ¶¶ 1, 70.
`
`Perhaps because humans are naturally social, this new way of interacting became hugely
`
`popular. In 2006, Myspace, at one point the leading social network, “overtook Google as the
`
`most-visited website in the world.” Id., ¶ 60. By 2008, however, it had been surpassed by a new
`
`competitor: Facebook. Id., ¶ 66. Launched in 2004 by then-undergraduate Mark Zuckerberg
`
`from his Harvard dorm room, “The Facebook,” as it was initially called, was a social-networking
`
` 5
`
`
`
`Case 1:20-cv-03589-JEB Document 137 Filed 06/28/21 Page 6 of 67
`
`service initially limited to Harvard students. Id., ¶ 61. Encouraged by its success on campus,
`
`Zuckerberg and some fellow students expanded the product to other universities, where it proved
`
`similarly popular. Id., ¶¶ 62–63. That growth led Facebook to expand beyond colleges, first to
`
`high schools and then to the larger adult population. Id., ¶¶ 64–66. By 2008, it had 120 million
`
`active users globally. Id., ¶ 66. Three years later, it had 156 million active users in the United
`
`States alone, with each user averaging over seven hours per month. Id. The following details of
`
`Facebook’s conduct are drawn from the States’ Complaint, as the Court must consider its
`
`allegations true at this stage. The allegations are quite similar, though not identical, to those
`
`made by the FTC in the parallel case and recounted in the Court’s companion Opinion.
`
`B. Facebook Blue
`
`Facebook’s “core” social-network product is known as “Facebook Blue.” Id., ¶ 71. This
`
`is what its millions of users think of when they think of “Facebook.” Generally speaking, using
`
`Facebook Blue entails interacting with “user-created content,” — i.e., content created or shared
`
`by one’s Facebook “friends,” id., ¶ 30 — or creating content oneself by posting. That is not all
`
`that users see or do, however. Users, for instance, also encounter “publisher-created content like
`
`news articles . . . and advertisements,” id., “interspers[ed]” in their “news feed.” Id., ¶¶ 30, 49,
`
`54. Such content can come in text, photo, or video form. Id., ¶ 49. In addition, Facebook users
`
`can play games or use other applications built either by Facebook or by third parties. Id., ¶¶ 80,
`
`152, 190. Facebook also offers other services beyond Facebook Blue to its users, such as
`
`Facebook Messenger, a free mobile-messaging and voice-calling service. Id., ¶¶ 71, 159, 209.
`
`Unlike most businesses, Facebook charges users no fee; instead, it makes money by
`
`selling advertising. Id., ¶¶ 2–3. By leveraging the “vast trove of data it has collected on users,
`
`their friends, and their interests,” the company is able to offer advertisers a “highly targeted” set
`
` 6
`
`
`
`Case 1:20-cv-03589-JEB Document 137 Filed 06/28/21 Page 7 of 67
`
`of potential customers distilled from its “massive network of users.” Id., ¶¶ 3, 51. Under this
`
`business model, as the States’ Complaint puts it, “Users do not pay a cash price to use
`
`Facebook”; instead, “they exchange their time, attention, and personal data for access to
`
`Facebook’s services.” Id., ¶¶ 2, 46. That approach has been highly profitable: in 2019, for
`
`instance, advertisers paid Facebook nearly $30 billion. Id., ¶ 48. To be clear, although
`
`Facebook’s data-collection and -use practices have been subject to increasing scrutiny, they are
`
`not the subject of this action.
`
`C. Alleged Monopoly Maintenance
`
`Instead, this suit alleges that Facebook has violated and is violating the antitrust laws, the
`
`focus of which, generally speaking, is to promote and ensure competition. According to
`
`Plaintiffs, Facebook Blue’s meteoric rise was a positive example of what happens when firms
`
`compete to provide the best product to consumers. Because its social-networking service
`
`provided more “innovative features,” “a higher-quality user experience, and better privacy
`
`protections” than anyone else, id., ¶ 73, at least as early as 2011, it had become the dominant
`
`personal social networking service” in this country, giving Facebook “monopoly power” in that
`
`market. Id., ¶¶ 4, 11, 68.
`
`Around that time, however, Facebook allegedly made a fateful pivot: rather than
`
`continuing to focus on providing the best product, it became concerned with protecting its
`
`monopoly by leveraging its dominance to foreclose and forestall the rise of new competitors. Id.,
`
`¶¶ 98–99. In particular, the company’s executives saw a “unique threat[] to Facebook’s
`
`dominance” in the advent of mobile devices — first and foremost, smartphones — capable of
`
`accessing the internet. Id., ¶¶ 100–01. Although Facebook had mobile functionality, it had been
`
`built with websites and desktop or laptop computers in mind. Other firms’ offerings, by contrast,
`
` 7
`
`
`
`Case 1:20-cv-03589-JEB Document 137 Filed 06/28/21 Page 8 of 67
`
`were “built to look and function well on a mobile device in the first instance.” Id., ¶ 100.
`
`Zuckerberg and other Facebook executives fretted over the possibility that other apps might
`
`create attractive mobile-native features and then leverage those features into exponential user
`
`growth, end-running Facebook’s established position. Id., ¶¶ 101–02. Even if such an app was
`
`not already providing social-network-like functionality, once it had a big enough base of users, it
`
`would still pose a potential threat to Facebook Blue. Id. Facebook executives feared fast-
`
`growing mobile-messaging services in particular, nervous that such apps could rather easily
`
`“morph[]” into direct competitors by adding social features. Id., ¶ 103.
`
`What Facebook did in response to these perceived threats is the basis for these antitrust
`
`suits against it. The company allegedly used its monopoly power to eliminate or destroy
`
`competitors in order to maintain its market dominance. Id., ¶ 104. Plaintiffs allege that,
`
`beginning around 2011, “Facebook used two primary tactics to achieve” that result. Id. First, it
`
`reached deep into its very deep pockets to acquire competitors and potential competitors,
`
`preventing their emergence as serious rivals. Id. Second, it adopted and then enforced policies
`
`that blocked rival apps from interconnecting their product with Facebook Blue, thereby both (i)
`
`blunting the growth of apps that had previously depended on that interoperability to attract new
`
`users, and (ii) warning all other developers not to compete with Facebook, lest they lose access
`
`as well. Id.; see also id., ¶¶ 186–87.
`
` Acquisitions
`
`On the acquisitions front, “Facebook acquired dozens of companies” from 2012 to 2020,
`
`and it “pursued many more acquisitions that did not come to fruition.” Id., ¶ 105. Among those
`
`“dozens” were many minor companies; the Complaint briefly mentions Glancee and EyeGroove,
`
`firms Facebook purchased in 2012 and 2016, respectively. Id., ¶ 184. Rather than catalog each
`
` 8
`
`
`
`Case 1:20-cv-03589-JEB Document 137 Filed 06/28/21 Page 9 of 67
`
`acquisition (some of which, presumably, posed no threat to competition), Plaintiffs focus almost
`
`exclusively on several key examples that purportedly illustrate Facebook’s allegedly
`
`anticompetitive approach: its purchases of Instagram (2012) and WhatsApp (2014), and its
`
`ultimately unsuccessful attempts to buy Snapchat (2012–13). Id., ¶¶ 107–80.
`
`Begin with Insta, as those in the know — viz., our children — refer to it. Launched in
`
`late 2010, Instagram was an innovative photo-editing and -sharing app designed for the era of
`
`smartphones with built-in cameras. Id., ¶¶ 107, 109. The company grew explosively, eventually
`
`attracting the attention of Facebook executives who feared that their own photo-sharing features
`
`paled in comparison. Id., ¶¶ 111, 113. That disparity gave Instagram a chance to grow to a large
`
`enough scale to be threatening, making it a “powerful competitive threat to Facebook’s . . .
`
`monopoly.” Id., ¶ 128. Aiming to “neutralize” that competition, and to “integrate” the
`
`“mechanics” of Instagram’s popular photo-sharing features with Facebook Blue in order to
`
`forestall the growth of future Instagrams, id., ¶ 115, Zuckerberg offered to buy the company for
`
`$1 billion in April 2012. Id., ¶ 119. Instagram agreed.
`
`As required by the Hart-Scott-Rodino Act, 15 U.S.C. § 18a, the FTC reviewed the
`
`acquisition prior to closing to assess whether it posed anticompetitive concerns. Whereas most
`
`mergers are cleared quickly, in this instance the review took over four months. During that
`
`scrutiny, the agency took the rare step of “requir[ing] the submission [by the parties] of
`
`additional information or documentary material relevant to the proposed acquisition.” 15 U.S.C.
`
`§ 18a(e)(1)(A). Eventually, however, Facebook and Instagram satisfied the agency’s concerns,
`
`and in August (over four months after the merger was announced), the Commission voted 5–0 to
`
`allow it to proceed without any challenge or conditions. See FTC, FTC Closes Its Investigation
`
`into Facebook’s Proposed Acquisition of Instagram Photo Sharing Program (Aug. 22, 2012),
`
` 9
`
`
`
`Case 1:20-cv-03589-JEB Document 137 Filed 06/28/21 Page 10 of 67
`
`https://bit.ly/3bDa2mp. Although Plaintiffs do not mention that prolonged FTC review in their
`
`Complaint, the Court may take judicial notice of that agency action. See Pharm. Rsch. &
`
`Manufacturers of Am. v. U.S. Dep’t of Health & Hum. Servs., 43 F. Supp. 3d 28, 33 (D.D.C.
`
`2014); Herron v. Fannie Mae, No. 10-943, 2012 WL 13042852, at *1 (D.D.C. Mar. 28, 2012).
`
`Zuckerberg, Plaintiffs allege, had similar designs in offering to buy Snapchat in October
`
`2013. Id., ¶¶ 131, 134. That app also involved photo-sharing, with the twist that images would
`
`usually be sent one-to-one or one-to-small-group, rather than to a user’s entire network, and
`
`would automatically delete after being viewed for only a few seconds. Id., ¶ 130. Impressed by
`
`the app’s engagement and user growth, Facebook offered to purchase it for $4 billion — mainly,
`
`allege Plaintiffs, to “keep[] [it] out of the hands of any firm with the resources to transform [it]
`
`into a major competitive threat.” Id., ¶ 134. Snapchat’s founder, however, steadfastly refused
`
`the overtures. Id., ¶ 135.
`
`Facebook had better luck the next year with WhatsApp. As noted above, the company’s
`
`executives saw mobile-messaging apps like WhatsApp as their “biggest competitive threat,”
`
`even though they did not directly compete with Facebook Blue in the Personal Social
`
`Networking Services market. Id., ¶ 153. The fear instead was that such apps might well
`
`“morph” into competitors in the future; given the ubiquity of text messaging in modern life, a
`
`widely adopted messaging app could leverage its network effects to transition into a highly
`
`competitive “mobile-first social network” by adding functions such as “gaming platforms,
`
`profiles, and news feeds.” Id., ¶¶ 152–53, 160. WhatsApp was the most potent threat, according
`
`to Facebook executives, because it was the “category leader” among mobile messengers, with
`
`over 400 million active users and a superior product. Id., ¶¶ 154–55. Zuckerberg in particular
`
`“believe[d] that WhatsApp had the potential to enter Facebook’s core market and erode its
`
` 10
`
`
`
`Case 1:20-cv-03589-JEB Document 137 Filed 06/28/21 Page 11 of 67
`
`monopoly power,” and he thus resolved to try to buy it to prevent that from happening. Id.,
`
`¶ 161. In February 2014, after negotiating specific terms regarding WhatsApp’s continued
`
`independence, user privacy, and freedom from ads, he succeeded, as the two companies agreed
`
`on a purchase price of around $19 billion. Id., ¶¶ 165–66. That transaction was also subject to
`
`Hart-Scott-Rodino Act pre-merger review, see 15 U.S.C. § 18a, but the FTC, once again, did not
`
`block it.
`
` Interoperability Permissions
`
`a. Facebook Platform
`
`Shortly after expanding beyond colleges and high schools, Facebook developed
`
`Facebook Platform, a set of tools designed to enable developers of other mobile or web apps to
`
`interoperate with Facebook’s site and data. See Redacted Compl., ¶ 80. The goal was to make
`
`Facebook the “platform” for all social interactions on the internet, thereby creating a better, more
`
`engaging product and driving even more users to its site. Id. The first iteration of Facebook
`
`Platform, circa 2007, allowed developers to build what Facebook called “canvas” apps displayed
`
`within the Facebook website itself. Id., ¶ 190. As an example, a user scrolling through
`
`Facebook could come upon a personality-test app, take the test, and then share her results and
`
`invite Facebook friends to take the test as well, all without ever navigating off the Facebook site.
`
`Id. Facebook made these third-party apps available to users “on a level playing field with
`
`applications built by Facebook.” Id., ¶ 189. App developers took advantage, scrambling to
`
`create these canvas apps in order to gain access to its growing network of users. Id., ¶¶ 80, 189–
`
`94. Such apps would make money by allowing users to purchase virtual goods or items within
`
`the app on a “freemium” model or via ad sales.
`
` 11
`
`
`
`Case 1:20-cv-03589-JEB Document 137 Filed 06/28/21 Page 12 of 67
`
`Facebook soon expanded Platform, deploying a suite of tools that expanded its reach off
`
`the Facebook site itself. These tools — called application programming interfaces or APIs —
`
`created mechanisms for sharing data between Facebook and other services. Id., ¶ 80. The States
`
`provide several examples of APIs that Facebook opened to developers. One is the “Find
`
`Friends” API, id., ¶ 190, which enabled freestanding apps to allow Facebook account holders to
`
`find and connect with Facebook friends within that separate app, or to invite Facebook friends to
`
`join that app. Id., ¶¶ 207, 210, 214–15, 217. For instance, when first starting to use an
`
`independent chess app — i.e., an app used separately as opposed to on the Facebook site itself —
`
`a user with a Facebook account could nonetheless search within the app for other Facebook
`
`friends already using it, or invite them to join via Facebook, all without leaving the app. Another
`
`API Facebook created was Facebook Connect, which allowed Facebook users to sign into third-
`
`party websites or apps using their Facebook log-in credentials. Id., ¶ 81.
`
`Facebook went even further in that direction in 2010 when it launched its Open Graph
`
`API. Open Graph allowed third-party apps and websites to essentially integrate pieces of
`
`Facebook within their own service; for instance, apps could install the famous “Like” button,
`
`which, if clicked, would share a user’s “like” on the user’s Facebook profile. Id., ¶ 82. Users
`
`could do this without even navigating away from the third-party service. Id., ¶¶ 191–93. “[A]
`
`user reading an article on ESPN.com,” for instance, “could now like an article on ESPN’s site,
`
`and choose to post a link of the article to the user’s Facebook profile directly from the
`
`ESPN.com website.” Id., ¶ 193. App developers could also host Facebook comment sections,
`
`facilitating further engagement with their content. Id., ¶ 194. This was, unsurprisingly, a
`
`massively popular tool among app developers. By May 2013, over 10 million apps and websites
`
` 12
`
`
`
`Case 1:20-cv-03589-JEB Document 137 Filed 06/28/21 Page 13 of 67
`
`had used the Open Graph API to integrate with Facebook, and Facebook “integrations quickly
`
`became common across the internet.” Id.
`
`According to Plaintiffs, Facebook benefited significantly from its Platform program and
`
`open APIs. The company garnered goodwill and positive media coverage, continued to increase
`
`its growth and user engagement, and earned substantial sums from its requirement that partner
`
`third-party apps share revenues from in-app purchases. Id., ¶¶ 195–96. Third-party app
`
`developers likewise gained, improving the quality of users’ experience by integrating social
`
`functionality and benefiting from Facebook’s sizeable network of highly engaged users. Id.,
`
`¶ 197. Users, too, enjoyed the increased efficiency and convenience. Id., ¶ 198.
`
`b. Conditioning Access
`
`Nonetheless, the States allege, Facebook eventually “turned to Platform as a tool to
`
`monitor, leverage,” and — most crucially here — “harm (via rescinding API access [to]) apps
`
`that Facebook viewed as actual or potential competitive threats.” Id., ¶ 200. In 2011, it
`
`announced a company policy that allegedly “aimed at forbidding ‘competing social platforms,’
`
`and any apps that linked or integrated with competing social platforms, from accessing its APIs.”
`
`Id., ¶ 199. In 2013, Facebook announced an even broader policy of withholding API access from
`
`apps that competed by “replicat[ing] [Facebook’s] core functionality,” even if they were not full
`
`social networks. Id., ¶ 201.
`
`To the extent the States allege that Facebook’s 2011 policy actually prohibited — as
`
`opposed to merely “aim[ed] at” prohibiting, as is the precise wording of the allegation —
`
`freestanding third-party apps from accessing its APIs merely because those apps also “linked to
`
`or integrated with” other social-networking services, the Court does not accept that
`
`characterization because it is inconsistent with the text of the 2011 policy, which the FTC quotes
`
` 13
`
`
`
`Case 1:20-cv-03589-JEB Document 137 Filed 06/28/21 Page 14 of 67
`
`in its simultaneously filed Complaint in the related case. See Vanover v. Hantman, 77 F. Supp.
`
`2d 91, 98 (D.D.C. 1999) (court may consider material outside the pleadings where it is “referred
`
`to in the complaint and is central to plaintiff’s claim”). As set out in the FTC’s Complaint, the
`
`2011 policy covered only “Apps on Facebook” — i.e., the sort of “canvas apps” described above
`
`— rather than freestanding third-party apps or sites such as ESPN.com. See No. 20-3590, ECF
`
`No. 3 (Redacted FTC Compl.), ¶ 139 (quoting 2011 policy as stating that “Apps on Facebook
`
`may not integrate, link to, promote, distribute, or redirect to any app on any other competing
`
`social platform”). The 2011 policy, then, limited what apps hosted and used on Facebook’s own
`
`site could do; it did not purport to restrict freestanding apps and sites from linking to or
`
`integrating with other social networks.
`
`At any rate, armed with its policies, Facebook “began to selectively enforce” them “to cut
`
`off API access to companies Facebook worried might one day threaten its monopoly.” Redacted
`
`Compl., ¶ 202. Plaintiffs allege that in cutting off access, Facebook intended to, and did,
`
`“devastat[e]” the targeted apps by suddenly depriving them of a “critical piece of infrastructure”
`
`on which they had relied for growth and engagement — namely, Facebook’s user data and
`
`network. Id. The Complaint provides seven discrete examples of competitive or potentially
`
`competitive apps that Facebook targeted for API revocation from 2013 to 2015. Each, after
`
`promising early growth, faltered shortly after losing its access. Id., ¶¶ 207–12 (Voxer), 213–14
`
`(Vine), 215–16 (MessageMe), 217–18 (Path), 219–21 (Circle), 222–24 (Tsū), 225–29 (Phhhoto).
`
`Around the same time, Facebook announced yet another new policy, requiring all developers to
`
`seek permission before being granted API access, even if they previously had it. Id., ¶ 203.
`
`Facebook then denied such requests from “apps it classified as competitors or potential
`
`competitors.” Id.
`
` 14
`
`
`
`Case 1:20-cv-03589-JEB Document 137 Filed 06/28/21 Page 15 of 67
`
`According to the States, Facebook’s policies and enforcement decisions helped “ensur[e]
`
`that would-be competitors could not gain or maintain a foothold in the Personal Social
`
`Networking Services market.” Id., ¶ 230. What is more, Plaintiffs allege, Facebook’s actions
`
`deterred other firms (and their venture-capital backers) from even thinking about challenging
`
`Facebook Blue. Id. The effect was to “maintain and enhance Facebook’s monopoly power.”
`
`Id., ¶ 231.
`
`Although the story laid out in the Complaint ends there, the States’ brief in opposition to
`
`the present Motion to Dismiss provides an important coda. According to that brief, and a
`
`Facebook press release the States append as an exhibit to their Opposition, see ECF No. 121-7,
`
`in 2018, Facebook terminated all of its policies regarding competitor API access. See ECF No.
`
`122 (States Opp.) at 13. Facebook does not dispute that contention, see ECF No. 123 (Reply
`
`States) at 24, and the FTC’s Complaint in the parallel action makes the same allegation. See
`
`Redacted FTC Compl., ¶¶ 148–49. The Court accordingly takes judicial notice of the fact that
`
`Facebook retracted its API policies in 2018. See Bowden v. United States, 106 F.3d 433, 437
`
`(D.C. Cir. 1997) (considering “the pleadings and undisputed documents in the record” while
`
`considering motion to dismiss); Webster v. Spencer, No. 17-1472, 2020 WL 2104231, at *5
`
`(D.D.C. May 1, 2020) (citing similar cases). That revocation holds legal relevance, as readers
`
`with sufficient stamina will discover.
`
`D. Procedural History
`
`Plaintiffs — 46 States, the District of Columbia, and the Territory of Guam — filed this
`
`action on December 9, 2020. See Redacted Compl. at 5 n.1. Their Complaint alleges three
`
`counts. First, they claim, Facebook has violated, and is violating, Section 2 of the Sherman
`
`Act’s prohibition on monopoly maintenance via the two forms of exclusionary conduct described
`
` 15
`
`
`
`Case 1:20-cv-03589-JEB Document 137 Filed 06/28/21 Page 16 of 67
`
`above: acquiring nascent and potential competitors, and anticompetitively conditioning access to
`
`its APIs. Id., ¶¶ 256–62. Second, Facebook violated Section 7 of the Clayton Act by acquiring
`
`Instagram, thereby “substantially . . . lessen[ing] competition [and] tend[ing] to create a
`
`monopoly,” 15 U.S.C. § 18, and it continues to violate that statute by holding and using
`
`Instagram assets. Id., ¶¶ 263–67. Third and finally, Facebook similarly violated and continues
`
`to violate Section 7 by acquiring and holding WhatsApp. Id., ¶¶ 268–72. Plaintiffs seek
`
`equitable relief for these violations, including an injunction prohibiting similar conduct in the
`
`future and the divestiture of unlawfully held assets, id., ¶¶ 277(2), (8), pursuant to Section 16 of
`
`the Clayton Act. See 15 U.S.C. § 26 (authorizing suits by “[a]ny person . . . for injunctive relief
`
`. . . against threatened loss or damage by a violation of the antitrust laws”).
`
`As noted, the Federal Trade Commission filed a very similar suit against Facebook on the
`
`same day as the State Pl