In a recent fair use case, the U.S. Court of Appeals for the Ninth Circuit held that installing software on more computers than provided for by the license is not fair use, even if the software is actually only run on the licensed number of computers. Wall Data, Inc. v. L.A. County Sheriff’s Dep’t., 447 F.3d 769 (9th Cir. 2006). To reach this result, the court threw the baby out with the bathwater, giving software makers a unique presumption of market harm for any use outside of their licensing agreement. The outcome might be correct, but the reasoning is overbroad and potentially harmful to lawful uses.
The L.A. Sheriff’s Department purchased 3,663 licenses for Wall Data’s software (now sold by NetManage), but in the process of setting up computers in a new facility, they copied the same hard drive to all the computers, such that Wall Data’s software ended up on 6,007 computers. IT departments often use this method to manage networks with many computers because it greatly increases the efficiency of the initial setup process and it allows them to fix problems more quickly. In an attempt to comply with their licenses, the Department limited the number of computers that could actually run the software to the number of licenses they purchased by requiring that a network administrator assign a computer one of the licenses before that computer could open the program.
The Ninth Circuit upheld the trial court’s judgment for Wall Data on its copyright infringement claim, denying the Sheriff’s Department’s fair use defense. The Court held that all four fair use factors, as enumerated in §107 of the copyright law, weighed against the Department.
The Department’s use was not favored by the first factor — the “purpose and character” of the use — because the Court found it to be both non-transformative and commercial. While the Department is a government agency, not a commercial business, its use was commercial because it engaged in “repeated and exploitative copying” to avoid the cost of purchasing more flexible licenses. The court also specifically noted that the use “did not promote the advancement of knowledge and the arts,” treating that as a separate element of the first-factor analysis. The second and third factors, the type of work copied and the amount copied, also weighed against the Department, although the first and fourth were the most significant.
In considering the fourth factor, which weighs the harm to markets for the original work, the court relied on an expansive view of potential licensing markets, stating that “whenever a user puts copyrighted software to uses beyond the uses it bargained for, it affects the legitimate market for the product.” Judge Pregerson, writing for the court, expressed concern that the digital nature of software facilitated overuse through easy copying.
Unfortunately, the court’s analysis on this factor reached too far. While the judges are likely correct that the fourth factor weighs against the Department, it should be because the potential licensing market in this case (something similar to the “concurrent use” licenses that many software makers sell) was traditional and reasonable enough to consider the harms to that market, not because software deserves special, enhanced protection from any unauthorized use.
Most traditional fair uses are not bargained for, such as quoting for criticism, and it is not clear in the court’s analysis what distinguishes software; it may certainly be quoted for criticism and often is. Instead of offering a special rule that assumes software authors should get paid for any and all uses of their product, when no other authors are accorded such a privilege, the court should have rested on its more precise determination that the Department could easily have bargained for the flexibility it needed and didn’t.
To complement its broad view of market harm, the court also offered a confusingly narrow vision of fair use: “[it] is appropriate where a “reasonable copyright owner” would have consented to the use, i.e. where the “custom or public policy” at the time would have defined the use as reasonable. As Michael Madison has noted, the legacy of this case in the Ninth Circuit may be this restrictive view of the fair use doctrine. That would be unfortunate, because it is squarely at odds with a core principle underlying fair use: that certain uses, unauthorized by the copyright owner, are protected regardless of the lack or even likelihood of permission.
While the court did not strike a direct blow against fair use in this case, the decision may have the unfortunate effect of choking off the development of novel and interesting uses for software by providing a confusing fair use standard and requiring an upfront bargaining process available only to the largest software buyers.