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

A software license agreement is the contract by which the owner of software (the licensor) lets another party (the licensee) use it on agreed terms, without transferring ownership. It covers what the licensee may do with the software, for how long, on how many machines or users, and what it may not do. In Mexico this is a commercial contract built on top of copyright law, because that is how software is protected. This page is general information, not legal advice. Confirm the current position with a qualified Mexican lawyer before you sign. ## How is software protected and licensed in Mexico? Software in Mexico is protected as a copyright work. The Federal Law on Copyright (Ley Federal del Derecho de Autor) treats computer programs as protected works, with a dedicated chapter on computer programs and databases. Software as such is generally not a patentable invention, so copyright, not patents, is the main route. Trademarks and other industrial property sit under the separate Federal Law for the Protection of Industrial Property (Ley Federal de Proteccion a la Propiedad Industrial). What this means for a licence: - A licence, not a sale. The licensor keeps ownership of the copyright and grants a right to use. The scope of that right is whatever the contract says, within copyright limits.

• The contract is commercial. A B2B software licence is governed by the Commercial Code (Codigo de Comercio), with the Federal Civil Code (Codigo Civil Federal) filling gaps under Article 2 of the Commercial Code. It needs no notarisation and can be signed electronically.
• Choice of law and language. The parties' choice of governing law is generally respected. For enforcement before a Mexican court you will usually need a Spanish version or an official translation.
• Tax. IVA at 16 percent and CFDI invoicing generally apply; cross-border licence fees can raise withholding tax questions.
• Data protection. If the software processes personal data, the 2025 Federal Law on the Protection of Personal Data Held by Private Parties applies and a separate data agreement may be needed. ## Key clauses in a Mexican software license agreement - Grant and scope. Whether the licence is perpetual or for a term, exclusive or non-exclusive, and the permitted use (number of users, machines, sites, production versus test).
• Restrictions. No copying beyond the licence, no reverse engineering except where the law allows, no sublicensing or transfer without consent.
• Delivery and acceptance. How and when the software is delivered, and any acceptance testing.
• Intellectual property. Confirm the licensor owns or has the right to license the software, and that the licensee gains no ownership.
• Maintenance and support. Updates, patches, versions and support levels, often in a schedule.
• Fees. Licence fee, any subscription or maintenance fees, currency, IVA and invoicing.
• Warranties. That the software performs to its documentation, with a remedy for defects.
• IP infringement indemnity. The licensor covers third party claims that the software infringes, within agreed limits.
• Limitation of liability. A cap and exclusion of indirect damages, within Mexican limits (no exclusion for fraud or wilful misconduct).
• Confidentiality. Source code and know-how protection.
• Audit. The licensor's right to verify that use stays within the licence.
• Term, termination and effect. Grounds, and the duty to stop use and delete copies on termination.
• Governing law, forum and language. ## A simple software license skeleton you can adapt 1. Parties and definitions

2. Licence grant and scope
3. Restrictions on use
4. Delivery and acceptance
5. Intellectual property ownership
6. Maintenance, support and updates
7. Fees, IVA and invoicing
8. Warranties and disclaimers
9. IP infringement indemnity
10. Limitation of liability
11. Confidentiality and source code
12. Audit rights
13. Data protection (where personal data is involved)
14. Term, termination and post-termination
15. Governing law, dispute resolution and language ## Common mistakes in Mexican software licenses - Treating the licence as a sale. A licence grants use and the licensor keeps the copyright. Language that sounds like a transfer of ownership creates confusion over what the licensee actually received.

• Vague scope. Not stating users, machines, sites or environments leads to disputes about whether use is within the licence, and makes audits contentious.
• No IP warranty or indemnity. Licensees need comfort that the software does not infringe; licensors need to cap that exposure.
• Over-broad liability waivers. Mexican law does not allow excluding liability for fraud or wilful misconduct, and excessive caps can be read down.
• Ignoring data protection. If the software touches personal data, the 2025 data protection law and a data agreement may apply.
• English only. Harder to enforce in Mexico; agree a controlling language. ## Keeping your licences under control The hard part of software licensing is not the first signature. It is tracking which customer has which licence scope, watching renewal and maintenance dates, spotting a liability cap or restriction that drifted from your standard, and keeping terms aligned with copyright and data law. When this sits in scattered files, overuse and lapsed renewals go unnoticed. That is the work an AI contract workspace can hold in one place: draft from your approved licence template, see per-clause risk flagged against how your company contracts, edit terms in plain language, and keep a live timeline of scopes, renewals and obligations. Adira is one such workspace if you want to see the idea in practice. Its depth outside India is on the roadmap, so confirm Mexico-specific points with local counsel. ## FAQ