Data hosting in Canada: how to check that a provider is truly sovereign
A data centre in Montreal guarantees nothing if the owner answers to foreign law. Ten concrete checks before you hand your data to a hosting provider.
Alexandre Sauvageau, co-founder of Cogio

“Sovereign” is just a word
“Data hosted in Canada.” The line appears on almost every cloud provider’s website, the largest included. It is accurate, and it answers the wrong question. Knowing where the servers are tells you about data residency. Knowing which law applies to whoever controls them tells you about data sovereignty.
The Government of Canada makes the same distinction in its white paper on data sovereignty and public cloud. It states that as long as a cloud service provider operating in Canada is subject to the laws of a foreign country, Canada will not have full sovereignty over its data, and that data residency does not mitigate against the application of foreign laws, regardless of where the cloud resources are physically located.
A more recent paper prepared for the Treasury Board, reported by The Canadian Press in November 2025, goes further: storing data in Canada, or even using a Canadian supplier, would not guarantee that foreign courts would not have jurisdiction. Hence the need to check rather than trust a label.
An admission that made headlines
On June 10, 2025, before a French Senate inquiry on public procurement, Microsoft France’s legal director, Anton Carniaux, was asked whether he could guarantee that French citizens’ data hosted by Microsoft would never be handed to U.S. authorities without the agreement of French authorities. He answered that he could not guarantee it, while adding, according to published accounts, that no such request had occurred so far.
That answer says nothing bad about Microsoft: it is an honest description of U.S. law. Our article on the CLOUD Act explains why a U.S.-owned company must hand over data in its possession, custody or control, even when it is stored outside the United States. The federal white paper also names the U.S. Foreign Intelligence Surveillance Act (FISA) as the primary risk.
Ten checks before you sign
This is the list we use to assess a hosting provider. None of it requires a law degree. All of it requires answers in writing.
- 1. The ultimate parent company. Follow the ownership chain all the way up. A Canadian subsidiary of a U.S. company is still exposed to U.S. law. Corporate registries and annual reports often answer better than the “About us” page.
- 2. Operational control. Who runs the servers? A subsidiary that shares systems, management or staff with a foreign parent remains under its de facto control.
- 3. Subcontractors. Ask for the complete list: backups, monitoring, content delivery, ticketing tools. A Canadian host that sends its backups to a U.S. hyperscaler brings you right back to square one.
- 4. Support access. From where can support staff reach your data, and under what conditions? “Follow-the-sun, 24/7” support often means teams outside the country.
- 5. Encryption keys. Who holds them? If you manage your own keys, out of the provider’s reach, an order served on the provider can only produce unreadable data.
- 6. Notice of foreign requests. Does the contract require the provider to notify you of any foreign authority request, where the law allows, and to challenge it when it can be challenged?
- 7. Transparency report. Does the provider publish how many government requests it receives and what it did with them?
- 8. Certifications. An ISO 27001 certificate or a SOC 2 Type II report proves security discipline. They prove nothing about jurisdiction: those are two separate questions.
- 9. Exit. In what format do you get your data back at the end of the contract, how quickly, and is deletion confirmed in writing?
- 10. AI commitments. If the host also offers AI models, are your prompts used for training? Are they retained? Who processes them?
What Law 25 requires on your side
In Quebec, these checks are more than good practice. Before communicating personal information outside Quebec, section 17 of the Act respecting the protection of personal information in the private sector requires an assessment that considers, among other things, the legal framework in the destination state, and the communication must be governed by a written agreement.
Answers to the ten questions above are the raw material for that assessment, and for the privacy impact assessment required for any information system project involving personal information. A provider that cannot answer them in writing leaves you with an empty compliance file.
The tiers, from most to least sovereign
Once you have the answers, the ranking is straightforward. A server on your own premises remains the top tier. Next comes a Canadian-owned host running its own data centres in Quebec with no foreign subcontractor in the chain. A non-U.S. foreign host operating in Canada sits one step lower: outside U.S. jurisdiction, but outside Canadian jurisdiction too. The Canadian region of a U.S. hyperscaler offers residency, not sovereignty.
This ranking condemns no provider. For low-sensitivity data, a large provider’s Canadian region can be a reasonable, documented choice. For patient records, trade secrets or information protected by professional secrecy, the analysis changes.
How we work at Cogio
Our AI agents are hosted on the client’s premises or in the client’s region, with a provider whose ownership chain we have checked against the list above. That is what we mean by sovereign AI: a model and data that answer to a law you know, and written answers to prove it.
To see how we build these architectures, visit our home page or send us the list of your current providers: we will tell you which ones deserve a second look.
Frequently asked questions
Is a data centre in Quebec enough to be sovereign?
No. Location determines data residency. Sovereignty depends on the jurisdiction of the owner that controls the data: a foreign-owned company can be compelled by its home country’s law wherever its servers are.
Is a Canadian subsidiary of a U.S. company protected?
Not necessarily. If the parent controls the subsidiary or shares systems and staff with it, the data may be considered under the parent’s control for the purposes of U.S. law.
Does encryption solve the problem?
It reduces it a great deal if you hold the keys yourself, out of the provider’s reach. If the provider manages the keys, it can be compelled to decrypt.
Does ISO 27001 certification guarantee sovereignty?
No. ISO 27001 and SOC 2 attest to security practices, not to the jurisdiction that applies to the owner. Check both.
Does Law 25 prohibit U.S. providers?
No. It requires an assessment before any personal information is communicated outside Quebec, plus a written agreement. Exposure to foreign law belongs in that assessment.
Sources and references
- Government of Canada, White Paper: Data Sovereignty and Public Cloud
- The Canadian Press, paper prepared for the Treasury Board (November 3, 2025), via National Newswatch
- Microsoft France testimony before the French Senate (June 10, 2025), SDxCentral
- Act respecting the protection of personal information in the private sector, CQLR c. P-39.1, LégisQuébec
This article is a plain-language summary, accurate as of the date shown. It is not legal, tax or financial advice: for your own situation, consult a qualified professional.
Read next
Sovereignty
CLOUD Act: why a server in Montreal is not always sovereign
Read
Security
ISO 27001: what the certificate proves (and does not prove) about an AI vendor
Read
Compliance
The privacy impact assessment, demystified: how to assess an AI project before you deploy it
Read
A question about your own project?
The discovery call is free and takes half an hour. You leave with an honest read on your situation.
Let’s talk about your project