Skip to content
FortaRisks
Back to blogCompliance

Hosted in Canada: what it changes, and what it does not

November 17, 2026 · 5 min read

"Data hosted in Canada." The line sits on the trust page of most of your vendors. It sits on ours too. It reassures an executive committee, it ticks a box in a tender, and it answers exactly one question: where the disk is.

Our position: "hosted in Canada" is an address, not sovereignty. Residency says where your data sleeps. Sovereignty asks who can reach it, from where, and under which law. This is not an argument against residency: it changes real things, and we chose it for our customers. It is an argument against stopping there.

What residency really changes

The law that governs the disk. Data stored in Canada falls first under Canadian courts and statutes: a production order goes through a Canadian process, and your contract is argued here. That is concrete, and it is why the federal government directs its departments to evaluate computing facilities located in Canada as the principal option for sensitive electronic information, Protected B and above (status: confirmed, Directive on Service and Digital).

Part of your compliance. In Quebec, section 17 of the private sector privacy act, as amended by Law 25, requires a privacy impact assessment before personal information is communicated outside Quebec, or before someone outside Quebec is entrusted with holding or using it on your behalf, plus a written agreement that reflects the assessment. Mind the trap: "in Canada" is not "in Quebec". Hosting in Ontario is still a communication outside Quebec under section 17. Canadian residency makes the assessment lighter; it does not remove it.

The conversation during an incident. A provider whose team and data are in Canada knows your reporting obligations (Law 25, PIPEDA) and works in your time zone. No statute says so, but the first hour of an incident often turns on it.

What it does not change

The law your provider answers to. The US CLOUD Act of 2018 lets US authorities require a provider under their jurisdiction to disclose data in its possession, custody or control, whether or not that data is located in the United States (status: confirmed, text of the law). The law also gives providers grounds to challenge, and large providers publish transparency reports; the risk is neither zero nor certain. On 10 June 2025, under oath before a French Senate inquiry, Microsoft France's director of public and legal affairs was asked whether he could guarantee that French citizens' data entrusted to Microsoft would never be handed over to US authorities under an injunction without France's explicit consent. His answer: "No, I cannot guarantee it", adding that it had never happened (status: confirmed, Senate transcript, our translation). The Government of Canada says it in its own white paper on data sovereignty and public cloud: data residency does not mitigate against the application of foreign laws, and as long as a provider operating in Canada is subject to another country's law, Canada does not have full sovereignty over its data. The white paper gives the US Foreign Intelligence Surveillance Act (FISA) as an example, and notes that under some foreign laws, disclosure could take place without notice. Its more recent digital sovereignty framework goes further: it is impossible for the Government of Canada to reach complete digital sovereignty (status: confirmed, Government of Canada).

Support and admin access. The disk is in Canada; the engineer who logs in at 3 a.m. for a ticket may be elsewhere. "Follow the sun" support lets people see your data from other countries without a single byte officially moving.

Backups and disaster recovery. The primary region is Canadian; the failover region, the backup copies or long-term archives are not always. It is often in a technical annex, rarely in the contract.

Subprocessors. Your vendor hosts in Canada, but its transactional email service, its monitoring, its log management or its AI model provider may process your data elsewhere. We covered it for AI last week: hosting can be in Canada and inference in the United States. The Office of the Privacy Commissioner of Canada reminds organizations that they remain accountable for information handed to a third party, and that processing abroad exposes it to that country's laws.

This week's test: five questions, one vendor

Take the vendor that holds the most personal information about your customers. Ask, in writing:

  1. Backups: in which region are backups, disaster recovery and archives?
  2. Access: from which countries can your support and admin staff reach our data?
  3. Law: which foreign law is your parent company subject to, and how do you respond to a request from a foreign authority?
  4. Subprocessors: which subprocessors handle our data, and in which region each?
  5. Logs: where do logs, telemetry and data sent to an AI service go?

A vague answer on two questions or more: the missing clause is written notice before any change of region, subprocessor or country of access. And the section 17 assessment should rest on those answers, not only on the trust page.

What do you think?

Is "hosted in Canada" a real selection criterion for you, or a box you tick? Which of your vendors has ever given a clear answer on support access? Tell us in the comments.

Where FortaRisks fits

The free Law 25 readiness check places your compliance in a few minutes, communications outside Quebec included; the vendor security questionnaire asks each third party for its subprocessors and data location. Forta Compliance links your obligations to 40+ frameworks and to your evidence, and Forta Suppliers tracks your third parties by risk. Our data is hosted in Canada, and the five questions apply to us too: ask us.

Sources: Act respecting the protection of personal information in the private sector (CQLR, c. P-39.1), section 17 · Commission d'accès à l'information du Québec, privacy impact assessment guide (in French) · Government of Canada, white paper: data sovereignty and public cloud · Government of Canada, digital sovereignty: a framework to improve digital readiness · Office of the Privacy Commissioner of Canada, guidelines for processing personal data across borders · US Department of Justice, CLOUD Act resources · French Senate, inquiry on public procurement, hearing of Microsoft France, 10 June 2025 (in French)

Where do you stand?

Measure your gap in five minutes, free

Reading about a framework is one thing, knowing where you stand is another. Our self-assessments give you a score per domain and the gaps to close first: Law 25, NIS2, DORA, SOC 2, CPCSC.