Software License Agreement in Japan: 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 Japan 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 Japanese lawyer (bengoshi) before you sign. ## How is software protected and licensed in Japan? Software in Japan is protected as a copyright work. The Copyright Act lists computer programs among protected works and has specific provisions for them. Protection covers the expression of a program, not the algorithms or programming language as such, and Japanese courts have generally taken a measured approach to program copyright. Inventions implemented in software can also be patentable in some cases under the Patent Act, but copyright is the usual basis for a licence. What this means for a licence: - A licence, not a sale. The licensor keeps ownership of the copyright and grants a right to use, whose scope is set by the contract.

• Moral rights stay with the author. In Japan, authors keep moral rights even after assigning economic copyright, so a licence or assignment often includes a non-assertion undertaking.
• The contract is commercial. A B2B software licence is governed by the Civil Code (Minpo), reformed with effect from 1 April 2020, and the Commercial Code (Shoho). It can be signed electronically.
• Choice of law and language. Under the Act on General Rules for Application of Laws, parties to an international contract may generally choose the governing law. Japanese-language or bilingual contracts are common; name a controlling language.
• Tax. Japanese consumption tax (currently 10 percent) generally applies; cross-border licence fees can raise withholding questions.
• Data protection. If the software processes personal information, the APPI applies and a separate data agreement may be needed. ## Key clauses in a Japanese software license agreement - Grant and scope. Whether the licence is perpetual or for a term, exclusive or non-exclusive, and the permitted use (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 and moral rights. Confirm the licensor owns or may license the software, that the licensee gains no ownership, and address moral rights.
• Maintenance and support. Updates, patches, versions and support levels, often in a schedule.
• Fees. Licence fee, any subscription or maintenance fees, currency, consumption tax and invoicing.
• Warranties and non-conformity. That the software performs to its documentation, with remedies reflecting the reformed Civil Code's non-conformity rules.
• IP infringement indemnity. The licensor covers third party infringement claims, within agreed limits.
• Limitation of liability. A cap and exclusion of indirect damages, subject to limits (no exclusion for wilful misconduct or gross negligence).
• Confidentiality. Source code and know-how protection, also supported by the Unfair Competition Prevention Act for trade secrets.
• 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 and moral rights
6. Maintenance, support and updates
7. Fees, consumption tax and invoicing
8. Warranties and non-conformity
9. IP infringement indemnity
10. Limitation of liability
11. Confidentiality and source code
12. Audit rights
13. Data protection (where personal information is involved)
14. Term, termination and post-termination
15. Governing law, dispute resolution and language ## Common mistakes in Japanese software licenses - Treating the licence as a sale. A licence grants use and the licensor keeps the copyright; wording that sounds like a transfer of ownership confuses what the licensee received.

• Ignoring moral rights. Authors keep moral rights in Japan; without a non-assertion undertaking, a licensee or assignee can be exposed.
• Vague scope. Not stating users, machines, sites or environments leads to disputes and contentious audits.
• Using pre-2020 warranty concepts. The Civil Code reform replaced hidden-defect language with non-conformity; update the warranty and remedy clauses.
• Over-broad liability waivers. You cannot exclude liability for wilful misconduct or gross negligence.
• No controlling-language clause. For bilingual contracts, state which language governs. ## 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 the Copyright Act and the reformed Civil Code. 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 Japan-specific points with local counsel. ## FAQ