# Databricks and Snowflake in Canada: what their Canadian regions solve for sovereignty, and what they do not

> Databricks and Snowflake both run in Canadian cloud regions and offer real residency controls, including Canada Protected B options. That solves where data is stored and processed. It does not change who operates the service: both are US companies running on US hyperscalers, so US legal process can still reach them. For full sovereignty, Canadian organisations also need a Canadian operator.

Source: https://datanature.ai/blog/databricks-snowflake-canada-sovereignty
Publisher: Dlytica Inc. (DataNature is a Dlytica company)
Updated: 2026-11-05

## What do Databricks and Snowflake offer in Canada?

Both are serious about regulated customers, and both deserve credit for it.

- **Databricks** runs in Canadian regions on AWS and Azure. Its classic compute plane runs in the customer's own cloud account in the region they choose. Databricks groups regions into "Geos"; the Americas Geo includes the United States, Brazil and Canada, and some AI features can process data anywhere in the Geo unless an administrator enforces processing within the workspace's own geography. Databricks also documents Canada Protected B compliance controls, which require the compliance security profile.
- **Snowflake** runs in Canadian regions on AWS and Azure and has completed the Canadian Centre for Cyber Security Protected B assessment on both. Snowflake publishes a law enforcement requests policy and transparency reports, redirects government requests to customers, supports Iceberg tables in customer-owned storage and offers customer-held encryption keys.

## What does that solve?

**Residency.** Data can be stored and processed in Canada. With the right settings, compute stays in the chosen region, and Protected B controls are available for government workloads.

## What does it not solve?

**Jurisdiction over the operator.** Under the US CLOUD Act, US authorities can compel providers subject to US jurisdiction to disclose data they control, wherever it is stored. Both vendors are US companies, running on US hyperscalers. Policies that redirect requests and customer-held keys reduce the risk; they do not remove the legal exposure.

Two details are easy to miss:

- **Metadata.** Databricks' own Protected B page notes that some fields, such as names and repository details, might be stored, processed or accessed outside the compliance boundary. Metadata is sensitive too.
- **Defaults.** Cross-region AI features and Geo-level processing depend on configuration. Sovereignty depends on settings someone must check.

## Is that a reason not to use them?

Not necessarily. Many Canadian organisations are comfortable with residency plus strong contracts. Others, such as some government departments, banks and organisations with sensitive personal data, need the operator itself to be Canadian. The right answer depends on your risk assessment.

## What questions should you ask any lakehouse vendor?

1. Which legal entity operates the service, and which laws apply to it and its parent?
2. Do the control plane, catalog metadata and logs stay in Canada?
3. Which features can process data outside Canada, and are they off by default?
4. Who holds the encryption keys?
5. Where are support staff, and can they access our data?
6. Can we run the platform in our own data centre or a Canadian cloud if needed?

## Where does DataNature fit?

DataNature is built and operated by Dlytica, a Canadian company, and runs on R2i Edwin in Canada, in your own cloud account or on-premises. Data, metadata, the control plane and AI stay in Canada. See [DataNature vs Databricks](/compare/databricks-alternative), [DataNature vs Snowflake](/compare/snowflake-alternative) and the [Canadian data sovereignty checklist](/blog/canadian-data-sovereignty-checklist).

## Sources

- [Databricks docs: Databricks Geos and data residency](https://docs.databricks.com/aws/en/resources/databricks-geos)
- [Databricks docs: Canada Protected B](https://docs.databricks.com/aws/en/security/privacy/cccs-medium-protected-b)
- [Snowflake: data sovereignty capabilities](https://www.snowflake.com/en/company/overview/data-sovereignty-europe/)
- [Snowflake: Protected B assessment note](https://snowflake.com/en/blog/partnering-aws-european-sovereign-cloud/)
- [BLG: Data sovereignty and the CLOUD Act](https://www.blg.com/en/insights/2026/04/data-sovereignty-and-the-cloud-act-what-canadian-organizations-should-know)

## What does Databricks' Geo model mean for Canadian AI features?

Databricks groups Canada with the United States and Brazil in a single Americas Geo, and processes some AI features, which it calls Designated Services, on a Geo basis. In-Geo processing therefore means the Americas, not Canada only, and Databricks documents that cross-Geo processing is on by default for some Geos without a compliance security profile. We explain the settings and the questions to ask in [Databricks Geos and Canadian data](/blog/databricks-geos-canada-data-residency).

## How does DataNature Atlas keep this secure and compliant?

Every rule in this article is enforced in one place, inside your jurisdiction. [DataNature Atlas](/platform/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](/blog/datanature-atlas-governance-rbac-abac-pii-masking) or see [security and compliance](/security).
