SaaS Agreement in Japan: Template, Key Clauses and Local Law (2026)

What law governs a SaaS agreement in Japan? Japan has no dedicated software-as-a-service statute. A SaaS contract is a commercial services agreement, and several general laws combine to govern it: - The Civil Code (Minpo) supplies the default rules on formation, performance and breach of a services contract, and the general duty of good faith. The 2020 Civil Code reform changed the rules on non-conformity and remedies, which affects warranty drafting.

• Consumer rules, principally the Consumer Contract Act and the Act on Specified Commercial Transactions, apply where the customer is a consumer, limiting unfair terms and adding disclosure duties.
• The Act on the Protection of Personal Information (APPI) applies wherever the service processes personal data, with rules on purpose of use, security, third-party provision and cross-border transfers, overseen by the Personal Information Protection Commission. Because the service is hosted and often delivered from outside Japan, data protection and the APPI cross-border transfer rules usually need the most attention. ## SaaS is a service, not a licence or a sale In SaaS the customer accesses a hosted service rather than receiving a copy of the software. That shapes the contract: - The provider grants a right to access and use the service for the term, not a perpetual licence.
• The provider keeps ownership of the software and platform.
• Availability, support and data handling are the real subject of the deal, so service levels and the data terms carry weight. ## Key clauses in a Japanese SaaS agreement ### Service description and access rights Define the service, the subscription, permitted users and usage limits, and state that this is access to a hosted service for the term, not a transfer of software. ### Fees, tax and invoicing Set fees, billing cycle, renewal pricing and late-payment terms, and address Japanese consumption tax, including the invoice-retention rules. ### Service levels and support Set uptime commitments, support response times, maintenance windows, and the remedy for missed levels (usually service credits) as the agreed remedy. ### Data protection and security This is central where personal data is processed. Address purpose of use, security measures, use of subcontractors, the rules on third-party provision of personal data, and APPI cross-border transfer safeguards. Make clear each party's role in handling personal data. ### Customer data ownership and return Confirm the customer's data remains the customer's, the provider processes it only to deliver the service, and set export and deletion on termination. ### Intellectual property Confirm the provider owns the platform and improvements, grant a limited right to use, and deal with ownership of configurations and feedback. ### Confidentiality Protect each side's confidential information, with carve-outs and survival. ### Warranties, liability and indemnities Give a service warranty consistent with the post-2020 Civil Code non-conformity rules, disclaim others to the extent allowed, cap liability and exclude indirect losses. Note the Consumer Contract Act voids clauses that wholly exclude a business's liability to a consumer, so consumer terms need care. ### Term, renewal, suspension and termination Set the term, auto-renewal and notice, suspension for non-payment, and data handling on exit. ### Governing law, language and disputes Parties may choose law and forum, though consumer rules can protect a Japanese consumer. Japan is a party to the New York Convention, so arbitration awards are generally enforceable. A Japanese version helps for consumer-facing terms and local enforcement. ## A clause-by-clause skeleton 1. Parties and definitions

2. Service description and access rights
3. Users, usage limits and acceptable use
4. Fees, consumption tax, invoicing and renewal pricing
5. Service levels, support and credits
6. Data protection and security (APPI)
7. Customer data: ownership, export and deletion
8. Intellectual property
9. Confidentiality
10. Warranties and disclaimers
11. Limitation of liability
12. Indemnities
13. Term, renewal, suspension and termination
14. Governing law, language and dispute resolution ## Common mistakes to avoid - Treating a SaaS deal as a software licence or sale, which misframes ownership and risk.

• Warranty wording that ignores the post-2020 Civil Code non-conformity and remedy rules.
• Thin data terms, especially on APPI third-party provision and cross-border transfer.
• Wholly excluding liability to a consumer, which the Consumer Contract Act will not enforce.
• An English-only contract for a service aimed at Japanese consumers. ## Managing SaaS contracts after signing A SaaS business runs on many similar subscription agreements, each with its own renewal date, price escalator, service-level commitment and data terms. Letting renewals auto-roll unnoticed, or losing track of which customer got which bespoke terms, is where margin and risk leak. Many teams keep the whole portfolio in one AI contract workspace: generate from a tuned template, see per-clause risk, make plain-English edits across documents, and get renewal and obligation alerts on a live timeline. Adira is built this way, India-first today, with non-India jurisdiction depth such as Japan on its roadmap, so treat the Japanese-law points here as a starting point to confirm with local counsel. This article is general information, not legal advice. Japanese civil, consumer and data-protection law change, and the right terms depend on your service and customers. Confirm the current law and get local advice before you sign.