How to Review a Subscription Agreement (2026 Checklist)

A subscription agreement in the software world is the contract under which you pay to use a product (usually SaaS) over a period, rather than buying it outright. It bundles the commercial terms (what you get, what you pay, how long for) with the legal terms (data, security, liability, termination). Reviewing one well means watching the commercial mechanics that quietly lock you in or raise costs, and the data and liability terms that decide your exposure. Note this is a SaaS or services subscription, not a share subscription agreement, which is an investment document and a different animal. This is general guidance, not legal advice. ## The fast answer: what to check first Check four things first. The term and auto-renewal, including the notice you must give to stop it. The fees and how they can rise on renewal. What happens to your data on exit (can you get it out, and when is it deleted). The liability cap and what sits outside it. These are where subscription agreements most often bite. ## Clause-by-clause review checklist ### The subscription and what you are buying Confirm exactly what is included: the product, the edition or tier, the number of users or units, usage limits, and any add-ons. Check what happens if you exceed a limit (a block, an overage charge, or an automatic upgrade). Make sure the order form and the main terms agree on scope. ### Fees, increases and overages Identify the price, the billing cycle, and taxes. The key clause is how fees change: many agreements allow an increase on renewal, sometimes capped, sometimes not. Check the cap (a fixed percentage or an index) and the notice you get. Check overage pricing and whether unused capacity rolls over. ### Term, auto-renewal and cancellation This is the most common trap. Note the initial term, whether it auto-renews, and the notice period to prevent renewal (often 30 to 90 days before the term ends). A short window plus auto-renewal means a missed date commits you to another full term. In some markets auto-renewal is regulated and the vendor must remind you and make cancellation easy; check local rules. ### Service levels and support Look for an SLA: uptime commitment, how it is measured and excluded, support response times, and remedies (usually service credits). Check whether credits are the only remedy and whether chronic failure lets you leave. A subscription with no meaningful SLA leaves you with little recourse for downtime. ### Data ownership, use and AI training Confirm you keep ownership of your data and content. Check how the vendor may use it: to provide the service is expected; using it for its own analytics, product development or to train AI models should be clearly stated and, ideally, something you can opt out of. If the product uses AI, check what happens to your inputs and outputs. ### Security and data protection Check the security commitments (encryption, access control, certifications such as SOC 2 or ISO 27001 if claimed, with a date) and that a data processing agreement is attached if personal data is involved. Confirm breach-notification terms and, if relevant, where the data is hosted. ### Warranties and disclaimers Note any warranty that the service will perform as described, and how long it lasts, against the usual broad disclaimer of all other warranties. Beta or early-access features are often provided "as is"; check what you are relying on. ### Limitation of liability Check the cap (often fees paid in the prior 12 months), the exclusion of indirect and consequential loss, and the carve-outs (data breaches, IP indemnity, confidentiality). Weigh the cap against the harm an outage or data loss could cause your business. ### Suspension and termination Check when the vendor can suspend or terminate (non-payment, breach, acceptable-use violations) and whether you get notice and a chance to cure. Check your own rights to terminate, including for the vendor's material breach or a prolonged outage. ### Exit and data portability On termination, can you export your data, in what format, and for how long is it available before deletion? A short export window or a proprietary export format can trap your data. Check whether transition assistance is offered and what it costs. ### Acceptable use and changes to terms Read the acceptable-use policy for anything that could catch normal use. Check whether the vendor can change the terms or the service unilaterally, and whether you get notice and any right to object or leave if a change is material. ## Red flags to push back on Auto-renewal with a long notice period and no reminder. Uncapped price increases on renewal. Data used for AI training or resale with no opt-out. A short or proprietary data-export window on exit. A liability cap far below the harm an outage could cause. The vendor's right to change material terms at will with no exit right. ## How the law changes by jurisdiction Contract law is national, so the same words do not behave the same everywhere. In common-law systems (India, the UK, Singapore, Australia, the US) courts lean on the written terms and read ambiguity against the drafter. Governing-law and jurisdiction clauses decide which country's rules apply and where disputes are heard; check they match where the parties and the assets actually are. In India, stamp duty and, for many instruments, registration are live concerns, and the Indian Contract Act 1872 governs formation. In the US, state law varies and the Uniform Commercial Code may apply where goods are involved. Across the EU and UK, data and consumer rules add mandatory terms you cannot contract out of. When in doubt, take local advice; this page is general information, not legal advice. ## A simple review workflow Work the commercial lock-ins first (term, renewal, fee increases, exit), then the data and security terms, then liability and the SLA, then acceptable use and change rights. Line up the order form with the main terms so they do not conflict. Keep an issues list with clause reference, risk and proposed change, and diarise the renewal notice date the moment you sign. ## One workspace for drafting, review and tracking Everything above is work you can do by hand: read the draft, mark the risky positions, line up your redlines, remember the dates. The friction is rarely the reading. It is that the draft, the comments, the versions, the signed copy and the renewal date usually live in five different places. The simple idea behind an AI contract workspace is to keep that work together: draft from your own catalogue, see each clause flagged favourable, neutral or unfavourable to you, edit clauses in plain English and get a clean diff, keep a live activity timeline so every version is traceable, and track key dates and obligations so renewals and notices do not slip. Adira is one such workspace, built on Anthropic's Claude and tuned to how your company contracts. It is India-first today; deeper support for other jurisdictions and a single legal health pane (the Company Command Centre) are on the roadmap. None of that replaces legal advice on a specific deal. It just means the review you ran once does not have to be rebuilt from scratch next quarter.