How can I profit from my software without selling it? What is a license and which rights does it give to the users of my software? Does the license provide enough protection for my source code? How far does my liability for the software go? Am I obliged to guarantee its functionalities?
It is highly likely that, at some moment, every software-developing company has asked itself at least one of the questions above. The transfer of intellectual property (IP) is a burning issue of importance for every inventive and ambitious business striving to launch their newly created product out on the market, considering the risks which may accompany such a business venture. Rare are those who are willing to entirely waive the rights they hold as the original creators and owners of particular software, and that is exactly where the software license agreement enters the scene as the main asset for offering the software to potential users without transferring the ownership itself.
We have written about the negative consequences of the illegal use of software (in Serbia, particularly) and the ways for companies to avoid imposing the possible penalties by the competent authorities by complying their business activities with the law. This time, we focus on a slightly different situation – in case your company develops the software that is being provided for use to the third party, it is immensely important to establish proper protection on time in order to prevent the risks that typically accompany any intellectual property transfer.
What does that mean? Simply, the first (and crucial) step is precisely defining the rights and obligations arising out of such a business relationship. As previously mentioned, the best way to do so is to enter into a comprehensively tailored software license agreement.
Licensing copyright (software, in particular) basically means granting selected rights out of the wide scope of the rights belonging to the holder of the copyright – usually, that is its creator, although that doesn’t always have to be the case. By granting a software license, the owner of the software provides the user with the specified set of rights on the software, but the ownership itself does not get transferred.
For instance, by purchasing a license for a Microsoft Office plan, the user actually buys a right to use one (or more) counterparts of software in accordance with the terms of the software owner (Microsoft). Therefore, users’ authorizations are limited solely to those rights provided by the owner – right to use, copy, etc., whereas the ownership right remains with the owner – Microsoft.
This way, the software owned by one company (or individual) may be used by a wider scope of subjects who are obliged to comply with precisely defined rules. Such a partial transfer brings benefits to both parties involved:
The company that had developed the software (e.g. licensor) remains the owner, which enables it to keep the essential rights comprised in the copyright and to control the use of the software, while at the same time acquiring additional income from providing it to multiple customers.
A company using the software (e.g. licensee) gets to “buy” a specifically determined set of rights on the software critical for their own business activities for a smaller price than the one it would have to pay in case it purchased the software entirely.
The particular rights included in the software license may differ, depending on the type of license. Anyhow, typically the two main ones are the right to use and the right to reproduce the software in enough copies necessary for the internal purposes of the licensee. Besides these two “usual” rights, some additional rights may be granted to the company wishing to use someone else’s software, such as:
- the right to distribute the software, which includes handing out copies of the software to third parties
- the right to sub-license the software, which includes granting the specified scope of rights on the software to the licensee’s customers
- the right to modify the software and to create derivative works out of it, which would, for instance, include creating a new version of the software.
Anyhow, the scope of the rights granted to the licensee depends entirely on the licensor who gets to decide on what their customer will be allowed to do with the licensed software. Generally speaking, when it comes to the proprietary license on software – the most restrictive among the licenses, the owner opts to solely grant to the user the right to use the copy of the software and eventually to make copies thereof for internal purposes only, excluding the delivery of the open source code to the user or providing the permission for modifications or further distribution of the software.
On the other hand, you can anytime “loosen up” the protection of your software by establishing an OSS license and thus provide more freedom to your users in regard to the use of your software.
There is a variety of questions that need to be answered in order for the software license agreement to comprehensively describe the business relationship between the licensor and licensee. However, as previously mentioned, the scope of the software license is the key clause in the agreement taking into account that it specifies the particular rights granted to the end-user and simultaneously sets the boundaries in that term. Depending on the limitations that the licensor wants to impose on the licensee, the license can be, for example:
- non-exclusive or exclusive,
- perpetual or time-limited,
- worldwide or territory/industry limited.
This list is, however, not exhausted and can vary depending on the nature of the business relationship between you and your licensee(s). Naturally, it is essential for the software license agreement to be appropriately adapted to your particular needs, so that it is clear which rights you are (not) granting to your users, which will finally contribute to avoiding the different interpretations and potential misuses.
Having in mind the previously explained purpose of the license itself, it can be concluded that the main objective of the software license agreement is to specify the rights and restrictions arising out of the relationship between the licensor and licensee. However, it must not be forgotten that the primary advantage of this type of contract is the mere fact that it enables the owner of the software to “share” its software without losing control over it. Regardless of whether your software is intended for use by companies or you are targeting mainly tech-oriented individuals, the benefits of entering into a comprehensively drafted agreement with regard to the use thereof are numerous.
To sum up, a software licensing agreement happens to be a golden mean between securing your software and making good use of it. Just as well, this type of agreement is a very useful tool for preventing the majority of the imaginable troubles that may occur between you and the purchasers of the license to use your software, which usually arise due to the fact that not all relevant matters with regard to this business relationship have been set in place on time.
In other words, when it comes to comparing these two types of agreements, the question is not always “which one should I choose” but instead might be “when do I need both”?
- terms of purchasing a product via an e-commerce website or application.
On the other hand, as stated earlier, the subject of the software license agreement is a particular scope of rights on the software. Therefore, by signing this type of contract with your customers, you provide them with a product instead of a service. Consequently, this leads to some additional issues which must be covered by specific rules and procedures in order to maintain the safety of your software.
On the other hand, by downloading the Facebook app the user concludes a license agreement with Meta company. In that case, although it might seem that the user has the same scope of rights as when using the web version of the same social network, there are significant differences in the rights and obligations of the provider, depending on the particular option user has chosen.
In case your software fails to comply with the specifications set in the software license agreement, you will probably have the obligation to provide some additional services including maintenance and support in order to fix the bug. In other words, the customer has the right to request from you repair the copy of the software which you have delivered to them in accordance with the license agreement. Besides, if you decide to offer your users a newer or better version of the software, you should lay down some ground rules explaining the procedure of updating and upgrading the software.
To sum up, entering into a software license agreement with your customers should be the first item on your checklist once you decide to place your new software on the market – this type of contract undebatably is one of the most convenient ways to share your breaking new idea with the world, while simultaneously establishing the adequate level of its protection.
In addition, if you adequately analyze all the potential risks at the right moment, you will be in a position to detect the potential threats and keep them from happening. Simply put – protect your software and do not risk being caught unprepared in case it is inappropriately used.