Sovereignty and compliance

Data residency and jurisdiction: what the CLOUD Act means for a data platform

The US CLOUD Act lets US authorities compel US-based providers to hand over data they control, wherever it is stored. A Canadian region of a US cloud therefore gives you Canadian residency, not Canadian sovereignty. To keep data under Canadian law, choose a provider and platform operator governed by Canadian law, and keep data, metadata and keys in Canada.

Published . Last updated

On this page

What is the CLOUD Act?

The Clarifying Lawful Overseas Use of Data Act is a US law passed in 2018. It followed a dispute over whether a US warrant could reach emails Microsoft stored in Ireland. The law answered yes: what matters is who controls the data, not where the server sits.

Does it apply only to one kind of provider?

The same logic applies to any provider subject to US jurisdiction, including companies headquartered elsewhere with significant US operations. That is why the question to ask is "which laws can compel my provider?", not "where is the data centre?".

What does this mean for Canadian organisations?

  • Banks, insurers and credit unions: customer and transaction data held by a US provider can be reached by US legal process.
  • Government and the public sector: Canada's sovereign cloud procurement asks for data processed and stored only in Canada.
  • Everyone using AI: prompts, outputs, embeddings and logs are data too. Where the model runs matters as much as where the tables sit.

How do you reduce the exposure?

  1. Run the data platform with a Canadian operator, on Canadian infrastructure.
  2. Keep metadata, catalog and the control plane in Canada, not just the storage.
  3. Hold your own encryption keys.
  4. Run AI models in Canada and keep prompts and logs there.

DataNature can run with all four in the jurisdiction you choose: on R2i Edwin in Canada, IBM Cloud in the United States, OVHcloud in Europe, your own cloud account or on-premises. See regions.

Is there another view?

Some analysts argue Canada does not need to own its cloud, only to control it through contracts, encryption and procurement rules. That debate is worth reading. Either way, the starting point is knowing which laws apply to your provider.

Sources

How does DataNature Atlas keep this secure and compliant?

Every rule in this article is enforced in one place, inside your jurisdiction. DataNature Atlas is the platform's governance module:

  • Knows your data: a catalog with automated PII detection and classification across Bronze, Silver and Gold.
  • Controls access: role-based grants plus attribute-based policies, row filters and column masks (null, redact, partial, hash, year only).
  • Governs AI: Voir agents are scoped principals; masks, row filters and PII guardrails apply to every tool call and answer.
  • Proves it: lineage from source to metric to decision, and an audit log of who or what accessed which data.
  • Stays local: Atlas runs inside your deployment, so policies, lineage and logs never leave your jurisdiction.

These controls support GDPR, PIPEDA, Quebec Law 25, CCPA, HIPAA and sector rules such as OSFI E-23. Read DataNature Atlas in depth or see security and compliance.

See it on your own data.

Book a demo

Demos and quotes are handled by Dlytica, the company behind DataNature.