User Generated Content Sites: 1

Lawrence G. Walters
Given the smashing success of YouTube™ and other video-sharing websites, it was inevitable that the adult industry would see a surge of similar business models involving adult material. Adult dating sites, ex-girlfriend sites, 'tube' sites, freak sites, community sites – you name it, and users are posting it. This online business method seems to be the latest rage in the industry, with about half of our firm's clients looking to sue an adult tube site and the other half looking to open one. A major lawsuit has already been filed against the operators of by powerhouse studio producer, Vivid Entertainment, asserting some interesting claims, including a novel take on the legal effect of § 2257 non-compliance. 1

Given the viral spread of this new business and entertainment model, it is important to examine the legal risks associated with operating a user generated adult content website, and consider whether the legal risks outweigh the potential rewards. This article will delve into the varied legal concerns associated with online erotic video-sharing. As with all legal issues, an article is no substitute for competent legal advice. Before considering the operation of a user generated adult content site, it is essential to consult with an experienced adult industry attorney.

Section 2257 Issues
An obvious place to begin the discussion is with the complicated and nuanced issue of Section 2257 compliance. User generated website content is not, strictly speaking, produced by the operator. Rather, it is provided by the site's users, who may, or may not, have created the content. Everything from erotic spousal activity, to shocking body modifications, to hidden bathroom cams, and even clips from unreleased, professionally-produced adult films, may appear on a typical user generated, adult content site. Most of this content is posted automatically to the website for immediate viewing by the site's users, without prior screening or approval by the webmaster.2 Naturally, the following question comes to mind: Does the operator of such a website need to comply with either the records keeping or labeling requirements of Title 18, U.S.C. § 2257?

As with most 2257 records keeping questions, the issue of compliance comes down to whether the business operation in question "produces" the actual sexually-explicit content. For purposes of this discussion, the term "produces," as defined in Title 18, U.S.C. § 2257(h)(1)(2)(a), includes:

digitizing an image, of a visual depiction of sexually-explicit conduct; or, assembling, manufacturing, publishing, duplicating, reproducing, or reissuing a…digital image…[and],

inserting on a computer site or service a digital image of, or otherwise managing the sexually-explicit content, of a computer site or service that contains a visual depiction of, sexually-explicit conduct.

The term "produces" does not include activities that are limited to:

…digitization of previously existing visual depictions, as part of a commercial enterprise, with no other commercial interest in the sexually-explicit material

* * *


* * *


the transmission, storage, retrieval, hosting, formatting…of a communication, without selection or alteration of the content of the communication, except that deletion of a particular communication or material made by another person in a manner consistent with 230(c) of the Communications Act of 1934 (47 U.S.C. § 230(c)) shall not constitute such selection or alteration of the content of the communication.

Therefore, the relevant consideration comes down to whether the operation of a video-sharing site constitutes digitization of an image, assembly of an image, publication of an image, or managing the sexually-explicit content of a computer site on the one hand; or whether such operation will be considered digitization of a previously-existing visual depiction, mere distribution of the content, or the transmission, storage, retrieval, hosting, or formatting of a communication, on the other hand. Thus far, the courts have not addressed whether the current definitions of compliance-triggering activities, contained in § 2257, apply to the operation of a user generated content website.

In light of the Sixth Circuit's decision striking down § 22573, records keeping compliance issues have taken somewhat of a back seat to other legal concerns, given the widespread industry perception that neither 2257 inspections nor prosecutions will occur until the constitutional issues are sorted out in court. Notwithstanding the accuracy or inaccuracy of this perception, the lull in 2257 activity has provided a unique opportunity for proliferation of user generated content sites. 4

The trial court's decision in the above-referenced case involving Connection Distributing5 held that the operation of a "swingers" classified website, which allowed users to post sexually-explicit images of themselves on profile pages, did not require records keeping compliance so long as the website operator did not control the areas of the site where the users posted the 2257 triggering content.6 While this decision was ultimately superseded by the Sixth Circuit Court of Appeal's opinion declaring § 2257 unconstitutional on it face, the trial court's opinion provides some insight into how this issue might be interpreted by the courts.

The mechanics of the content submission process can significantly impact whether a video-sharing site is exposed to § 2257 compliance burdens. While a final determination whether to comply rests with the site's operator, in consultation with his or her attorney, the following factors might be considered in making this important decision:

1) Whether the content is reviewed and approved by the operator prior to its appearing on the site, or whether it is posted automatically (or some combination thereof);

2) Whether specific categories of content are solicited for, or permitted on, the site, or whether all content types are accepted;

3) Whether any content subjects or categories are deleted after posting, and how decisions relating to deletion of content are made;

4) Whether users are restricted in the manner in which content is submitted; i.e., whether profiles or restrictive forms are used, or whether content can be provided in a free form manner;

5) Whether the site is promoted as featuring specific subjects, or is more general interest in erotic fare;

6) Whether any 'seed' content is included by the operator, and the impact of this content on the ultimate nature of the content submitted by users.

Generally, the less control the operator has over the posting of content by the user, the less likely the site will need to comply with 2257. However, this lack of control comes with a price, since the site operator will therefore be unable to prevent potentially illegal images or video from appearing – even temporarily – on the site. This heightens some of the other legal concerns such as child pornography, obscenity, or copyright infringement, as discussed below.

Even if the webmaster's activities do not fall within the definition of "produces" in the Statute, so as to trigger records keeping obligations, they may meet the definition of the term "distribution." While distributors are not subjected to records keeping obligations under the Statute, they are required to ensure that a proper "label" appears on the 2257-triggering content. From the standpoint of a user generated content website, this means that the webmaster would need to ensure that each depiction of actual sexually-explicit conduct is accompanied by a proper 2257 disclosure statement, identifying the full name and physical address of the records custodian along with the date and title of the work. Given the natural hesitation of many amateur content producers to provide information about themselves when posting sexually-explicit materials, non-compliance by users is virtually guaranteed if webmasters are considered distributors. The labeling issue therefore presents a significant concern.

The legal validity of § 2257 is far from over, since the Government is seeking further judicial review of the Sixth Circuit's opinion. Thus, it is too early to discount the potential impact of 2257 on user generated content sites. The courts could reinstate the current version of 2257 by subsequent decision, or Congress could act to correct the constitutional concerns noted by the court. While passing new laws may lead to new challenges, it bears noting that the appellate court's decision in the Connection Distribution case came after more than 12 years of litigation and repeated constitutional challenges. Given the prevalent attitude of hostility towards the adult industry that currently exists in Washington D.C., it is likely that some sort of performer age verification law will be on the books for years to come.

With respect to the current Statute, there are valid arguments on both sides with respect to its applicability to user generated content. On the one hand, website operators often act to digitize images hosted on user generated sites – even if the process is automated. Erotic images are "inserted" on these user generated content sites by both the user and the operator, and webmasters have some role in "managing" the content of the website – if only to "assemble" or "arrange" the categories or profiles.

On the other hand, the visual depictions posted to the site are "previously existing" and usually not created by the operator. Moreover, the webmaster's activities may well be limited to activities like "transmission, storage, retrieval, hosting, and/or formatting" of the preexisting images, so as to fall within the plain meaning of the records-keeping exemption language. Notwithstanding the above, it remains an open question whether website transmission constitutes 'distribution' within the meaning of Section 2257. If so, labeling is required, at a minimum. Obviously, risks of non-compliance exist. Therefore, a decision can only be intelligently made in consultation with an adult industry lawyer, and must be based on the operator's unique risk tolerance level.

Obscenity & Child Pornography
One of the strengths of the user generated content business model is the fact that the webmaster need not purchase or create content – instead it comes free of charge from the users. This strength is also one of the business model's great weaknesses.

Since the content comes directly from users, the webmaster has no opportunity to make decisions as to what kind of content will appear on the site in question. While other adult website operators only purchase or create content that falls within their own risk tolerance levels, user generated content can (and often does) depict just about anything under the sun. This includes content that might be considered obscene or – worse yet – child pornography.

With respect to obscenity, the inability to review and approve each image or video clip before it is posted to the website means that some content, that the webmaster may not like, ends up on the website – at least for some period of time. The operator can delete the content – either in response to user complaints or its own review process – without losing any exemption that would otherwise be applicable, pursuant to § 2257(h)(b)(V).7 However, removing the content after it has been posted does not change the fact that it may have appeared on the website at one time, and may have been viewed or downloaded by claimants or government agents. One obvious answer is to review and authorize all content before it goes live to the website. In theory, this is a good option, but it has both legal and practical drawbacks. Initially, as a site's popularity increases, so does the amount of content posted to it at any given time. The manpower necessary to review each second of every video clip or every image posted to the website may be cost-prohibitive. Moreover, the decision to review all content ahead of time may impact the viability of any claimed exemption under § 2257, as well as the immunity from civil suits provided by § 230 of the Communications Decency Act (discussed later). Pre-selection of acceptable content may well put the webmaster in the position of "assembling" or "managing" the sexually-explicit content, and thus trigger § 2257 obligations. The impact on these legal issues of any particular posting policy should be properly evaluated by the operator and the legal department. However, the foregoing helps illustrate the "Catch 22" facing many user generated content website operators, since both auto-post and content review policies come with associated legal pros and cons.

One of the key advantages of 2257 compliance is the almost automatic defense to child pornography claims. The child pornography issues associated with user generated content are serious. Given the lack of 2257 performer records, website operators will usually be in the position of being unable to prove the age of individuals depicted on their user generated content website. No records mean no proof of age and possibly no defense to child pornography charges.

Prosecutors in the federal system use something called the "Tanner Scale" to prosecute individuals for child pornography charges, particularly where the actual birth date of the individual depicted in the images is unknown. The Tanner Scale allows prosecutors to call a pediatrician to the stand to testify regarding such factors as breast development, presence/absence of pubic hair, and maturity of the inner thigh tissue, when reviewing images of suspected child pornography, to make prognostications about the suspected age of the individual depicted. Therefore, federal prosecutors need only secure the testimony of a friendly pediatrician "expert" whom is willing to testify that the individual depicted on the user generated post appears to be approximately 16-17 years of age, based on these factors. While the operator may ultimately win his or her criminal trial on issues of reasonable doubt, etc., by that time most of the serious consequences of a child pornography prosecution have been experienced, and the victory is quite hollow. Therefore, child pornography risks constitute one of the major drawbacks of the user generated content business model.

A strict review policy may be necessary to weed out any even arguable underage images, or obscene material, to avoid the serious consequences. However the details and mechanics of how such a policy is instituted, will affect other issues such as § 2257 compliance and § 230 immunity.

In part two of this article, we will look at other legal issues surrounding user generated content sites, including copyright, trademark law, and ways in which a site's terms and conditions can be structured to mitigate such sites' legal concerns.

Lawrence G. Walters, Esquire, is a partner with the law firm of Weston, Garrou, DeWitt & Walters, with offices in Orlando, Los Angeles, Las Vegas, Salt Lake City, and San Diego. Mr. Walters represents clients involved in all aspects of the adult industry. The firm handles First Amendment cases nationwide, and has been involved in much of the significant Free Speech litigation before the United States Supreme Court over the last 45 years. All statements made in the above article are matters of opinion only, and should not be considered legal advice. Please consult your own attorney on specific legal matters. You can reach Lawrence Walters at, or AOL Screen Name: "Webattorney."

1 Vivid Entertainment LLC v. Data Conversions, Inc. et al, Case No. 2:2007cv08023 (C.D. Ca. Dec. 10, 2007), wherein the Plaintiff claims that's failure to comply with § 2257 results in unfair competition, with respect to all the other websites that are required to comply.
2 Sometimes all of the content is pre-screened by the operator; however this practice may impact some of the legal issues, as discussed below.
3 Connection Distributing Co. v. Keisler, 505 F.3d 545 (6th Cir. 2007).
4 It should be noted, however, that failure to comply with 2257 requirements could result in civil claims based on unfair competition, as have been asserted in the lawsuit by Vivid Entertainment against See Vivid Entertainment LLC, supra.
5 Connection Distributing Co. v. Gonzalez, Case No. 1:95CV1993 (N.D. Oh. 2006).
6 The case did not decide whether the "labeling" obligations were triggered by this activity, however.
7 Some deletion policies may be so broad as to result in "management" or "assembly" of the content, so caution is urged when developing a deletion policy.


More Articles


Privacy Notices Shouldn’t Be Treated as an Afterthought

Corey D. Silverstein ·

Legal Issues Pop Up When Filming Sex in Public

Lawrence G. Walters ·

The Importance of Patents in the Sex Tech Industry

Maxine Lynn ·

The European Legal Scene: Challenges, Opportunities in 2017

Stephen Yagielowicz ·

Will Your Business Need a Data Protection Officer?

Chad Anderson ·

A Legal Primer to Help Develop Explicit Brands Previously Off Limits

Lawrence G. Walters ·

Preventing Data Breaches Staves Off Big Legal Claims

Chad Anderson ·

Trademark Ruling a Victory for Adult Products, Services

Marc Randazza ·

Data Privacy Is Tightening Up in the E.U.

Chad Anderson ·

Preventing Legal Problems Before They Start

Corey D. Silverstein ·
Show More