A SaaS agreement, or software as a service agreement, is a contract under which a software provider gives a customer access to software, usually for a recurring subscription fee. Because the customer accesses the software rather than owning a copy, a SaaS agreement is structured around a right to access and use the service, not a transfer of the software itself. A SaaS agreement sets out important terms including license terms, fees, data handling, intellectual property, and liability that governs the relationship. A well-drafted SaaS agreement protects the provider’s software and revenue while giving the customer the certainty it needs to rely on the service.
Defining the subscription and the right to access. A SaaS agreement establishes that the customer receives a limited right to access and use the hosted service, not ownership of the software. It records the subscription term, renewal and cancellation terms, usage limits, and the consequences of exceeding them, which protects the provider’s recurring revenue and its software.
Setting service levels and availability. A SaaS agreement can set out uptime commitments, support response times, maintenance windows, and the remedies available if the service falls short, often through a service level agreement. Clear service level terms manage customer expectations and cap the provider’s exposure when the service is unavailable.
Allocating data protection responsibilities. A SaaS provider processes the customer’s data, which engages Alberta’s Personal Information Protection Act and the federal Personal Information Protection and Electronic Documents Act where personal information is involved. A SaaS agreement addresses data ownership, security, breach notification, and the use of sub-processors, frequently alongside a separate data processing agreement.
Protecting intellectual property and confidential information and data. A SaaS agreement confirms that the provider retains ownership of the software, while addressing ownership of customer data and any data the provider generates from use of the service. It also protects the confidential information and data each party discloses, which is central to a software business.
Limiting liability and managing risk. A SaaS agreement allocates risk through terms like warranty disclaimers, limitation of liability clauses, indemnities, and terms addressing service suspensions and downtime. These terms are among the most negotiated in any SaaS agreement and shape each party’s exposure when something goes wrong.
Electronic Transactions Act, SA 2001, c E-5.5. Alberta’s legislation recognizing the validity of electronic contracts and signatures, which supports the click-through and online acceptance methods commonly used to form a SaaS agreement.
Personal Information Protection Act, SA 2003, c P-6.5. Alberta’s private-sector privacy legislation, which applies where a SaaS provider or its customer collects, uses, or discloses personal information through the service, and informs the data protection terms of a SaaS agreement.
Personal Information Protection and Electronic Documents Act, SC 2000, c 5. Canada’s federal private-sector privacy legislation, which applies to personal information collected through a SaaS service in the course of commercial activity, particularly where data crosses provincial or national borders.
Consumer Protection Act, RSA 2000, c C-26.3. Alberta’s consumer protection legislation, which can apply to SaaS offered to consumers rather than businesses, and which regulates matters such as automatic renewals, cancellation rights, and unfair practices.
Automatic renewal and termination. SaaS agreements commonly renew automatically, and disputes arise over notice periods, mid-term cancellation, fee increases on renewal, and the parties’ obligations after termination.
Treating SaaS like a software licence. A common issue is using a traditional software licence agreement for a hosted service. SaaS is delivered as access to a service, not a copy of software, so terms drafted for installed software — perpetual licences, copy restrictions, source code handling — often do not fit and can leave the actual subscription relationship undefined.
Data ownership and security. Customers often expect to own their data and to know how it is stored, secured, and returned or deleted when the SaaS agreement ends. Disputes arise where the SaaS agreement is silent on data ownership, breach notification, sub-processors, or the customer’s ability to export its data on termination.
Service levels and remedies. Uptime and support commitments mean little without defined remedies. A SaaS agreement that promises availability but does not specify how it is measured, what counts as excused downtime, or what the customer receives when commitments are missed tends to generate disputes.
Limitation of liability and indemnities. Limitation of liability and indemnity clauses are heavily negotiated and frequently litigated. Overbroad limits may be challenged, while inadequate ones can expose a provider to claims far exceeding subscription revenue. The interaction between these clauses, service credits, and insurance is a recurring source of difficulty.
Can I get out of my SaaS agreement? Whether a customer can exit a SaaS agreement before the end of the term depends on its terms. Some agreements allow termination for convenience on notice, while others lock the customer in for the full subscription term and permit termination only for cause, such as the provider’s uncured breach or insolvency. The available exit routes, notice periods, early-termination fees, and any refund of prepaid fees are generally governed by the termination provisions of the SaaS agreement, subject to applicable legal protections in legislation including the Consumer Protection Act.
What is the difference between a SaaS agreement and a software licence? A software licence grants the right to use a copy of software, often installed on the user’s own systems. A SaaS agreement grants access to software hosted and operated by the provider, delivered over the internet as a service. The provider retains and runs the software, and the customer subscribes to use it.
Does a SaaS agreement need a separate data processing agreement? Not always, but a separate data processing agreement is common where the provider handles significant personal information on the customer’s behalf. The data terms can sit within the SaaS agreement or in a standalone data processing agreement referenced by it.
Can a SaaS agreement be formed by clicking “I agree”? Generally, yes. The Electronic Transactions Act supports the formation of contracts electronically.
Who owns the data in a SaaS arrangement? This is determined by the SaaS agreement. Customers typically retain ownership of the data they input, while providers often retain rights to aggregated or anonymized data and own the software and any improvements to it. Clear terms prevent disputes when the relationship ends.
This information is for education and entertainment purposes only. It is not intended to be legal, business, or other professional advice to be relied on. Do not make or refrain from any decisions on the basis of this information. Please contact us to receive advice from a qualified lawyer. View our Terms of Service for more information.