SaaS Agreement in the Philippines: Template and Key Clauses (2026)

A SaaS agreement in the Philippines is the contract under which a provider gives a customer access to hosted software over the internet, usually on a subscription. The customer does not buy or install the software; it gets a right to use it as a service. This guide sets out a clause-by-clause skeleton, the the Philippines law points that matter (data protection, tax and consumer rules), and the common mistakes. This is general information, not legal advice. ## How a SaaS agreement differs from a licence A traditional software licence transfers a copy you install and run. A SaaS agreement grants access to software the provider hosts and operates. Because the data and the service sit with the provider, the contract has to deal with uptime, support, security, and what happens to the customer's data on exit. These are the clauses that matter most, more than the licence grant itself. ## Clause-by-clause skeleton 1. Parties and definitions. Provider, customer, the service, authorised users, and customer data. 2. Grant of access. A non-exclusive right to use the service for the subscription term, and any user or usage limits. 3. Subscription, fees and renewal. Plan, number of seats, price, billing cycle, auto-renewal and price-change notice. 4. Service levels. Uptime commitment, support response times, and any service credits if targets are missed. 5. Customer data and privacy. Who owns the data (the customer), how it is processed and protected, and a data-processing addendum where personal data is involved (see the law note below). 6. Security. Agreed controls, encryption, access management, and breach notification. 7. Acceptable use. What the customer and its users may not do with the service. 8. Intellectual property. The provider keeps the software IP; the customer keeps its data; feedback terms. 9. Warranties and disclaimers. Service warranty and the usual exclusions. 10. Liability. Caps (often tied to fees paid) and carve-outs for data breach, IP infringement and confidentiality. 11. Confidentiality. Protecting each side's non-public information. 12. Term and termination. Term, termination for cause, and suspension for non-payment. 13. Data export and deletion on exit. The customer gets its data back in a usable format, and the provider deletes it after a set period. This is the clause customers most often forget. 14. Governing law and disputes. Choice of the Philippines law and the forum. 15. Boilerplate. Notices, assignment, subprocessors, and changes to the service. ## Philippines-specific legal points - General contract law. Contracts in the Philippines are governed by the Civil Code of the Philippines (Republic Act No. 386), including the rules on consent, object, cause and obligations. <!-- [VERIFY] Civil Code (RA 386) relevant articles -->

• Data protection. Personal data is governed by the Data Privacy Act of 2012 (Republic Act No. 10173), enforced by the National Privacy Commission. Where the provider processes personal data for the customer, agree data-processing terms, security measures and breach notification that meet it. <!-- [VERIFY] Data Privacy Act (RA 10173) controller/processor obligations -->
• Electronic contracts. Online acceptance and electronic documents are recognised under the Electronic Commerce Act of 2000 (Republic Act No. 8792), so click-through SaaS terms can be valid. <!-- [VERIFY] E-Commerce Act (RA 8792) recognition of e-contracts -->
• Tax. Supplies and services can attract value-added tax and documentary stamp tax under the National Internal Revenue Code. State who bears VAT and confirm any documentary stamp tax with a local adviser. <!-- [VERIFY] VAT and documentary stamp tax applicability and rates -->
• Consumer rules. If the customer is a consumer rather than a business, consumer-protection rules may override some terms. <!-- [VERIFY] consumer protection application to SaaS --> ## Common mistakes - No data-processing terms where the provider handles personal data covered by the Data Privacy Act.
• No data export and deletion clause, so the customer cannot get its data back on exit.
• Uncapped liability, or a cap with no carve-out for data breach.
• Auto-renewal with no clear notice period or price-change warning.
• Treating a hosted service like a perpetual licence, so uptime and support are never agreed. ## One workspace instead of scattered files Drafting a contract like this is only the first step. It then has to be reviewed for risk, signed and stamped, tracked against its dates and obligations, and governed over its full life. In most companies that work is spread across email threads, a drive full of near-identical files, and a spreadsheet nobody fully trusts. The result is slow reviews and missed renewal and compliance dates. A better setup is to keep drafting, review, e-signing and e-stamping, tracking and governance in one AI workspace that is tuned to how your own company contracts, built on Claude. Adira is built around that idea, with public per-seat pricing and a 7-day free trial, India-first and global-capable. A single company command centre that shows every upcoming obligation in one view is on its roadmap. The point is not the tool. The point is that if your SaaS agreement lives in one connected place, you can actually see what you signed and what falls due, instead of hunting for it. The guidance above stands on its own. ## Bottom line A SaaS agreement is won or lost in the service levels, the security and data-protection terms, and the data export and deletion rights on exit, not in the licence grant. Make the data-processing terms match the Philippines privacy law, set a realistic liability cap with sensible carve-outs, and spell out what happens to the data when the subscription ends. Have a qualified local lawyer review anything material.