Data residency vs data sovereignty: where the disk is, and whose law reaches it.
Data residency is where your data is physically stored. Data sovereignty is which country’s law can compel access to it. A Canadian region of a US cloud gives you residency: the disks are in Canada, but the US CLOUD Act still reaches the provider. Sovereignty needs a provider that no foreign law can order to hand the data over.
Facts checked
The two definitions
The Government of Canada’s white paper on data sovereignty and public cloud uses short definitions. Data residency is “the physical or geographical location of an organization’s digital information.” Data sovereignty is “Canada’s right to control access to and disclosure of its digital information.”
The same paper then says the part most vendor pages leave out. Data residency “does not mitigate against the application of foreign laws”, and “as long as a CSP that operates in Canada is subject to the laws of a foreign country”, Canada “cannot ensure full sovereignty over its data”. That is the federal government describing its own cloud use, not a vendor’s pitch.
For a buyer, it helps to split the question in three: where the data is (location), which courts can order the provider to produce it (jurisdiction), and who runs the systems and holds the keys (operator). Residency answers only the first.
Location, jurisdiction, operator: the difference in one table
Each row is a common hosting setup. The last column is our reading of section 17 of Quebec’s private-sector privacy Act, for the hosting only; the Law 25 guide covers it in full.
| Setup | Location (residency) | Whose law can compel the provider | Who operates it | Law 25 s. 17 for the hosting |
|---|---|---|---|---|
| US-owned cloud, Montréal region † † | Quebec | Canadian and Quebec law, plus US law under 18 U.S.C. § 2713 | A US company | No, unless a backup or replica is kept outside Quebec |
| US-owned cloud, Toronto or Calgary region † † | Canada, outside Quebec | Canadian law, plus US law under § 2713 | A US company | Yes |
| Canadian-owned host with no foreign parent, servers in Ontario † | Canada, outside Quebec | Canadian law | A Canadian company | Yes: the line is Quebec, not Canada |
| Canner | Montréal, Quebec (data and backups) | Canadian and Quebec law; no US parent or affiliate | Canner, from Quebec | No |
| Any of the above, with backups copied to a US bucket † † | The copy is in the US | US law, for the copy | The bucket’s provider | Yes, for the copy |
† Competitor details come from each vendor’s own published pages on the dates shown; prices and plans change, so check the vendor before you decide. US-owned cloud, Montréal region (2026-10-29) · US-owned cloud, Montréal region (2026-10-29) · US-owned cloud, Toronto or Calgary region (2026-10-29) · US-owned cloud, Toronto or Calgary region (2026-10-29) · Canadian-owned host with no foreign parent, servers in Ontario (2026-10-29) · Any of the above, with backups copied to a US bucket (2026-10-29) · Any of the above, with backups copied to a US bucket (2026-10-29)
Why a Canadian region of a US cloud is residency without sovereignty
The US CLOUD Act added section 2713 to title 18 of the US Code in 2018. It says a provider of electronic communication or remote computing service must disclose data “within such provider’s possession, custody, or control, regardless of whether such communication, record, or other information is located within or outside of the United States.”
The test is control, not location. A US-incorporated cloud controls the disks in its Montréal region as much as the ones in Virginia, so picking ca-central-1 changes where the data sits and nothing about who can be ordered to produce it. That is our reading of the statute; it has not been tested in a Canadian case that we know of.
A treaty could change how those orders reach Canada. The US and Canada announced negotiations on a CLOUD Act agreement in March 2022. No agreement had been announced as of October 2026; the US Justice Department lists signed agreements with the UK and Australia only.
Data residency requirements in Canada
Most private businesses in Canada have no legal requirement to keep data in Canada. The rules that do require it bind governments: Nova Scotia’s public bodies and their service providers, and, as a strong preference, federal departments for Protected B and above. Quebec draws its line at the province and asks for an assessment, not a ban.
A residency requirement more often reaches a business through a contract. Public-sector customers pass their own rules down to suppliers, and health and financial clients often write a Canada-only clause into the agreement. Check your customer contracts as well as the statutes.
| Jurisdiction | Who it applies to | What it requires | Source |
|---|---|---|---|
| Federal, private sector † | Businesses under PIPEDA | No residency rule. Transfers abroad are allowed: the organization stays accountable, protects the data by contract and tells people it may be processed in another country | PIPEDA; OPC guidelines for processing personal data across borders |
| Federal government † | Federal departments | Computing facilities in Canada (or in a department’s premises abroad) must be “identified and evaluated as a principal delivery option” for Protected B, Protected C and classified data. A strong preference, not an outright ban | Directive on Service and Digital, 4.3.24 |
| Nova Scotia † | Public bodies, including municipalities, and their service providers | Personal information “stored only in Canada and accessed only in Canada”, unless the person consents, it is for a disclosure the Act allows, or the head of the public body allows it to meet the body’s operational needs (reported to the Minister each year) | Personal Information International Disclosure Protection Act, s. 5 |
| British Columbia † † | Public bodies | No storage-in-Canada rule since 2021 (former ss. 30.1–30.2 repealed). Disclosure outside Canada must follow the regulations; where sensitive personal information is stored outside Canada, the privacy impact assessment must include an extra assessment | Freedom of Information and Protection of Privacy Act, s. 33.1; B.C. Reg. 294/2021 |
| Quebec, private sector † | Enterprises | No residency rule. A privacy impact assessment and a written agreement before personal information is communicated outside Quebec; see the Law 25 guide | Act respecting the protection of personal information in the private sector, s. 17 |
| Quebec, public sector † | Public bodies | A privacy impact assessment before releasing personal information outside Quebec, “adequate protection”, and a written agreement, including when a body outside Quebec keeps the information on its behalf | Act respecting access to documents held by public bodies and the protection of personal information, s. 70.1 |
† Competitor details come from each vendor’s own published pages on the dates shown; prices and plans change, so check the vendor before you decide. Federal, private sector (2026-10-29) · Federal government (2026-11-10) · Nova Scotia (2026-11-10) · British Columbia (2026-10-29) · British Columbia (2026-11-10) · Quebec, private sector (2026-10-29) · Quebec, public sector (2026-11-10)
What residency alone still buys you
Residency is not worthless. It is necessary for sovereignty, and on its own it does a few real things:
- Quebec location takes section 17 off the hosting. A Montréal or Quebec City region, on any provider, means the hosting itself is not a communication outside Quebec. Backups and replicas elsewhere still count.
- It meets the federal “principal delivery option” for Protected B workloads, which is a location test, not an ownership test.
- Latency. A Montréal server answers users in Quebec and Ontario faster than one in Virginia or Oregon.
A buyer’s checklist
Ask each provider these questions in writing, and keep the answers with your privacy impact assessment.
- Where is every copy? The primary database, backups, replicas, logs, error reports and support exports. Residency claims often cover the first one only.
- Who owns the provider, all the way up? If a Canadian company has a US parent, ask whether the parent could be ordered to produce what the subsidiary holds. That is the question the “control” test in § 2713 raises.
- Where are support and operations staff? Whether remote access from outside Quebec is a communication outside Quebec has not been settled by the Commission d’accès à l’information. Record the answer either way.
- Which subprocessors touch your data, and what do they hold? Ask for the list and what each one sees. Canner’s: GloboTech for hosting (Montréal data centre), WHC and OVH (former hosts being wound down, now only forwarding traffic), Cloudflare for DNS records and certificates only (no traffic passes through it), Stripe for payments, Resend for account emails, GitHub when you connect a repository, Dynadot for domains you register through Canner, and Google or Microsoft if you sign in with them.
- Will they sign the contract section 18.3 requires? A written mandate with confidentiality measures, use only for the service, deletion at the end, and breach notice without delay.
- Where do your own integrations send data? Analytics, email, error tracking and AI APIs are often the copies that leave the country. They count as much as the host does.
- Can you leave? Standard Postgres dumps and S3-compatible storage make an exit plan real.
Where Canner sits, and where it doesn’t fit
Canner’s servers are in Montréal. Your apps, databases, files and their backups are stored there, the platform is operated from Quebec, and the company is Canadian-owned with no US parent. For your assessment, the Compliance add-on ($29/mo) adds a signed data processing agreement, a data-residency attestation and the organization audit log. See pricing.
Off-site backup copies go to a bucket you choose, so you decide whether that copy stays in Quebec (database docs).
Canner runs in one region with no automatic failover. If you need a second province for disaster recovery, or multi-region high availability, a hyperscaler’s Canadian regions do that and Canner does not. Do the section 17 assessment for the second region and weigh the US exposure in it.
Questions
What is the difference between data residency and data sovereignty?
Residency is where the data is physically stored. Sovereignty is whose law can compel access to it. Data in a Canadian data centre run by a US company has Canadian residency but stays within reach of US orders under the CLOUD Act.
Does the CLOUD Act apply to data in a Canadian AWS or Azure region?
On the text of 18 U.S.C. § 2713, yes. It covers data in the provider’s possession, custody or control “regardless of whether” it is inside or outside the United States. The Government of Canada’s own white paper reaches the same conclusion about foreign-law exposure.
Does Canadian law require data to be stored in Canada?
For most private businesses, no. PIPEDA allows transfers abroad with accountability, a contract and notice, and Quebec’s Law 25 requires an assessment and a written agreement before data leaves Quebec, without forbidding it. The binding rules are in the public sector: Nova Scotia requires its public bodies and their service providers to store and access personal information only in Canada, with exceptions, and federal departments must evaluate Canadian facilities as the principal option for Protected B and above. BC repealed its storage-in-Canada rule in 2021. Contracts with public-sector, health or financial clients often add a Canada-only clause.
Is there a CLOUD Act agreement between Canada and the US?
No. Negotiations were announced in March 2022, and no agreement had been announced as of October 2026. The US Justice Department lists agreements with the UK and Australia only.
What are the benefits of Canadian data residency?
Lower latency for Canadian users, a location that meets the federal principal-delivery-option test for Protected B, and, if the data is in Quebec, no section 17 assessment for the hosting itself. It does not remove foreign-law exposure if the provider is foreign-owned.
Related
- GuideQuebec Law 25: what the privacy law requires
- GuideLaw 25 for developers: privacy by default in code
- GuideQuebec’s digital sovereignty statement
- BlogCanada's AWS Alternative — By Accident
- BlogWhy We Moved Canner Off a Fleet of Virtualized Servers and Onto Our Own Hardware
- BlogHow to Build a 100% Canadian Stack
Residency and sovereignty, in one place.
Every Canner project runs in Montréal, on a Canadian-owned platform. Start free, add the Compliance add-on when you need the paperwork.