Software Licensing Agreements in India: Common Commercial Risks

Buying access to software does not necessarily mean buying the intellectual property behind it. Computer programs are protected as literary works under the Copyright Act, 1957, and the copyright owner can permit another person to exercise specified rights through a licence. The software licensing agreement therefore defines the boundary between authorised use and conduct that remains controlled by the copyright owner. This distinction matters for both software companies and their customers. A licence that is too broad may expose the developer's intellectual property, while a licence that is too narrow may prevent the customer from using the software in the manner its business requires. The commercial terms should therefore match how the software will actually be deployed.

Understanding What a Software Licence Gives You

1. A Licence Does Not Automatically Transfer Ownership

Copyright and possession of software are separate concepts. A customer can receive software and have extensive rights to use it while ownership of the underlying copyright remains with the developer or other copyright owner. Section 30 of the Copyright Act allows the copyright owner to grant an interest in the copyright through a written licence. The agreement should therefore distinguish clearly between ownership and permitted use. If the parties intend only a licence, the customer should understand which rights it receives and which remain with the licensor. Ambiguous language can create disagreement later about whether the customer merely acquired access or obtained broader intellectual property rights.

2. Software Use Can Involve Several Copyright Rights

Copyright in a computer program is not limited to preventing someone from copying the program word for word. The Copyright Act gives the copyright owner rights relating to reproduction and other forms of exploitation, as well as particular rights concerning the sale or commercial rental of copies of computer programs. A software licence can therefore regulate several different forms of use. The commercial question is not simply whether a customer is “allowed to use the software.” The agreement should define the particular activities that are permitted under the licence. This becomes increasingly important where software is copied across multiple systems or incorporated into wider commercial operations.

Common Risks in Software Licence Scope

1. The Permitted Use Is Not Defined Clearly

A licensing agreement should identify the scope of the rights being granted. A broad licence may allow use across multiple purposes or territories, while a narrower licence may restrict use to a defined activity or area. The scope should therefore correspond with the commercial arrangement agreed between the parties. Problems arise where the agreement grants a general right to “use” the software without explaining what that means in practice. The customer may assume that the licence covers all of its operations, while the licensor may have intended a more limited permission. Clear boundaries reduce the likelihood that ordinary business use later becomes a licensing dispute.

2. User or Installation Limits Are Ignored

Software licences may limit the number of users, installations or copies that a customer is permitted to operate. Using more copies than the licence allows can amount to unauthorised software use. A business should therefore understand its licence limits before deploying software across an expanding organisation. This risk can arise without deliberate infringement. A company may originally purchase software for a small team and later install it on additional systems as the business grows. Internal software management should therefore track actual use against the permissions purchased.

3. Territory and Commercial Use Are Too Vague

Licensing arrangements can differ significantly in geographical and commercial scope. Rights may be granted broadly or confined to particular territories, markets or uses. The agreement should make those limits understandable to the teams responsible for implementing the software. Territorial restrictions become particularly relevant where businesses operate in several countries. A licence obtained for one market should not automatically be assumed to cover international operations. The same principle applies where software originally acquired for internal use later becomes part of a wider commercial activity.

Ownership and Third-Party Intellectual Property

1. The Licensor Should Have Rights to License the Software

A customer should understand whether the party granting the licence actually owns or controls the relevant intellectual property. A licence cannot provide reliable commercial rights if the licensor itself lacks authority over an important part of the software. Ownership is therefore a central issue in technology licensing. Warranties can be used to address this concern. The licensor may be asked to confirm that it owns the relevant intellectual property and that the licensed technology does not improperly interfere with third-party rights. The appropriate warranty position will depend on the nature of the software and the transaction.

2. Third-Party Components Can Affect the Rights Being Granted

Software products may contain intellectual property originating from more than one source. A software company may own its proprietary development while using other technology under separate licences or contractual arrangements. The rights granted to the customer should therefore be consistent with the rights the licensor itself possesses. This is particularly important where third-party or open source components impose conditions on their use. The existence of such software does not by itself establish a problem, but the underlying licensing conditions should not be ignored. A business should understand whether third-party restrictions affect its ability to use or commercially exploit the overall product.

Commercial Terms That Need Attention

1. Pricing and Payment Should Be Clear

A licensing agreement should specify what the customer is required to pay and how the payment is calculated. Licensing arrangements may use recurring payments, royalties, lump-sum amounts or other agreed structures. Unclear payment provisions can create disputes even where the underlying software performs as expected. The agreement should also explain when payments become due and how continuing charges are determined. Where payments depend on usage or another variable, the basis for calculating the amount should be understandable. Commercial transparency is particularly important in long-term technology relationships.

2. Performance Expectations Should Match the Agreement

Technology agreements may include performance requirements concerning the functionality or quality expected from the licensed technology. If specific performance has been commercially promised, the agreement should explain what is required and what happens when those requirements are not met. Otherwise, the parties may have different expectations about the licensor's responsibilities. Performance obligations should be realistic and connected to the licensed product. A customer may expect particular capabilities while the licensor considers those functions outside the agreed scope. Defining the expected performance can reduce uncertainty when technical problems arise.

3. Confidentiality Should Protect Sensitive Information

Software licensing can involve access to confidential business or technical information. The agreement should identify the parties' responsibilities for keeping that information confidential and restricting unauthorised disclosure. Confidentiality provisions become particularly important where proprietary technology or know-how accompanies the licensed software. The obligations should operate alongside practical safeguards. A contractual restriction has limited value if sensitive information is routinely made available without internal controls. Businesses should therefore consider both the agreement and how confidential information will actually be handled.

Termination Can Be as Important as the Licence Grant

1. The Agreement Should State When It Can Be Terminated

Termination provisions should identify the circumstances in which the licensing relationship can end. Examples may include failure to make agreed payments, breach of contractual obligations or failure to provide promised goods or services. The agreement should also deal with other agreed termination circumstances relevant to the relationship. Without clear termination provisions, the parties may disagree about whether the licence remains in force after a serious contractual problem. This matters because continued software use may depend entirely on the licence. The consequences of termination should therefore be considered before the contract is signed.

2. Post-Termination Use Should Be Addressed

A significant practical question is what happens to the software when the licence ends. The customer should understand whether continued use is permitted and what contractual obligations continue after termination. The licensor should equally understand how its intellectual property will be treated once the commercial relationship has ended. These issues are more difficult to resolve after termination has already occurred. A customer may have built important operations around the licensed software, while the licensor may be concerned about continued unauthorised use. Planning the end of the relationship is therefore an important part of negotiating the beginning of it.

Common Software Licensing Mistakes

1. Treating the Agreement as Standard Documentation

There is no single licensing structure suitable for every technology arrangement. The rights required by a business depend on how it intends to use the software and what the licensor is prepared to permit. A standard document that does not reflect the transaction can therefore create unnecessary restrictions or uncertainty. The agreement should be adapted to the actual commercial relationship. A licence for limited internal use will not necessarily require the same structure as an arrangement involving broader commercial exploitation of technology. The contract should follow the business model rather than the other way around.

2. Ignoring Actual Software Deployment

A company can sign an appropriate licence and still create problems if its employees use the software beyond the authorised scope. Running unlicensed copies or installing more copies than the agreement permits can amount to unauthorised software use. Contract compliance therefore continues after the licence has been signed. Businesses should know how licensed software is deployed internally. This becomes more important as headcount and technology use increase. Periodic checks can identify whether the original licence still matches the organisation's actual requirements.

3. Focusing Only on Price

The lowest licence fee does not necessarily produce the most useful commercial arrangement. Restrictions on use, ownership questions, performance obligations and termination can have greater long-term significance than the initial price. A licence should therefore be assessed as a package of rights and obligations. The same applies from the licensor's perspective. Granting rights too broadly may reduce control over valuable intellectual property or permit uses that were not reflected in the commercial price. Scope and economics should therefore be negotiated together.

Frequently Asked Questions

Conclusion

A software licensing agreement should answer a simple commercial question clearly: what may the customer do with the software, and on what conditions? That requires more than a statement that software is being “licensed.” Scope, ownership, authorised use, payment, confidentiality, warranties and termination should work together as part of the same arrangement. Businesses should also ensure that actual software use continues to match the contractual permissions they have received. A licence that was appropriate when a company had five users may not remain appropriate when the same software is deployed across a much larger organisation. Reviewing software rights as the business evolves can reduce both copyright and contractual risk.

About the Author

Shauree Gaikwad is the founder of Wayver and advises founders and businesses on corporate, commercial and intellectual property matters. Her practice includes software licensing, technology agreements, intellectual property ownership and commercialisation arrangements. She also advises businesses on intellectual property issues arising during commercial transactions. She can be reached at shauree@wayverlaw.com.

This article is intended for general informational purposes and does not constitute legal advice. Software licensing rights and obligations depend on the relevant program, copyright ownership and the particular terms agreed between the parties. Specific advice should be obtained after reviewing the applicable software licence and commercial arrangement.