Free SaaS Agreement Template for India (2026)

Why SaaS contracts need different drafting from generic vendor agreements

A SaaS agreement is not a vendor agreement with software-flavoured clauses. The drafting starts from a fundamentally different commercial posture: the buyer is not procuring deliverables, the buyer is subscribing to a continuously-evolving service. That changes everything downstream. Acceptance criteria don't apply because there's nothing to accept. Implied warranties of merchantability and fitness for purpose look strange against software the vendor is updating weekly. Termination for convenience runs into the practical reality that the buyer's data, configurations, and integrations are all locked into the vendor's cloud.

Indian SaaS agreements layer on additional complexity that doesn't apply to a generic vendor agreement:

1. Copyright Act, 1957 framing — SaaS access is a non-exclusive licence under Section 14 of the Copyright Act. The template uses licence language explicitly, not "sale" or "delivery."
2. OIDAR and GST treatment — 18% GST applies, and cross-border SaaS sales trigger reverse-charge obligations on the Indian buyer.
3. DPDP processor framework — most SaaS engagements involve processing personal data, making the DPDP compliance guide directly applicable.
4. Data residency and cross-border transfer — Section 16 of the DPDP Act and sectoral RBI directions (for fintech) limit where buyer data can be stored.
5. IT Act Section 79 safe harbour — limits SaaS provider liability for user-generated content if the provider acts as an intermediary. The template preserves this defence where applicable.

This template is built around those five Indian-law-specific anchors.

What this template covers

The agreement is structured as a master subscription agreement with an Order Form for each subscription. Operative clauses include:

• Licence grant — non-exclusive, non-transferable, time-limited licence to access the service, drafted as a copyright licence under Copyright Act, 1957 § 14Section 14 defines copyright as the exclusive right to do specified acts in respect of a work; a licence under Section 30 permits the licensee to do those acts subject to the licence terms..
• Order Form — captures subscription tier, user count, contract term, pricing, and any negotiated deviations from the master.
• Service Levels — 99.9% uptime, defined exclusions (scheduled maintenance, force majeure, customer-caused outages), and service credits as the sole financial remedy short of termination.
• Customer data ownership — customer retains title to all customer data; provider has only the licence necessary to provide the service.
• Acceptable use policy — incorporated by reference, with the right to suspend for material breach (security, fraud, illegal content).
• Confidentiality — mutual, with 3-year survival and a perpetual carve-out for trade secrets. Drafted to align with the Indian NDA template for consistency across the customer relationship.
• Pricing and payment — annual or monthly billing, with auto-renewal default and CPI-capped price escalation.
• Indemnification — provider indemnifies for IP infringement; customer indemnifies for unlawful use. Both subject to the limitation of liability with carve-outs.
• Limitation of liability — capped at 12 months of fees with the standard exceptions (IP, confidentiality, gross negligence, DPDP).
• Term and termination — initial term, auto-renewal, termination for convenience (typically not allowed during initial term), termination for material breach, and post-termination data export.
• Dispute resolution — institutional arbitration seated in India (default Bengaluru, MCIA or DIAC).

Service Levels: the clause that gets renegotiated most

Every Indian SaaS deal of meaningful size renegotiates the SLA. The template's default 99.9% monthly uptime translates to 43.2 minutes of permitted downtime per month — a number Indian SaaS providers can typically meet on AWS or Azure infrastructure but that gets uncomfortable for self-hosted or hybrid deployments.

The Provider shall use commercially reasonable efforts to make the Service available 99.9% of the time during each calendar month, measured by the Provider's monitoring systems and excluding (i) Scheduled Maintenance announced at least 48 hours in advance, (ii) Force Majeure events under Clause 18, (iii) outages caused by the Customer's act or omission, and (iv) outages of third-party services not under the Provider's reasonable control. If the Provider fails to meet the foregoing in any calendar month, the Customer's sole and exclusive remedy shall be a Service Credit calculated under Schedule B.

The market-standard service credit ladder is:

Three commercial points buyers should push for:

1. Aggregate annual cap on credits: providers often try to cap credits at 30% of monthly fees with no annual aggregation. Insist on annual aggregation so persistent monthly underperformance translates into meaningful credit.
2. Termination right at sustained underperformance: three consecutive months below 99% should trigger a termination right with prorated refund of pre-paid fees.
3. API and integration uptime: if you depend on the provider's API, measure that separately from the web UI. Most SaaS providers measure only UI uptime by default.

Data processing: the DPDP overlay

For most B2B SaaS engagements, the provider is a data processor and the customer is the data fiduciary under Digital Personal Data Protection Act, 2023 § 8Section 8(5) requires the data fiduciary to enter into a valid contract with the data processor obligating the processor to process personal data only on the fiduciary's instructions and in accordance with reasonable security safeguards.. The template's Schedule C operationalises this with eight obligations:

For SaaS targeting Indian financial-services customers (banks, NBFCs, payment aggregators), Schedule C must additionally comply with the RBI Master Direction on IT Outsourcing and the RBI Storage of Payment System Data circular. The template flags these sectoral overlays in the commentary but does not embed RBI-specific language by default — it varies too much by sub-sector.

Auto-renewal and price escalation: the commercial guardrails

Indian B2B SaaS contracts almost always auto-renew. The template's default is 12-month auto-renewal with two important guardrails:

• 30-day opt-out notice: customer can prevent renewal by giving notice 30 days before the end of the current term.
• Price escalation cap: renewal pricing is the lower of (a) the current price plus CPI inflation as published by the Reserve Bank of India, or (b) 5% over the current price.

Vendors push back on the price cap. Buyers should hold the line — without a cap, a multi-year SaaS subscription becomes a vendor option to extract arbitrary price increases at renewal. The market-clearing position for mid-market Indian SaaS is CPI+3%, and the template uses the lower-of construction to give buyers price certainty.

Drafting note: If the customer is a public-sector entity or a regulated financial institution, multi-year auto-renewal may run into internal procurement policies that require fresh tendering after a defined term. Insert an explicit termination-at-renewal right and avoid language suggesting irrevocable extension.

IP: the common drafting mistake

A frequent error in Indian SaaS templates copied from US precedents is treating the entire service as the customer's "deliverable." It isn't. The customer never owns the SaaS; the customer has a licence to access it. The template makes this explicit:

• Provider owns the SaaS, all updates, all aggregated and anonymised data, all platform IP.
• Customer owns customer data and any customer-specific configurations.
• Customer grants the provider a non-exclusive licence to use customer data only to provide the service.
• Provider may use aggregated and anonymised statistics for benchmarks and product improvement, subject to DPDP compliance.

This four-way IP carve-up is the standard market position for Indian B2B SaaS and consistent with the

Copyright Act, 1957 § 30Section 30 permits the owner of copyright to grant a licence to do any of the acts in respect of which the owner has the exclusive right under Section 14, subject to the terms of the licence.

licence framework.

GST and cross-border invoicing

For India-based SaaS providers selling to Indian customers, the agreement should be priced plus GST at applicable rates rather than inclusive, to avoid disputes when GST rates change. Current rate: 18% on B2B SaaS. The template's pricing clause uses the standard "all amounts exclusive of GST and other applicable taxes" formula.

For cross-border SaaS:

• Indian provider selling to foreign customer: zero-rated supply under GST if export of services qualifies under Section 2(6) of the IGST Act. Requires LUT or refund route for input tax credit.
• Foreign provider selling to Indian B2B customer: reverse-charge applies; the Indian customer self-assesses and pays 18% GST.
• Foreign provider selling to Indian B2C customer: simplified OIDAR registration required if cross-border supply exceeds prescribed thresholds.

The template includes a tax clause that addresses each of these scenarios and a withholding-tax fallback under Section 195 of the Income Tax Act, 1961 for cross-border payments.

Termination and data export

The single most-disputed clause in Indian SaaS terminations is data export. The template uses the same three-tier transition framework as the vendor agreement template, adapted for SaaS:

1. Self-service export: customer has the right at any time during the term to export customer data via the Service's standard export functionality.
2. Termination assistance: for 60 days post-termination, provider continues to make customer data available for export at no additional cost.
3. Provider-assisted export: provider provides reasonable cooperation for additional formats or one-time bulk exports at the provider's then-current professional services rates.

The template specifies the export formats: machine-readable, non- proprietary (CSV, JSON, or industry-standard equivalent). Without this specificity, terminating customers have been forced to pay for proprietary export tools.

What this template does not cover

A few SaaS engagements need bespoke drafting beyond this template:

• B2C SaaS click-through terms — these are unilateral terms of service, not negotiated agreements. Use the template's substantive clauses but adapt the structure for click-acceptance.
• Payment aggregator and BFSI-regulated SaaS — needs RBI Master Direction overlays. The template's DPA is a starting point, but the IT Outsourcing and Payment Storage circulars require specific contractual language.
• Free trial and freemium tiers — the template assumes a paid subscription. Free tiers need different liability and SLA framing.
• Reseller and channel partner SaaS — three-party arrangements need flow-down provisions and back-to-back commercial terms.

How Clauseium accelerates SaaS agreement review

Clauseium's clause comparison engine matches incoming SaaS redlines against the standard Indian-market positions captured in this template. For an in-house counsel reviewing 20 customer-paper SaaS agreements per quarter, that turns each review from 90 minutes of clause-by-clause comparison into a 15-minute exception triage.

Try Clauseium free →

Final checklist before signing

Before issuing the SaaS agreement to a customer (or accepting a customer's paper), verify:

1. The Order Form is fully populated — subscription tier, user count, term, pricing, billing frequency.
2. The Service Description (Schedule A) accurately describes the service as of contract date.
3. The Service Levels (Schedule B) match the customer's commercial expectations and your operational capability.
4. The Data Processing Schedule (Schedule C) is retained or expressly waived in writing.
5. GST is "plus" not "inclusive," with a withholding-tax fallback for cross-border payments.
6. The auto-renewal and price-escalation guardrails are calibrated to your commercial preference.
7. The arbitration seat, institution, and rules are filled in.
8. Both signatories have authority — board resolution for companies; LLP designated partner for LLPs.

Get these eight things right, and a SaaS agreement closes in three days. Get them wrong, and the renewal cycle becomes a re-negotiation cycle.