Hopson, Benjamin v. Google, LLC

CourtDistrict Court, W.D. Wisconsin
DecidedMarch 31, 2023
Docket3:21-cv-00320
StatusUnknown

This text of Hopson, Benjamin v. Google, LLC (Hopson, Benjamin v. Google, LLC) is published on Counsel Stack Legal Research, covering District Court, W.D. Wisconsin primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Hopson, Benjamin v. Google, LLC, (W.D. Wis. 2023).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE WESTERN DISTRICT OF WISCONSIN

BENJAMIN HOPSON, II, d/b/a GELBOORU/GELCOM, and BLUETYPE, LLC,

Plaintiffs, OPINION AND ORDER v. No. 21-cv-320-wmc GOOGLE, LLC and DOES 1-2

Defendants.

Benjamin Hopson, II owns BlueType, LLC, and does business as website Gelbooru/Gelcom (“Gelbooru”). Collectively, these plaintiffs allege that Does 1 and 2 knowingly submitted false takedown notices against Hopson’s website in violation of the Digital Millennium Copyright Act, 17 U.S.C. §§ 512, 1201 et seq. (“DMCA”). Plaintiffs further allege that in responding to those takedown notices, Google, LLC violated the DMCA’s takedown notice procedures and failed to restore certain content to the website. Google moves to dismiss under Federal Rule of Civil Procedure 12(b)(1) and (6) because: the court lacks jurisdiction over this lawsuit; and the complaint fails to state a viable claim against Google. For the following reasons, the court will dismiss defendant Google, as well as provide plaintiffs the opportunity to submit an amended complaint clarifying their allegations against Does 1 and 2. ALLEGATIONS OF FACT1 Gelbooru is website of Japanese animation and related images where users can upload, search, and comment on its content. Google is a technology company that provides

a popular, eponymous search engine and a web browser called Chrome. At some point, Google received multiple DMCA takedown notices from Does 1 and 2 claiming that certain content on Gelbooru infringed their copyright. After redacting the complainants’ contact information, Google forwarded these notices to plaintiffs. Google also preemptively “delisted” the disputed content from its search engine, disabled “site content javascripts,” and displayed notices on Gelbooru that allegedly “would scare the average user into

thinking something” on the website “is malicious” in nature. (Dkt. #2 at 4.) As a result, plaintiffs claim that defendants’ wrongful “interference with business contracts” has caused Gelbooru to generate less revenue. (Id.) After plaintiffs received the redacted takedown notices, they submitted multiple counter notices to Google contending that the disputed content did not infringe anyone’s copyright and asking that the disputed content be restored. However, when Google replied

to plaintiffs, it was only to convey that no further action would be taken or to state “a pretextual reason to disable access to the site.” (Id. at 5.) Google has still not restored some of this disputed content after over five years in “review.”

1 The court draws the following facts from the complaint and supplement (dkt. ##1, 2), “accept[ing] as true all of the well-pleaded facts in the complaint and draw[ing] all reasonable inferences in favor of” plaintiffs. Jakupovic v. Curran, 850 F.3d 898, 902 (7th Cir. 2017) (standard for review under Rule 12(b)(6)), (internal citation omitted); see also Bultasa Buddhist Temple of Chi. v. Nielsen, 878 F.3d 570, 573 (7th Cir. 2017) (“A motion to dismiss under Rule 12(b)(1) tests the jurisdictional sufficiency of the complaint, accepting as true all well-pleaded factual allegations and drawing reasonable inferences in favor of the plaintiffs.”). OPINION In this lawsuit, plaintiffs not only claim that Google altered the content and appearance of Gelbooru and failed to follow DMCA takedown notice procedures -- all

damaging plaintiffs’ business reputation and interfering in their contractual relationships with advertisers -- but also by redacting the Does’ identities and contact information from the takedown notices, Google has ensured that plaintiffs cannot identify, much less pursue their claims against, these other defendants. As noted, Google moves for dismissal under Federal Rule of Civil Procedure 12(b)(1) for lack of jurisdiction, and under Rule 12(b)(6) for failure to state a claim. The court will address Google’s motion, and then turn to the

viability of plaintiffs’ claims against Does 1 and 2. I. Subject Matter Jurisdiction

As an initial matter, the court must address the question of its own subject matter jurisdiction. As discussed below, even if the DMCA does not provide plaintiffs with a viable cause of action against providers like Google, the statute does create liability for knowingly making false claims in a takedown notice as alleged against Does 1 and 2. See 17 U.S.C. § 512(f) (creating liability for misrepresentations in takedown notices and in counter notices). Therefore, the court has jurisdiction over this lawsuit under § 1331,

regardless of the merits of plaintiffs’ claims against Google. II. Failure to State a Claim

The court next turns to Google’s motion to dismiss the claims against it under Rule 12(b)(6), which challenges the legal sufficiency of the complaint on the basis that plaintiffs have failed to state a claim for which relief can be granted. Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009) (quoting Bell Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007)). In particular, dismissal of a claim is appropriate where “the allegations of the complaint, however true,

could not raise a claim of entitlement to relief.” Twombly, 550 U.S. at 558. To survive a motion to dismiss, therefore, a complaint must “plead[ ] factual content that allows the court to draw [a] reasonable inference that the defendant is liable for the misconduct alleged.” Iqbal, 556 U.S. at 678.

A. Plaintiffs’ DMCA Claims Title II of the DMCA limits the liability of internet service providers (“ISPs”) for copyright violations committed by their users. Nevertheless, plaintiffs claim Google is liable for failing to follow certain procedural steps for addressing takedown notices under

§ 512(g) of the DMCA. Unfortunately for plaintiffs, that section of the statute actually creates a “safe harbor,” which protects ISPs from suit for taking down allegedly infringing content. Specifically, under § 512(g), an ISP’s obligations are initially triggered by the receipt of a takedown notice from a copyright holder declaring that one of the ISP’s users has violated copyright laws. 17 U.S.C. § 512(g)(2). After receiving the takedown notice,

the ISP must then “take[ ] reasonable steps promptly to notify the subscriber that it has removed or disabled access to the material.” § 512(g)(2)(A). The subscriber may then file a counter notice declaring that the disputed material is not infringing and was wrongfully removed under § 512(g)(3). Moreover, when an ISP receives a valid counter notice, it must then “promptly provide[ ]” a copy to the copyright holder who filed the original takedown notice. Id. at § 512(g)(2)(B). Outside of situations where the copyright holder notifies an ISP that it has filed a court action against the alleged infringer, the ISP must then restore the disputed material within 10 to 14 business days under § 512(g)(2)(C). See Martin v. Tumblr, Inc., No. 15-cv-8338, 2017 WL 11665339, at *4 (S.D.N.Y. Feb. 10,

2017) (providing a detailed overview of the § 512 procedure).

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

Related

Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Kipp v. Royal & Sun Alliance Personal Insurance Company
209 F. Supp. 2d 962 (E.D. Wisconsin, 2002)
Langdon v. Google, Inc.
474 F. Supp. 2d 622 (D. Delaware, 2007)
Alexander v. Sandoval
532 U.S. 275 (Supreme Court, 2001)
Meanith Huon v. Nick Denton
841 F.3d 733 (Seventh Circuit, 2016)
Jian Zhang v. Baidu.Com Inc.
10 F. Supp. 3d 433 (S.D. New York, 2014)
Lattanzio v. Comta
481 F.3d 137 (Second Circuit, 2007)
Bultasa Buddhist Temple of Chicago v. Nielsen
878 F.3d 570 (Seventh Circuit, 2017)
Jakupovic v. Curran
850 F.3d 898 (Seventh Circuit, 2017)
Hard Drive Productions, Inc. v. Doe
283 F.R.D. 409 (N.D. Illinois, 2012)

Cite This Page — Counsel Stack

Bluebook (online)
Hopson, Benjamin v. Google, LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/hopson-benjamin-v-google-llc-wiwd-2023.