# Sovereignty and compliance

> Plain explanations of data residency, data sovereignty and the rules that shape them: OSFI E-23, Quebec Law 25, PIPEDA, the CLOUD Act, cloud procurement and audit. Each guide ends with what to check in your own platform.

Source: https://datanature.ai/blog/category/sovereignty-and-compliance
Publisher: Dlytica Inc. (DataNature is a Dlytica company)
Updated: 2026-11-03

- [A sovereign data and AI platform for Europe: what GDPR, DORA, NIS2 and the EU AI Act ask of your lakehouse](https://datanature.ai/blog/sovereign-data-ai-platform-europe-gdpr-dora-nis2-ai-act.md): European regulated organizations need more than an EU region. GDPR governs transfers and processing, DORA requires financial entities to manage ICT third-party risk and exit plans, NIS2 adds supply-chain security for critical sectors, and the EU AI Act asks for data governance and traceability for high-risk AI. A lakehouse that runs under EU jurisdiction, on open formats, with lineage and audit inside the EU, addresses all four.
- [Private AI vs sovereign AI: the difference, and what each demands from your data platform](https://datanature.ai/blog/private-ai-vs-sovereign-ai.md): Private AI keeps your data, prompts and models away from other parties: no training on your data, controlled access, nothing shared. Sovereign AI adds jurisdiction: the data, the models, the metadata and the operators all sit under the laws you choose. Private AI is about who can see; sovereign AI is about where it runs and who governs it.
- [Row-level security and column masking on a lakehouse: how to design policies that hold](https://datanature.ai/blog/lakehouse-row-level-security-column-masking.md): In DataNature, row-level security is a SQL predicate per user or group, and column masking is a mask type per column: null, redact, first or last four, hash, year only or exempt. Atlas enforces both in the interactive SQL and serving compute (Trino and DN Warehouse), in JDBC clients, cubes and impersonating Superset connections, within about a minute of a change.
- [DataNature Atlas in depth: RBAC, ABAC, automated PII masking and a governed semantic layer](https://datanature.ai/blog/datanature-atlas-governance-rbac-abac-pii-masking.md): DataNature Atlas is the platform's governance module: catalog, classification, lineage, certified metrics, access policies and audit. Atlas combines role-based access (who you are) with attribute-based policies (what the data is and what you are cleared for), masks PII automatically from classifications, and enforces the same rules in SQL, cubes, dashboards and AI agents, so one set of controls supports GDPR, PIPEDA, Law 25, CCPA, HIPAA and sector rules.
- [Databricks Geos and Canadian data: what "cross-Geo processing" means for residency](https://datanature.ai/blog/databricks-geos-canada-data-residency.md): 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.
- [Data residency for AI in Saudi Arabia, the UAE and the GCC: PDPL, SAMA, NCA and in-Kingdom lakehouses](https://datanature.ai/blog/data-residency-ai-saudi-arabia-uae-gcc.md): In Saudi Arabia, the PDPL is enforced by SDAIA, and SAMA and NCA expect banking and critical-sector data to stay in the Kingdom. In the UAE, the federal PDPL applies, and the Central Bank expects core banking and customer data to be processed in the country. For AI, residency covers the whole path: data, embeddings, prompts, model inference and logs. An in-country lakehouse with a local AI gateway keeps all of them inside the border.
- [Data localisation for banks in India, Nepal and South Asia: DPDP, RBI and in-country AI](https://datanature.ai/blog/data-localisation-banks-india-nepal-south-asia-dpdp-rbi.md): India's DPDP Act and Rules, notified in November 2025, set a consent- and security-driven privacy regime, while sectoral rules such as the RBI's 2018 payment data direction require payment data to be stored only in India. Nepal's banks, like many in South Asia, prefer to keep banking data in-country. An in-country lakehouse with local AI inference meets both the letter of storage rules and the growing expectation that processing stays local too.
- [Air-gapped lakehouse and private AI: a reference architecture that runs with no internet](https://datanature.ai/blog/air-gapped-lakehouse-private-ai-reference-architecture.md): An air-gapped lakehouse runs every dependency inside the enclave: object storage, Iceberg tables, Spark, Trino, the catalog, identity, secrets, a container registry mirror, model weights, the vector store and the LLM serving layer. Updates arrive on signed media. DataNature deploys this stack on Kubernetes with no outbound connection, including dbt packages committed to Git so scheduled jobs never call the internet.
- [AI outbound calling compliance: consent, disclosure and data rules in the US, Canada, Europe and beyond](https://datanature.ai/blog/ai-outbound-calling-compliance-consent-tcpa-crtc-gdpr.md): AI-voiced outbound calls are regulated like automated or prerecorded calls. In the US, the FCC confirmed in 2024 that AI-generated voices fall under the TCPA, so calls need prior express consent (written consent for marketing), caller identification and an opt-out. Canada requires express consent for automated telemarketing calls under the CRTC's Unsolicited Telecommunications Rules. In Europe, GDPR and national e-privacy rules apply. A CDP that stores consent by purpose and channel, and enforces it before every call, is the practical control.
- [Databricks and Snowflake in Canada: what their Canadian regions solve for sovereignty, and what they do not](https://datanature.ai/blog/databricks-snowflake-canada-sovereignty.md): 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.
- [OSFI Guideline E-23 explained: why it matters for Canadian banks, insurers and lenders, and how DataNature Atlas helps](https://datanature.ai/blog/osfi-e-23-guideline-canadian-financial-institutions.md): OSFI Guideline E-23 sets expectations for enterprise-wide model risk management at every federally regulated financial institution in Canada, effective May 1, 2027. It covers traditional, AI and machine learning models, including vendor and third-party models, across their whole lifecycle. DataNature Atlas helps institutions meet it by keeping a governed inventory of data, models and agents, with lineage from every decision back to source, access controls, PII masking, an AI gateway and a complete audit trail, all inside Canada.
- [Data residency and jurisdiction: what the CLOUD Act means for a data platform](https://datanature.ai/blog/us-cloud-act-and-canadian-data.md): 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.
- [Lessons from the 2024 Snowflake customer breaches: shared responsibility on any data platform](https://datanature.ai/blog/snowflake-customer-breaches-shared-responsibility-lessons.md): In 2024 attackers accessed more than 100 Snowflake customer environments using stolen credentials on accounts without multi-factor authentication. Investigators found Snowflake’s own platform was not breached. The lesson applies to every data platform: enforce single sign-on and MFA, restrict network access, rotate service credentials, monitor logs, and know exactly which controls are yours.
- [Canada’s sovereign cloud procurement: what it means for enterprises and vendors](https://datanature.ai/blog/canada-sovereign-cloud-procurement-explained.md): The Government of Canada is building a sovereign cloud procurement stream led by Shared Services Canada. At a minimum, solutions must process, transmit and store government data only in Canada and stay under Canadian control, insulated from foreign legal compulsion. Ottawa invoked the National Security Exception so the stream is exempt from trade agreements, and the open competition focuses on Canadian small and medium-sized suppliers.
- [Data residency vs data sovereignty: what is the difference?](https://datanature.ai/blog/data-residency-vs-data-sovereignty.md): Data residency is where data is stored. Data sovereignty is who controls it and which laws can compel access. A provider can store data in your country and still be subject to foreign law. True sovereignty needs the right location, the right operator and the right legal entity, covering metadata and AI as well as data.
- [Canada’s AI for All strategy: what it means for sovereign compute and data](https://datanature.ai/blog/canada-ai-for-all-strategy-sovereign-compute.md): Canada launched its national AI strategy, AI for All, on June 4, 2026. It commits to building sovereign Canadian AI infrastructure under Canadian control and law, including a public AI supercomputer, while continuing more than $2 billion in sovereign compute investments begun in December 2024. For organisations, it signals that domestic compute, cloud and data platforms will grow, and that sovereignty is now national policy.
- [The Canadian sovereign AI playbook: what Cohere shows about winning enterprise and government](https://datanature.ai/blog/canadian-ai-sovereign-playbook-lessons-from-cohere.md): Cohere became Canada’s sovereign AI champion by focusing on enterprise and government rather than consumers, offering private deployment where customers keep control, partnering with Canadian infrastructure such as Bell, winning federal work, and expanding through allied sovereignty partnerships in Europe. DataNature follows the same playbook for the data layer.
- [Canada’s sovereign AI infrastructure: Bell AI Fabric, TELUS AI factories and the Canadian cloud](https://datanature.ai/blog/canadian-ai-infrastructure-bell-telus-cohere.md): Canada’s sovereign AI infrastructure is being built by Canadian telecom operators, cloud providers and data centre companies. Bell AI Fabric and the TELUS Sovereign AI Factory offer domestic GPU capacity, while ThinkOn, R2i Edwin, Hypertec and eStruxture provide Canadian cloud, servers and facilities. Cohere supplies Canadian models and agents on top. Together they make a mostly Canadian stack possible.
- [Québec Law 25, PIPEDA and OSFI: what they mean for your data platform](https://datanature.ai/blog/quebec-law-25-pipeda-osfi-data-platform.md): PIPEDA sets federal rules for personal information in Canada. Québec Law 25 adds a privacy impact assessment before personal information leaves Québec. OSFI B-10 and B-13 require federally regulated financial institutions to manage third-party and technology risk. Together they push data platforms toward clear residency, access logging and lineage.
- [How Ottawa is adopting sovereign AI: Cohere, CANChat and what comes next](https://datanature.ai/blog/cohere-and-sovereign-ai-in-canadian-government.md): The federal government has started buying Canadian AI. Shared Services Canada licensed Cohere’s Command A model for CANChat, its in-house assistant, from November 2025, and later bought North agent licences, describing North as the only fully Canadian-developed agentic AI solution meeting its sovereignty requirements. Agents need governed data, which is where a sovereign data platform comes in.
- [Canadian data sovereignty checklist: 12 questions to ask any data and AI vendor](https://datanature.ai/blog/canadian-data-sovereignty-checklist.md): To test whether a data and AI platform is sovereign in Canada, ask where the data, metadata, control plane, models, prompts and logs live; which company operates the service and which laws govern it; who holds the encryption keys; where support staff and backups sit; and whether disaster recovery stays in Canada. A vendor should answer all twelve questions in writing.
- [Sovereign AI in Nepal banking: what banks need to know](https://datanature.ai/blog/sovereign-ai-in-nepal-banking.md): Banks in Nepal are expected to keep data in the country and follow Nepal Rastra Bank IT guidelines. Sovereign AI lets them use modern analytics and AI agents without moving data abroad. DataNature runs in Nepal on EverestCloud or on-premises, and Nabil Bank is the first bank in Nepal on it.
- [Managed, dedicated, hosted or on-premises: choosing a deployment model](https://datanature.ai/blog/choosing-a-deployment-model-for-sovereign-data.md): Choose managed for speed, dedicated for single-tenant control without running infrastructure, hosted for sovereignty on a trusted partner cloud, your own cloud for existing commitments, and on-premises or air-gapped for the strictest rules. DataNature runs the same platform in all six models, so you can move later.
