Content owners continue to battle with technology providers regarding the scope of protection provided by the DMCA. Content lockers are the latest front in this battle. Capitol Records v. MP3Tunes provides insight not only into the copyright implications of this new technology, but also into the continuing analysis of the safe harbor afforded to infrastructure providers as well as the obligations of content owners and their representatives. This decision analyzes almost all of the elements of the DMCA that I get questions about, and provides a great guide on how to design and implement a DMCA compliance policy.
MP3Tunes provides a locker service allowing customers to store copies of music they have purchased, as well as providing a music discovery search engine that allows users to store copies of music freely available on the Internet. The owners of the recordings sent take down notices to MP3Tunes identifying over 300 infringing works, and demanding that MP3Tunes take down all other infringing works, even if not identified in the DMCA notice. This tactic is often used by copyright owners who state that the list of infringing works in their notice is merely a “representative list.” MP3Tunes removed links to the works contained in its music identification service, but did not remove the works from users lockers. MP3Tunes also asked the complainant to actually identify those works not set out in the initial DMCA notice.
The first element of the decision that is important to infrastructure providers is the statement that as a matter of legal doctrine, safe harbor provisions are to be narrowly construed. Quoting the Aimster decision, the court held that “[s]ervice providers must do what [they] can reasonably [be] asked to do to prevent use of its service by ‘repeat infringers.’” The three elements providers must implement in their repeat infringer polices are:
1. Having a system for responding to takedown notices;
2. Not interfering with a copyright owner’s ability to issue notices; and
3. Terminating users who repeatedly or blatantly infringe copyrights.
The court held that MP3Tunes met these criteria. Not only did MP3Tunes maintain a system for tracking content, it also terminated users who repeatedly infringed copyrights. MP3Tunes also met the second criteria when it responded to takedown notices by removing links to infringing content from its identification service. However, the fact that it did not terminate users who shared multiple links to content identified on a notice did not remove MP3Tunes from safe harbor. The court aligned with settled precedent that DMCA notices are not, by themselves, evidence of infringement. So, in order to be a “repeat” or “blatant” infringer, a notice must identify a user and infringing content specifically.
The decision also adds clarity to how notice providers must identify the works they seek to be removed. The DMCA requires notice providers to identify those works that are the subject of the notice, and include sufficient information for the recipient of the notice to locate those works. Confusion often arises when there are multiple infringements of the same work. In these cases, notice providers may include a “representative list” of those works. Often, however, notice providers simply state, as they did in this case, “all songs” by an artist. The court held that simply providing a representative list is not sufficient if it does not include information, such as a url, that will allow the recipient to locate the allegedly infringing material.
While the court held that those notices that simply contained a phrase like “all songs” were not valid, once the notice provider had given the recipient sufficient information that the material could be located, its obligations were satisfied. In this case, because MP3Tunes could search for the web address identified in the notice, the exact location need not be identified. I believe that the court came to this conclusion simply because given the structure of MP3Tunes’ service, there was no way the notice provider could in fact identify the location. However, MP3Tunes kept track of this information.
The third issue addressed by the court is what constitutes a “red flag” removing a provider from safe harbor. The court concluded, as have many courts, that if the circumstances require a provider to conduct an investigation to determine whether the material, or acts, identified by the red flag are a violation of copyright law, it is not a red flag. Put another way, the circumstances must be fairly blatant to be within the definition of a red flag. In this case, the fact that content was downloaded from a file sharing site was not a red flag, since file sharing sites have legitimate uses. Further, although MP3Tunes received notices from members that its site was used for infringing purposes, these notices, taken by themselves, were not red flags.
Finally the court discussed whether the fact that MP3Tunes made money off its service, and had the ability to delete songs, removed it from safe harbor. The court held that it did not. As many courts have held, direct financial benefit means receiving actual monetary compensation from the infringing act. In this case, not only did the MP3Tunes service have non-infringing uses, the company actually removed material identified in a DMCA notice.
The fact that MP3 could delete user accounts, and controlled the servers, did not remove it from safe harbor. Again, like many courts before it, this court held that “control of the infringing activity” means actual control, and not simply “the ability to remove or block access” to the allegedly infringing material.