You worked hard on developing your software. You spent hours coding it, and even more hours bringing it to market. Now, you believe that someone has stolen your code or related intellectual property, and using it in their own product. Does the law provide you with any protections?
Most people believe that copyright law protects paintings, poems, and books. While that is true, copyright law is actually broader in its coverage. Theft of software also constitutes copyright infringement. As far as the law is concerned, code is no different from prose or paint. Copyright gives creators certain exclusive rights over their works, whether those works are novels or website code.
While you do not need to have formally registered your software with the U.S. Copyright Office, doing so is helpful for establishing your ownership. It is also helpful to list a copyright notice on your software, to scare away potential infringers.
When a copyright dispute arises, there are often several self-help steps a copyright owner can take. These generally begin with telling the infringer to stop the infringing activity and/or to pay for the infringement.
When push comes to shove, however, there is only one remedy with teeth: to ask a federal court (through a lawsuit) to order the infringing activity halted and to award a judgment for damages. Because this type of litigation is procedurally complex, an attorney skilled in copyright litigation is required.
However, before seeing an expensive lawyer, you should determine whether you could have a valid claim for copyright infringement. Here are the major elements you must establish to prove infringement:
The question of infringement does not even arise unless the work allegedly infringed is protected by copyright. This means that the work must be:
Learn more about copyright protection for software.
As a practical matter, most cases of software copyright infringement involve a violation of the owner's exclusive right to make copies. That is, someone copies all or part of somebody else's program without the owner's permission. For purposes of illustration, this discussion assumes that is the case here.
Although the focus here is on the right to make copies, the principles discussed relative to copying also apply to all copyright rights that make up the bundle of rights (such as the exclusive right to display the work or create derivative works based on it).
To prevail in an infringement lawsuit, the plaintiff must prove that an infringement actually occurred. If someone is caught with an exact copy of a copyrighted work, or is seen copying it, the plaintiff has what is aptly called a smoking gun. The infringing villain has been caught redhanded.
Unfortunately, this type of evidence usually is not available. Most infringers are smart enough to attempt to disguise their copying. Moreover, there are rarely any witnesses to copyright infringement. Infringement usually happens behind closed doors and the participants rarely admit their involvement.
This means that in most cases you must prove two things to establish infringement:
If these are proven, copying is inferred because there is no other reasonable explanation for the similarities.
To prove access, you must show that the alleged infringer had the opportunity to view and copy your software. This requirement is easy to show if the work is mass-marketed. It may be more difficult if the work has been accessible only to a very few people or the source code has been protected as a trade secret. Problems can develop, for example, when software that is very narrowly distributed under a license agreement is pirated.
Proving substantial similarity is usually the crux of any copyright infringement case, particularly in the software context. Assuming the alleged infringer had access to your work, the similarities between your work and the infringer's must be compared to see if copying may reasonably be inferred. The similarities must be such that they can be explained only by copying having occurred, not by factors such as coincidence, independent creation, or the existence of a prior common source for both programs.
The first step most courts take is to filter out the unprotectable elements of the plaintiff's program before comparing it with the allegedly infringing program. Under this filtration test, those elements of the plaintiff's program that are not protected by copyright are identified and eliminated from consideration. This includes, for example, ideas, elements dictated by efficiency, or external factors or taken from the public domain. After this filtration process is completed, there may or may not be any protected program elements left. If there are, this core of protected expression is compared with the defendant's allegedly infringing program to see whether there has been impermissible copying.
The defendants in most software copyright infringement actions will doubtless claim that any alleged similarities relate only to elements of the plaintiff's program that should be filtered out as unprotectible. This filtration test can make it very difficult for plaintiffs to win infringement cases. Indeed, it makes it difficult for plaintiffs and their attorneys to know whether they have a good infringement case in the first place, since opinions can and will naturally differ as to what elements should and should not be filtered from the infringement analysis.
The clearest cases of copyright infringement involve wholesale copying of your computer code. You will likely have far more difficulty proving infringement when you allege that nonliteral elements of your program have been copied—that is, things other than computer code, such as the user interface.
The bottom line is that it is virtually impossible for even the most experienced software attorney to predict with confidence whether a nonliteral infringement claim will succeed. Thus, plaintiffs who bring these cases enter a crap shoot: You pay your money in legal fees, and take your chance.
Learn more about intellectual property from Nolo's articles on Patent, Copyright, and Trademark.
Need a lawyer? Start here.