How to avoid IP rights traps in software development?
If I pay for development, will I own the code? Who will obtain intellectual property rights for my app? These questions are one of the top questions asked by our clients at the beginning of their business journey. According to the Dutch Intellectual Property rights legislation, the creator is the owner by default, which means those who wrote the code own it. Unless written contract states the difference.
Thus, when outsourcing software development, it is paramount to make sure that all the IP (Intellectual Property) rights, business ideas, content, documentation, and the source code remain under the sole ownership of the client.
If you develop with us, the answer is: YES, you will. The case is we are the rare ones among software development companies that transfer all IP rights to the client. I cannot emphasize more how important that is to manage IP rights transfer. The earlier, the better. This is what can happen if the issue is neglected in advance:
- It might harm business. The client could get into the “vendor lock” (Giants like Oracle and Microsoft tend to apply these “vendor lock” strategies making the clients very dependent on their technologies).
- It can be costly. Every minor change in the project may require high costs.
- It might hurt the client’s customers. In the end, it could mean that the client is held hostage by the service provider and so their service to their customers is entirely dependent on the decisions between them and the service provider.
- It might harm the client’s collaboration with investors. The client must own all IP, source code, knowledge, and materials for investors. It is an immediate red flag for them if it is not the case.
This article will outline how to deal with IP rights to make sure all the boxes are checked for the client’s safety.
One could name four types of intellectual property rights relevant to software: patents, copyrights, trade secrets, and trademarks.
Types of Intellectual Property rights applicable to software development.
A different kind of legal protection covers each one. Patents, copyrights, and trade secrets are used to protect the technology itself. We will not cover trademarks legislation in this article, as they do not protect technology but serve to distinguish a product in the marketplace.
Everyone who is involved in the project development can overstep IP:
- Employees — have the moral right to own the IP developed during employment; however, they are usually restricted by the employment contract.
- Consultants/individual contractors — unless a written contract, they may own the IP.
- Vendor company to develop software — even though clients pay for their services, they are not necessarily the owners unless it is documented.
All the code developed on clients’ request could be roughly divided into three major types:
1. Existing/Third-Party code — already used by the developing company in other projects.
The vendor may use the code they created or already used for the other client to develop the software. Usually, the vendor is not interested in giving up the ownership of this type of code as they might want to continue using it for other clients. One of the ways to manage this type of IP rights is to pay a license for the code in a way that is compatible with the client’s project.
Content used in the project like imagery, sounds, and videos could also be mentioned here, as it might also have restricted usage policies, and violations may cause significant fines.
2. Open-source code — publicly accessible technologies frequently used in the development, that are eligible to be modified and shared.
Definitely, the client can neither own the IP rights to the open-source projects nor maintain exclusive control over them.
However, the client must be aware of what open-source software is used in their project and ensure that the developer is eligible to use it and all the other compliance requirements are met. There could also be restrictions that the client must be aware of. Violation of the open-source licenses could lead to significant risks of the whole project, e.g., by most GPL licenses, one must also publish the source code of the complete project.
Please, read a separate article about open-source third-party technologies that we use in our works and their terms and usage conditions. To name a few, they are GPL, GNU, BSD, MIT, APACHE.
3. Unique code — the code explicitly developed for a particular business.
If the project IP is bespoke to the client’s company, the software may be of limited use to the developer, so they may be more willing to assign ownership of it to the client or grant them an exclusive license. You might be restricted by license terms related to the existing code IP and third-party software IP included within the end product.
Considering the combination of these three types of code used and the business model of our client, we manage IP rights the following way:
How Moqod manages Intellectual Property rights transfer:
- Usage rights for the existing code: depending on the definition stated in the agreement, we negotiate terms of its usage with the client.
- Access rights for the open-source code: we help clients obtain all the necessary licenses or perform all the required compliance operations (copyright notifications, etc.).
- Full ownership for the unique code developed: yes, FULLY transferred rights so that the client will be the actual owner (commercialize and replicate it for his\her benefits).
What else could the client do to protect IP rights for their app?
- Pay special attention to the Ownership section in the software development contract. Ensure that all the code developed for the project is stated as ‘work made for hire.
- Add The Source Code Ownership section in the vendor agreement for additional protection and assurance. State all third-party software used along with the usage terms, conditions, and restrictions.
- Check employment agreements and consultancy agreements. Their contracts must contain the at-will assignment of all the inventions and the associated IP rights developed during the employment period. It mainly concerns the senior executives.
- Keep a written record of who helped design and create the source code.
- Perform an IP audit regularly using, for example, external juridical help. Double-check and triple-check.
Bonus track for startups
From our perspective, a failure to develop and execute an IP strategy is the most common mistake startups make when it comes to developing (or executing on) a well-thought IP strategy. So why do startups neglect a plan to fix some of their company’s most valuable assets?
Startups can acquire and protect their IP assets and can shield themselves from potential exposure to third-party infringement. By taking the time up-front with qualified IP counsel to outline their existing and contemplated IP assets and to develop a plan of action to acquire and protect them, startups can reap significant value from the IP assets they create and can shield themselves from potential exposure to third-party infringement.
It is cheaper to take appropriate action than to have to deal with IP problems later. Engage qualified IP counsel, create an IP plan and execute it over time. The future success of your business depends on it.
From our numerous conversations with clients and other industry players, we know that most software development firms do not transfer IP rights to their clients. But we do! And we think that working this way should become the industry standard at some point. Meanwhile, we urge clients to be careful and ensure they are warned and adequately informed about the IP rights transfer issues. What do you think about all these IP issues?