Communications Decency Act immunizes hosting provider from defamation liability

Johnson v. Arden, — F.3d —, 2010 WL 3023660 (8th Cir. August 4, 2010)

The Johnsons sell exotic cats. They filed a defamation lawsuit after discovering that some other cat-fanciers said mean things about them on Complaintsboard.com. Among the defendants was the company that hosted Complaintsboard.com – InMotion Hosting.

Sassy is my parents' cat. She hisses whenever I'm around, though they say she's a nice cat otherwise.

The district court dismissed the case against the hosting company, finding that the Communications Decency Act at 47 U.S.C. §230 (“Section 230”) immunized the hosting provider from liability. The Johnsons sought review with the Eighth Circuit Court of Appeals. On appeal, the court affirmed the dismissal.

Though Section 230 immunity has been around since 1996, this was the first time the Eighth Circuit had been presented with the question.

Section 230 provides, in relevant part, that “[n]o provider or user of an interactive computer service shall be treated as the publisher or speaker of any information provided by another information content provider.” It also says that “[n]o cause of action may be brought and no liability may be imposed under any State or local law that is inconsistent with this section.”

The Johnsons argued that Section 230 did not immunize the hosting company. Instead, they argued, it did just what it says – provides that a party in the position of the hosting company should not be treated as a publisher or speaker of information provided by third parties. The Johnsons argued that the host should be liable in this case regardless of Section 230, because under Missouri law, defendants can be jointly liable when they commit a wrong by concert of action and with common intent and purpose.

The court rejected the Johnsons’ argument, holding that Section 230 bars plaintiffs from making providers legally responsible for information that third parties created and developed. Adopting the Fourth Circuit’s holding in Nemet Chevrolet v. Consumeraffiars.com, the court held that “Congress thus established a general rule that providers of interactive computer services are liable only for speech that is properly attributable to them.”

No evidence in the record showed how the offending posts could be attributed to the hosting provider. It was undisputed that the host did not originate the material that the Johnsons deemed damaging.

Given this failure to show the content originated with the provider, the court found in favor of robust immunity, joining with the majority of other federal circuits that have addressed intermediary liability in the context of Section 230.

Web host did not breach contract by terminating rude customer

Mehmet v. Add2net, Inc., — N.Y.S.2d —-, 2009 WL 3199876 (N.Y.A.D. 1 Dept. October 8, 2009)

Plaintiff website operator didn’t pay his monthly hosting fees on time. He called the hosting company and said he’d be sending a check, but in the meantime the web host exercised its right under the hosting agreement to suspend Plaintiff’s account for nonpayment. Plaintiff called and left a nasty voicemail, using an obscene word to threaten to sue the hosting company if his website was not reactivated.

In response to this angry voice mail, the web host terminated Plaintiff’s account. He sued for breach of contract. The web host moved to dismiss at the trial court level and the court granted the motion. Plaintiff sought review. On appeal, the court affirmed the dismissal.

Of particular importance was a provision in the hosting agreement that incorporated by reference an Acceptable Use Policy (AUP), and provided that any breach of that policy would be grounds for suspension or termination of plaintiff’s account. Under the AUP, plaintiff agreed “not to abuse whether verbally or physically or whether in person, via email or telephone or otherwise … any employee or contractor of [defendant].”

The nonpayment coupled with this violation of the web hosting acceptable use policy undercut Plaintiff’s breach of contract claim.

Court enforces forum selection clause in web hosting agreement

Bennett v. Hosting.com, Inc., 2008 WL 4951020 (N.D. Cal. November 18, 2008)

Bennett filed an astounding 30-count complaint against defendant Hosting.com. Though the Managed Hosting Agreement designated Jefferson County, Kentucky to be the sole and exclusive venue for actions brought in connection with the agreement, Bennet brought the action in federal court in Northern California. Hosting.com moved to dismiss for improper venue. The court granted the motion.

Kentucky on a map

The court held that Bennett failed to prove that the forum selection clause in the hosting agreement was unreasonable. The fact that Hosting.com may have had superior bargaining power and the agreement appeared to be non-negotiable was not enough to render the agreement unconscionable. Moreover, Bennett failed to demonstrate how the forum selection clause was against any public policy of California. And the court rejected her argument that the case belonged in California because Kentucky does not recognize certain of the causes of actions in the complaint. After all, a Kentucky court could apply California law.

The court also rejected Bennett’s argument that the forum selection clause shouldn’t apply because a number of the claims arose from tort law and did not involve the agreement. This argument was rejected because many of the tort claims would require the same findings of fact as the contract-related claims. Moreover, and perhaps more importantly, the forum selection clause was broad. All the claims appeared to be “in connection with” the agreement. That was enough in this case to bring them in.

(Missing Kentucky image courtesy Flickr user dog_manor under this Creative Commons license.)

Scroll to top