---
title: "SaaS Agreement (Canada)"
url: "https://forms-legal.com/canada/business/intellectual-property/saas-agreement-canada"
description: "A SaaS Agreement in Canada sets the subscription, service levels, and data-protection terms for use of the software-as-a-service product, governed primarily by common-law contract principles and PIPEDA."
language: "en"
jurisdiction: "Canada"
category: "Business / Intellectual Property"
primaryStatute: "Common law of contract + PIPEDA"
dateModified: "2026-10-29"
maintainer: "Vladislav Sergienko, founder (not a lawyer)"
---

# SaaS Agreement (Canada)

- Canada · Business / Intellectual Property
- Legal basis: Common law of contract + PIPEDA

## What Is a SaaS Agreement (Canada)?

A SaaS Agreement in Canada sets the subscription, service levels, and data-protection terms for use of the software-as-a-service product, governed primarily by common-law contract principles and PIPEDA.

The legal framework for Canadian SaaS agreements is shaped by several federal and provincial statutes. The Personal Information Protection and Electronic Documents Act, S.C. 2000, c. 5 (PIPEDA) governs how the provider must handle, store, and protect any personal information contained within customer data. PIPEDA’s ten fair information principles (consent, accountability, purpose limitation, collection limitation, use limitation, accuracy, safeguards, openness, individual access, and challenging compliance) must be reflected in the agreement’s data processing provisions.

Canada’s Anti-Spam Legislation, S.C. 2010, c. 23 (CASL) applies to any commercial electronic messages sent through or in connection with the service. SaaS providers that send marketing emails, product updates, or promotional communications to Canadian users must comply with CASL’s requirements for express consent, sender identification, and functional unsubscribe mechanisms, with penalties of up to $10 million per violation for organizations.

Provincial Consumer Protection Acts, particularly Ontario’s Consumer Protection Act, 2002, impose requirements for subscription auto-renewal, including clear disclosure of renewal terms, advance notice of renewal, and the ability for the consumer to cancel at any time. SaaS providers serving Canadian consumers must confirm their subscription billing practices comply with these provincial requirements.

The Copyright Act, R.S.C. 1985, c. C-42 and the Trademarks Act, R.S.C. 1985, c. T-13 govern the intellectual property provisions of the agreement, confirming that the provider retains ownership of the software while granting the customer a limited licence to use it. Customer data ownership, by contrast, remains with the customer, and the provider’s right to process that data is limited to providing the contracted service.

## When Do You Need a SaaS Agreement (Canada)?

When a Canadian software company is launching a cloud-based application and needs a formal agreement to govern customer subscriptions, including pricing, access rights, data handling, and support obligations.

When a business is subscribing to a SaaS platform for CRM, project management, accounting, HR, e-commerce, or other business functions and needs a clear contract defining the service scope, data ownership, security requirements, and termination rights.

When a SaaS provider handles personal information of Canadian individuals (employees, customers, patients, students) and must confirm its agreement complies with PIPEDA’s privacy requirements, including consent, purpose limitation, security safeguards, and mandatory breach notification.

When a SaaS provider offers subscription auto-renewal and needs to comply with provincial Consumer Protection Acts that require clear disclosure, advance notice, and the ability for customers to cancel without penalty.

When a customer requires specific data residency commitments, confirming that customer data is stored and processed exclusively within Canadian borders or within specified jurisdictions, with appropriate safeguards for any cross-border data transfers.

When enterprise customers require service level commitments, including guaranteed uptime percentages, scheduled maintenance windows, support response times, and service credit remedies for downtime that exceeds the guaranteed thresholds.

Parties in Canada should prepare a SaaS Agreement (Canada) proactively rather than waiting for a dispute to arise.

## What to Include in Your SaaS Agreement (Canada)

Service Description and Access Rights — A clear definition of the software service, including its name, URL, functionality, and the scope of the Customer’s non-exclusive, non-transferable right to access and use the platform during the subscription term. Restrictions on use must be explicitly stated.

Subscription Terms and Pricing — The initial subscription term, recurring fees (in CAD, exclusive of GST/HST/PST/QST), billing frequency, payment terms, and provisions for fee increases upon renewal. Auto-renewal terms must comply with provincial Consumer Protection Acts.

Intellectual Property Ownership — A clear statement that the Provider retains all IP rights in the software under the Copyright Act and Trademarks Act, while the Customer retains ownership of all Customer Data, with the Provider receiving only a limited licence to process that data for service delivery.

PIPEDA Compliance — Data processing provisions that address PIPEDA’s ten fair information principles, including purpose limitation, consent, data minimization, security safeguards, and the Customer’s right to access and correct personal information processed through the service.

Data Residency and Security — Specification of where Customer Data will be stored (Canada only, Canada and US, or global), the encryption standards applied at rest and in transit, and the Provider’s obligation to implement administrative, physical, and technical safeguards.

Breach Notification — The Provider’s obligation to notify the Customer of any breach of security safeguards involving Customer Data within a specified timeframe, and to cooperate with breach reporting to the Office of the Privacy Commissioner of Canada and affected individuals.

Service Level Agreement — Uptime guarantees (e.g., 99.9%), scheduled maintenance windows, support response times for critical issues, and service credit remedies for downtime exceeding the guaranteed threshold.

CASL Compliance — The Provider’s obligation to comply with Canada’s Anti-Spam Legislation when sending any commercial electronic messages through or in connection with the service, including obtaining express consent and providing unsubscribe mechanisms.

Termination and Data Portability — Conditions for termination (convenience, material breach, insolvency), the Customer’s right to export data in a standard format, and the Provider’s obligation to securely delete all Customer Data within a defined period after termination.

## Sources & Citations

- [R.S.C. 1985, c. C-42](https://laws-lois.justice.gc.ca/eng/acts/C-42/)
- [R.S.C. 1985, c. T-13](https://laws-lois.justice.gc.ca/eng/acts/T-13/)

## Frequently Asked Questions

### What is PIPEDA and how does it affect a SaaS agreement?

The Personal Information Protection and Electronic Documents Act (PIPEDA, S.C. 2000, c. 5) is Canada's federal privacy law governing how private-sector organizations collect, use, and disclose personal information during commercial activities. Under Section 5 of PIPEDA, organizations must comply with the ten fair information principles in Schedule 1, including accountability, consent, limiting collection, and safeguards. A SaaS agreement must address PIPEDA compliance by specifying how customer data is collected, stored, processed, and protected. Under Section 10.1 of PIPEDA (added by the Digital Privacy Act, S.C. 2015, c. 32), SaaS providers must report security breaches that create a real risk of significant harm to the Office of the Privacy Commissioner of Canada (OPC) and notify affected individuals. In British Columbia, the Personal Information Protection Act (PIPA, SBC 2003, c. 63) applies to provincially regulated SaaS customers — Section 6 of PIPA governs consent. In Alberta, the Personal Information Protection Act (SA 2003, c. P-6.5) applies. In Quebec, Law 25 (Act to modernize legislative provisions respecting the protection of personal information, S.Q. 2021, c. 25, amending the Act respecting the protection of personal information in the private sector, CQLR c. P-39.1) imposes additional obligations beyond PIPEDA, including mandatory privacy impact assessments before transferring personal data outside Quebec under Section 70.1 and the right to data portability under Section 27. SaaS agreements serving Quebec customers must specifically address Loi 25 compliance.

### What is CASL and why is it included in a SaaS agreement?

Canada's Anti-Spam Legislation (CASL, S.C. 2010, c. 23) regulates the sending of commercial electronic messages (CEMs) to electronic addresses of recipients located in Canada. Under Section 6 of CASL, a SaaS provider must not send a CEM unless the recipient has given express or implied consent, the message identifies the sender, and the message includes a functional unsubscribe mechanism that the recipient can use within 10 business days. Express consent requires a clear positive opt-in action by the recipient. Implied consent exists under Section 10(9) of CASL where the recipient has an existing business relationship with the sender within the prior 24 months. Under Section 20 of CASL, violations by organizations can result in administrative monetary penalties of up to $10 million per violation, and individuals can face penalties of up to $1 million per violation, enforced by the Canadian Radio-television and Telecommunications Commission (CRTC). SaaS agreements should specify that the customer is responsible for obtaining CASL-compliant consent from their own end users before sending CEMs through the platform, indemnifying the SaaS provider against CASL liability arising from the customer's use.

### What are the data breach notification requirements under PIPEDA?

Under Section 10.1 of the Personal Information Protection and Electronic Documents Act (PIPEDA, S.C. 2000, c. 5), as amended by the Digital Privacy Act (S.C. 2015, c. 32), organizations must report to the Office of the Privacy Commissioner of Canada (OPC) any breach of security safeguards involving personal information that creates a real risk of significant harm to an individual. The breach report must be made as soon as feasible after the organization determines that the breach has occurred. Under Section 10.3 of PIPEDA, organizations must also notify affected individuals as soon as feasible. The Breach of Security Safeguards Regulations (SOR/2018-64) require organizations to maintain a record of every breach for a minimum of 24 months and to provide those records to the OPC upon request. In Quebec, Section 3.5 of the Act respecting the protection of personal information in the private sector (LPRPSP, CQLR c. P-39.1), as amended by Law 25, requires that confidentiality incident reports be made to the Commission d'accès à l'information du Québec (CAI) and affected persons within 72 hours when there is a risk of serious injury. In British Columbia, Section 34.1 of the Personal Information Protection Act (PIPA, SBC 2003, c. 63) imposes similar mandatory breach reporting obligations to the BC Information and Privacy Commissioner. SaaS agreements must allocate breach notification responsibilities between the provider and customer.

### Can a SaaS agreement include auto-renewal in Canada?

Yes, Canadian SaaS agreements may include automatic renewal provisions, but provincial consumer protection legislation imposes disclosure and cancellation requirements. In Ontario, Section 27 of the Consumer Protection Act, 2002 (S.O. 2002, c. 30, Sched. A) requires that internet agreements and remote agreements — which include SaaS subscriptions — clearly disclose material terms including automatic renewal provisions before the consumer is bound. Under Section 45 of the Consumer Protection Act, 2002, the consumer has the right to cancel a subscription agreement that is for an indefinite period, and the supplier must provide a full refund of amounts paid for goods or services not yet received. In British Columbia, the Business Practices and Consumer Protection Act (SBC 2004, c. 2) governs the disclosure of renewal terms in subscription agreements. Section 19 of that Act prohibits deceptive acts or practices, including failing to clearly disclose auto-renewal terms. In Quebec, the Act respecting consumer protection (RLRQ, c. P-40.1) requires contracts concluded by technological means to clearly indicate renewal terms. The Office de la protection du consommateur du Québec (OPC Québec) enforces these requirements. For B2B SaaS, consumer protection legislation typically does not apply, but common law still governs. SaaS agreements should include a 30-60 day renewal notice and cancellation window.

### Where must customer data be stored under Canadian law?

The Personal Information Protection and Electronic Documents Act (PIPEDA, S.C. 2000, c. 5) does not prohibit cross-border transfers of personal information, but under Schedule 1, Section 4.1.3, organizations remain accountable for personal information transferred to a third party for processing, even if the third party is located outside Canada. The SaaS agreement should clearly specify data residency options — Canadian-only servers, US servers with Standard Contractual Clauses, or global infrastructure — and require sub-processors to maintain equivalent privacy protections. In Quebec, Section 70.1 of the Act respecting the protection of personal information in the private sector (LPRPSP, CQLR c. P-39.1), as amended by Law 25 (S.Q. 2021, c. 25), requires a privacy impact assessment (PIA) before transferring personal information outside Quebec, and the transfer must be authorized by a written agreement that includes privacy protections. Quebec-based SaaS customers whose data is stored outside Quebec must comply with these requirements. In British Columbia, Section 33.1 of PIPA (SBC 2003, c. 63) limits transfers outside Canada unless consented to. OSFI Guideline B-10 imposes data residency obligations for federally regulated financial institutions.

### Are SaaS subscription fees subject to GST/HST in Canada?

Yes. Cloud-based software subscriptions are taxable supplies under the Excise Tax Act (R.S.C. 1985, c. E-15). Canadian SaaS providers registered for GST/HST under Section 240 of the Excise Tax Act must charge GST/HST on subscriptions sold to Canadian-resident customers. The applicable rate depends on the customer's province of residence: 5% GST in Alberta, Manitoba, Saskatchewan, British Columbia, and the territories; 13% HST in Ontario; 15% HST in Nova Scotia, New Brunswick, Prince Edward Island, and Newfoundland and Labrador; 5% GST + 9.975% QST (totalling 14.975%) in Quebec under the Act respecting the Quebec sales tax (RLRQ, c. T-0.1); and 5% GST + 6% PST in British Columbia under the Provincial Sales Tax Act (SBC 2012, c. 35). Non-resident SaaS providers that make taxable supplies to Canadian consumers may be required to register under the simplified GST/HST registration framework for non-residents introduced in 2021 under amendments to the Excise Tax Act — businesses with annual revenues exceeding CAD $30,000 from Canadian digital services must register. SaaS providers may claim input tax credits (ITCs) under Section 169 of the Excise Tax Act for GST/HST paid on business expenses related to the SaaS service. CRA GST/HST Info Sheet GI-150 provides guidance on digital services.

Fillable version (PDF or Word): [Download the free template](https://forms-legal.com/canada/business/intellectual-property/saas-agreement-canada)

General information, not legal advice — see our [accuracy & editorial policy](https://forms-legal.com/accuracy-policy). Confirm the cited law is current before relying on it.
