Software License Agreement in Malaysia: Template, Key Clauses and Local Law (2026)

What a software license agreement does A software license agreement sets the terms on which a software owner (the licensor) lets another party (the licensee) use its software. The licensor keeps ownership. The licensee gets a defined right to use, which can be narrow or broad, exclusive or non-exclusive, for a fixed term or perpetual. Unlike a SaaS subscription, a licence usually involves the licensee installing or holding a copy of the software, so the agreement must be precise about what the licensee may and may not do with that copy. In Malaysia the agreement sits on two legal foundations: copyright law, which is what gives the licensor something to license, and the general law of contract under the Contracts Act 1950 (Act 136). This page explains how to build a clear software licence for a Malaysian licensor or licensee. It is general information, not legal advice. ## The legal basis: copyright in software In Malaysia, computer programs are protected as literary works under the Copyright Act 1987. Protection arises automatically when the work is created and fixed; there is no registration requirement, though a voluntary notification system exists to help prove ownership. Because the owner holds the exclusive rights to reproduce, distribute and adapt the software, any use by another party needs a licence. The licence is the legal permission; the agreement is the document that defines and limits it. Two consequences follow. First, a licence should be granted expressly and precisely, because anything not granted stays with the owner. Second, where the software is developed for a customer, ownership of the new code depends on the contract and the employment or commissioning position, so the agreement should say clearly who owns what. ## Is a software license agreement binding in Malaysia? Yes, when the Contracts Act 1950 requirements are met: offer, acceptance, consideration, capacity, free consent and a lawful object. Licences accepted electronically, including click-wrap and shrink-wrap style terms, are valid, supported by the Electronic Commerce Act 2006 and the Digital Signature Act 1997, provided acceptance is a clear act and the terms are available before the licensee commits. ## Key clauses in a Malaysian software license agreement ### The licence grant This is the core clause. Define precisely: what software (including version and modules), the scope (install, use, copy for backup), the model (per user, per device, per site, enterprise), whether it is exclusive or non-exclusive, the territory, and the term (fixed, renewable or perpetual). State whether the licensee may sublicense or assign, which is usually not permitted without consent. ### Restrictions Set out what the licensee may not do: no copying beyond the licence, no reverse engineering (subject to any rights the law preserves), no removing proprietary notices, no use beyond the licensed scope, and no transfer to third parties. These restrictions are what keep the licence within its intended bounds. ### Intellectual property ownership Confirm the licensor owns all rights in the software and that the licence does not transfer ownership. If the licensee gets custom development or configuration, state who owns that new work. If the software includes open-source components, disclose them and flag that their own licence terms apply. ### Fees, payment and tax Set the licence fee, whether it is one-off or recurring, and the payment terms. On tax, note that service tax can apply to certain software supplied as a digital service, and from 1 March 2024 the service tax rate rose from 6 percent to 8 percent for most taxable services, including digital services. State whether fees are inclusive or exclusive of tax. A traditional perpetual licence of on-premise software may have a different tax treatment from a subscription-style digital service, so confirm the position for your specific supply. ### Maintenance, support and updates Say whether support, bug fixes and updates are included, charged separately, or excluded. Define response expectations and whether new versions are covered or require a new licence. ### Warranties and disclaimers Give a limited warranty that the software will perform materially in line with its documentation for a defined period, and that the licensor has the right to license it. Disclaim broad implied terms where the law allows. Avoid promising the software is error-free. ### Limitation of liability and indemnity Cap the licensor's liability, usually by reference to the fees paid, and carve out items that should not be capped such as an intellectual property infringement indemnity. The licensor commonly indemnifies the licensee if the software infringes a third party's intellectual property rights, with a right to repair, replace or refund. ### Term, termination and effect of termination Set the term and renewal. On termination, the licensee must stop using the software and, for non-perpetual licences, destroy or return copies and certify it has done so. For perpetual licences, say what survives. ### Governing law and disputes Choose Malaysian law where appropriate, and decide between the courts and arbitration for disputes. ## A simple software license agreement structure 1. Parties and definitions

2. Licence grant: scope, model, exclusivity, territory and term
3. Restrictions on use
4. Intellectual property ownership and open-source components
5. Fees, payment and tax
6. Maintenance, support and updates
7. Warranties and disclaimers
8. Limitation of liability and infringement indemnity
9. Confidentiality
10. Term, termination and effect of termination
11. Governing law (Malaysia) and dispute resolution
12. General: assignment, notices, entire agreement ## Common mistakes in Malaysian software licences - A vague licence grant that leaves the scope, user model and term unclear, which invites disputes about over-use.

• Silence on ownership of customisations or custom code, so both sides claim it.
• Ignoring open-source components and their own licence obligations.
• No infringement indemnity, leaving the licensee exposed if the software turns out to infringe.
• Treating the tax position as settled when a perpetual on-premise licence and a digital subscription can be taxed differently. ## Keeping software licences under control An organisation that licenses software, whether as licensor or licensee, quickly accumulates many agreements: different scopes, different renewal dates, different support terms, and the occasional perpetual licence buried among subscriptions. The hard part is not drafting one licence. It is drafting consistently, spotting the clause that granted more than intended, remembering renewals and support windows, and knowing which version is in force. That work is the same whether you hold five licences or fifty, and it is far easier when drafting, per-clause risk review, version history and renewal tracking live in one place rather than across folders and inboxes. A single AI contract workspace such as Adira is built around that idea. Adira is India-first today, with other jurisdictions including Malaysia on its roadmap, so for Malaysia-specific copyright and tax positions you would still confirm the detail with counsel. The point to take is the direction: licences you can rely on are the ones that stay in one place, consistent, with their scope and dates in view.