Analysis: Is The Website Owner Responsible For User Generated Content?

Authored by David Oxenford on April 14, 2008 - 7:29am.

Website operators who allow the posting of user-generated content on their sites enjoy broad immunity from legal liability. This includes immunity from copyright violations if the site owner registers with the Copyright Office, does not encourage the copyright violations and takes down infringing content upon receiving notice from a copyright owner (see our post here for more information). There is also broad immunity from liability for other legal violations that may occur within user-generated content. In a recent case, involving the website Roommates.com, the US Court of Appeals determined that the immunity is broad, but not unlimited if the site is set up so as to elicit the improper conduct. A memo from attorneys in various Davis Wright Tremaine offices, which can be found here, provides details of the Roommates.com case and its implications.

In the case, suit was filed against the company, alleging violations of the Fair Housing Act, as the site had pull-down menus which allowed users to identify their sex, sexual orientation, and whether or not they had children. Including any of this information in a housing advertisement can lead to liability under the law. The Court found that, if this information had been volunteered by users acting on their own, the site owner would have no liability. But because the site had the drop-down menus that prompted the answers that were prohibited under the law, liability was found.

The protections offered for those hosting sites come from two separate statutes. The protections against copyright infringement claims are in the Digital Millennium Copyright Act, and require that the site owner take several steps to secure the safe harbor from liability. Registration of an individual who can be contacted by a copyright owner if infringing material is posted is required. The Copyright Office's instructions for such registration can be found here. The site owner must take down infringing material if properly notified, and should not encourage or promote such infringement.

The protection against most other liability stems from Section 230 of the Communications Decency Act, and has, for the most part, been interpreted very broadly to protect the company running the website from anything posted on the site by third parties. The holding of the Roommates.com case, while signaling a slight retreat, basically brings the requirements for the safe harbor closer to those for copyright protection in that the site owner cannot be a part of the activity that causes to liability - here by providing the option to choose certain classifications that could be construed as a violation of the law. While the details and subtleties of the decision are discussed in greater detail in our firm's memo, the basic point seems to be that where the site owner provides part of the content that gives rise to the liability, it cannot claim the safe harbor. If the same information had been posted by third-party site users without the prompts from the site itself, there likely would be full protection for the site owner. Thus, to the extent that you are encouraging website users to post their own content on a site that you own, make sure that your site does not prompt the user into providing any specifics that could be found to have been specifically prompted by site material or information that you provide.

Note that there are no doubt going to be other arguments about how overt a "prompt" must be for the site owner to fall outside the safe harbor. Also note that this is the decision of just one US Court of Appeals and courts in other jurisdictions could decide a case like this differently (in fact there was a dissent here that worried about how lines would be drawn). So there is no doubt that we have not heard the last of this issue.

David Oxenford

David Oxenford is a partner in the Washington, DC office of the law firm of Davis Wright Tremaine LLP. This post originally appeared on DWT's Broadcast Law Blog, and is posted on DMW with the author’s permission. This information is provided for educational purposes only and should not be relied on as legal advice, and should not substitute for competent legal advice from your own attorney.

Image By DOM_2plus1

 

Comments

Roommates.com

The Court’s decision is narrowly limited to conduct by website operators that is allegedly to violate laws prohibiting discriminatory practices, in which it is not the content itself (e.g. “I am white, straight, and Buddhist.”) which results in liability but the type of content (e.g., the race, sexual orientation, or religion of a potential home purchaser) which is elicited, developed, and then published. Roommates.com was alleged to have required subscribers to provide and publish certain information in a context in which that type of information may not legally be used – thus, the website “developed, in whole or in part” the content and was not entitled to immunity under Section 230 of the Communications Decency Act.


This is not at all similar to a website eliciting comments or posts about a particular subject (e.g., personal dating experiences with particular men on dontdatehimgirl.com) but is much closer to a website asking its users to provide specific and unlawful comments (e.g., false assertions that particular men have criminal records or untreated sexually transmitted diseases). In fact, the Court distinguished the case before it from many others in which Section 230 protection did apply by noting that in those cases the website operator “did not design its system around the dissemination of unlawful content.” Fair Housing Council of San Fernando Valley v. Roommates.com, ___ F.3d ___, 2008 WL 879293, *9 (9th Cir. 2008).


In the end, the Court’s opinion is not all that earth-shattering. It’s crafted to be narrowly applicable to the particular case decided and should not alter the Section 230 analysis in most future cases.

Post new comment

The content of this field is kept private and will not be shown publicly.