# Databricks Geos and Canadian data: what "cross-Geo processing" means for residency

> Databricks groups Canada, the United States and Brazil into one "Americas" Geo. Some features, called Designated Services and including AI workloads, are processed on a Geo basis, so Canadian content can be processed elsewhere in the Americas Geo. Admins can enforce in-Geo processing, but in-Geo still means the Americas, not Canada only. Teams with a Canada-only rule need a platform that processes everything in-country.

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

Canadian teams often choose a cloud platform's Canada region and assume that settles residency. For core compute it usually does. For AI-assisted features, Databricks documents a wider boundary. This article explains Databricks Geos, what they mean for Canadian data, and the questions to ask before you enable AI features on regulated data.

## What is a Databricks Geo?

A Geo is a group of cloud regions that Databricks treats as one boundary for certain services. According to Databricks' documentation, the Americas Geo comprises the **United States, Brazil and Canada**. Other Geos include Europe (the EEA, Switzerland and the UK), Asia, Australia and New Zealand, India, Mainland China, and the Middle East and Africa.

## What are Designated Services?

Designated Services are features that Databricks manages on the customer's behalf and offers on a Geo basis rather than per region. Databricks states that they include services that power AI workloads, and that they are always managed by Databricks. For these services, customer content is processed within the workspace's Geo, unless cross-Geo processing is enabled.

## What does that mean for a workspace in Canada?

| Setting | Where Designated Services may process Canadian content |
|---|---|
| In-Geo processing enforced | Anywhere in the Americas Geo: Canada, the United States or Brazil |
| Cross-Geo processing enabled | Outside the Americas Geo as well |

Regional compute planes stay in their region: Databricks states that classic and serverless compute resources do not process data outside the selected region. The wider boundary applies to Designated Services.

Databricks also documents that cross-Geo processing is enabled by default for workspaces in Geos outside the US and EU that do not have a compliance security profile, and that admins may need to disable in-Geo enforcement for some AI assistive features to work. Check these settings per workspace.

## Why does this matter for sovereignty?

Because residency rules are usually written per country, not per vendor grouping. A policy that says "personal information is processed in Canada" is not met by "processed in the Americas". AI features are also where prompts, schemas, sample rows and query text tend to flow, which is exactly the content regulators ask about.

It also matters for legal reach. Data processed by a US-headquartered provider can be subject to US legal process such as the CLOUD Act, wherever it sits, and that question is separate from region choice.

## What should Canadian teams check before enabling AI features?

1. Which features in your workspace are Designated Services?
2. Is in-Geo processing enforced, and which features stop working if it is?
3. Is a compliance security profile enabled?
4. What content does each AI feature send: prompts, schemas, sample data, query text?
5. Where are logs and telemetry from those features stored?
6. Does your privacy impact assessment cover processing in the United States or Brazil?

## How does DataNature handle the same question?

DataNature has no Geo concept because it has no shared vendor region. The whole platform, including the control plane, AI gateway, vector store, semantic layer and audit log, runs in the deployment you choose: a Canadian sovereign cloud such as Edwin by R2i, your own Canadian data centre, or air-gapped. Models are called through an AI gateway pointed at an endpoint you approve, which can run in the same Canadian facility. Processing location is a deployment fact, not a toggle.

## Frequently asked questions

### Does a Databricks Canada region keep all processing in Canada?

Regional compute stays in the region. Designated Services, including AI features, are processed on a Geo basis, and Canada's Geo also contains the United States and Brazil.

### Can I keep Databricks and still meet a Canada-only rule?

For workloads that use only regional compute and no Designated Services, often yes, subject to your legal review. For AI features on regulated data, review Geo settings carefully or run those workloads on an in-country platform.

### Is this a criticism of Databricks?

No. Geos are a documented, reasonable design for a global service. They are simply wider than a single country, which matters when your rule is national.

## Sources

- [Databricks documentation: Databricks Geos, data residency](https://docs.databricks.com/aws/en/resources/databricks-geos)
- [Microsoft Learn: Azure Databricks Geos](https://learn.microsoft.com/en-us/Azure/databricks/resources/databricks-geos)
- [DataNature: the US CLOUD Act and Canadian data](/blog/us-cloud-act-and-canadian-data)

## 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).
