Original ResearchScorecardMarch 2026

Data Sovereignty Policy Scorecard

By Joshua van Es, Founder of Upper Harbour

Canada talks about data sovereignty as a national priority. But which governments are actually building the legal and policy infrastructure to achieve it? We graded the federal government, every province, and all three territories across six dimensions. The results are uneven — and in some cases, alarming.

Quebec
82
A
British Columbia
54
C+
Alberta
46
C
Federal (PIPEDA)
34
F
Ontario
18
F
Saskatchewan
14
F
Manitoba
14
F
New Brunswick
14
F
Nova Scotia
14
F
Prince Edward Island
14
F
Newfoundland & Labrador
14
F
Yukon
14
F
Northwest Territories
14
F
Nunavut
14
F

The headline finding

Only one Canadian jurisdiction — Quebec — has a data sovereignty framework that would be recognizable as adequate by international standards. British Columbia and Alberta have their own private-sector privacy laws, which gives them a foundation to build on, but neither has implemented cross-border transfer controls or CLOUD Act-specific provisions. The federal government's framework, PIPEDA, is a 25-year-old statute with no meaningful penalty structure, no TIA requirement, and no enforcement teeth. Ontario — Canada's largest province and economic centre — has no private-sector privacy law at all.

This is not a marginal gap. The distance between Quebec's score (82) and the average score of all other jurisdictions (27) is the distance between a country that takes data sovereignty seriously and one that doesn't. When the Prime Minister says digital sovereignty is a national priority, the scorecard shows that most of Canada's legal infrastructure does not yet support that ambition.

The federal gap

The proposed Consumer Privacy Protection Act (CPPA) under Bill C-27 died on the order paper in January 2025. The Osler legal review expects new legislation in late 2025 or early 2026, but as of February 2026 no replacement for PIPEDA has been enacted. This means Canada's federal private-sector privacy framework dates to 2001 and carries a maximum penalty of $100,000 — roughly what a mid-size SaaS contract costs. The European Commission's adequacy determination for Canada, which enables cross-border data flows with the EU, was made on the basis of PIPEDA. If Canada's framework is deemed insufficient for adequacy renewal, the trade implications are significant.

Methodology

The scorecard evaluates each jurisdiction across six equally weighted dimensions, each scored 0–4 on a transparent rubric. The six dimension scores are summed (maximum 24) and converted to a percentage (maximum 100). We selected dimensions that map directly to whether a jurisdiction's legal framework can actually protect Canadian data from foreign jurisdictional reach — which is what sovereignty means in practice.

Dimension 1: Legislation strength (0–4)

Does the jurisdiction have modern, comprehensive private-sector privacy legislation with data sovereignty provisions? Scores range from 0 (no provincial private-sector law, relies on PIPEDA) to 4 (comprehensive, modern legislation with explicit cross-border and sovereignty provisions, comparable to GDPR).

Dimension 2: Enforcement capacity (0–4)

Does the regulator have order-making power, adequate resources, and a demonstrated track record of enforcement? A law without enforcement is a suggestion. Scores range from 0 (regulator can only make recommendations) to 4 (regulator has order-making power, has issued post-reform enforcement actions, and processes a significant volume of complaints and incident notifications).

Dimension 3: Procurement sovereignty (0–4)

Does government procurement policy require or incentivize data sovereignty for public-sector SaaS and cloud purchases? Government procurement is the single largest policy lever for driving sovereignty standards into the market. Scores range from 0 (no sovereignty requirements in procurement) to 4 (explicit data sovereignty and Canadian-ownership requirements in government technology procurement, with enforcement mechanisms).

Dimension 4: Cross-border transfer controls (0–4)

Are Transfer Impact Assessments or equivalent mechanisms mandatory for cross-border data flows? This is the operational heart of sovereignty: if an organization can send data offshore without documenting the risks, the framework is incomplete. Scores range from 0 (no TIA or equivalent requirement) to 4 (mandatory TIAs with specific evaluation criteria for foreign legal frameworks, including extraterritorial law access).

Dimension 5: CLOUD Act awareness (0–4)

Does the legal framework explicitly acknowledge or address the risk of foreign law access to data, including the US CLOUD Act? The CLOUD Act is the single biggest jurisdictional threat to Canadian data sovereignty. A framework that doesn't address it is ignoring the primary risk. Scores range from 0 (no mention or acknowledgment) to 4 (legal framework explicitly addresses extraterritorial foreign law access, with binding requirements for organizations to assess and mitigate CLOUD Act exposure).

Dimension 6: Penalty and accountability (0–4)

Are penalties meaningful enough to drive compliance? Do individuals have private rights of action? Compliance follows consequences. Scores range from 0 (no meaningful penalties, no private right of action) to 4 (administrative penalties in the millions or percentage of revenue, penal fines, and private right of action with minimum statutory damages).

Full rankings

RankJurisdictionLegislationEnforcementProcurementTransfer ControlsCLOUD ActPenaltyTotal /100
1Quebec44342482
2British Columbia32311254
3Alberta32111346
4Federal (PIPEDA)21211134
5Ontario01100118
6Saskatchewan01000114
7Manitoba01000114
8New Brunswick01000114
8Nova Scotia01000114
8Prince Edward Island01000114
8Newfoundland & Labrador01000114
8Yukon01000114
8Northwest Territories01000114
8Nunavut01000114

Jurisdiction analysis

Quebec
82 / 100 — A
Legislation
4/4 — Law 25 (fully in force)
Enforcement
4/4 — CAI active (277 complaints, 444 incidents)
Procurement
3/4 — Residency norms, no ownership mandate
Transfer Controls
4/4 — Mandatory TIAs since Sept 2023
CLOUD Act Awareness
2/4 — TIA framework addresses it implicitly
Penalty & Accountability
4/4 — $25M / 4% + private right of action
Quebec is the clear leader. Law 25 is the most comprehensive provincial privacy law in Canada and the only one that mandates Transfer Impact Assessments for cross-border data transfers. The CAI is actively processing hundreds of complaints and incident notifications annually and issued its first post-reform enforcement order in September 2024. Quebec loses points on CLOUD Act awareness — the TIA framework requires evaluation of foreign legal frameworks, which implicitly covers the CLOUD Act, but there is no explicit statutory reference to extraterritorial foreign law access. Procurement sovereignty is strong but relies on administrative norms rather than binding legislation requiring Canadian-owned infrastructure. Even so, Quebec is the only Canadian jurisdiction operating at a level comparable to the EU's post-Schrems II framework.
British Columbia
54 / 100 — C+
Legislation
3/4 — PIPA + FIPPA (public sector residency)
Enforcement
2/4 — OIPC has order power, limited volume
Procurement
3/4 — FIPPA PIA requirement for foreign-stored data
Transfer Controls
2/4 — FIPPA PIA required for sensitive PI outside Canada
CLOUD Act Awareness
2/4 — PIA must assess foreign access laws (post-2021)
Penalty & Accountability
2/4 — Limited fines, no private right of action
BC was historically the only province that mandated data residency in Canada for public bodies under FIPPA section 30.1. The 2021 amendment (Bill 22) relaxed this blanket prohibition, replacing it with a risk-assessment framework — public bodies can now store sensitive personal information outside Canada after completing a privacy impact assessment that evaluates jurisdictional risk, including foreign government access laws. This is arguably a more sophisticated sovereignty posture than the old binary rule, as it requires active jurisdictional analysis rather than simple geography checks. PIPA provides a provincial private-sector framework, but it lacks the cross-border transfer controls, penalty severity, and enforcement volume of Law 25.
Alberta
46 / 100 — C
Legislation
3/4 — PIPA (under review, amendments expected)
Enforcement
2/4 — OIPC has order power, moderate activity
Procurement
1/4 — Some residency norms, no binding sovereignty rules
Transfer Controls
1/4 — No mandatory TIA
CLOUD Act Awareness
1/4 — Not explicitly addressed
Penalty & Accountability
3/4 — Fines up to $200K, review committee recommended penalty-based enforcement
Alberta's PIPA legislative review committee completed its report in February 2025 with 12 recommendations, including introducing a penalty-based enforcement regime. If those recommendations are enacted, Alberta's score could improve significantly — potentially reaching the low 60s. For now, Alberta has a functional but aging private-sector privacy framework that doesn't address cross-border sovereignty concerns. Alberta's AI Data Centre Strategy is attracting significant investment — $100B target over five years — but the data governance framework hasn't kept pace with the infrastructure ambition.
Federal Government (PIPEDA)
34 / 100 — F
Legislation
2/4 — PIPEDA exists but hasn't been materially updated since 2001
Enforcement
1/4 — OPC has limited enforcement power, no order-making authority
Procurement
2/4 — Digital Sovereignty Framework exists, not yet binding
Transfer Controls
1/4 — OPC recommends assessments but they're not mandatory
CLOUD Act Awareness
1/4 — Digital Sovereignty Framework acknowledges it; PIPEDA doesn't
Penalty & Accountability
1/4 — Maximum penalty $100,000, no private right of action
The federal score is the most consequential on this list — because PIPEDA is the default framework for seven provinces and all three territories. The federal government has published a Digital Sovereignty Framework (2025) that correctly identifies foreign technology dependencies as a risk, and the proposed CPPA would significantly strengthen the penalty structure and potentially introduce TIA requirements. But as of February 2026, PIPEDA remains the law. The OPC cannot issue binding orders. The maximum penalty is $100,000. There is no private right of action. This means for the majority of Canadians — everyone outside Quebec, BC, and Alberta — the legal framework protecting their data from foreign jurisdictional reach is a quarter-century-old statute with no meaningful enforcement mechanism. The gap between the government's sovereignty rhetoric and its legal infrastructure is the largest of any jurisdiction on this scorecard.
Ontario
18 / 100 — F
Legislation
0/4 — No provincial private-sector law
Enforcement
1/4 — IPC exists but limited to public sector
Procurement
1/4 — Some residency awareness, no binding sovereignty rules
Transfer Controls
0/4 — No requirement
CLOUD Act Awareness
0/4 — Not addressed
Penalty & Accountability
1/4 — Relies on PIPEDA's $100K maximum
Ontario's score should be a policy alarm. As Canada's most populous province, largest economic centre, and home to its largest technology sector, Ontario has no private-sector privacy law, no TIA requirement, no CLOUD Act provisions, and no private right of action for privacy violations. An Ontario-headquartered organization using US-parented SaaS tools has no provincial obligation to assess, document, or mitigate the jurisdictional exposure of its data. The same organization operating in Quebec would require 10–16 TIAs. Ontario has discussed introducing a private-sector privacy law for years, but no legislation has been enacted. Every year this gap persists, Ontario's data becomes more exposed — and its organizations less prepared for the federal reforms that are coming.

The structural problem

This scorecard reveals something more important than individual grades: it shows that Canada's data sovereignty posture is structurally fragmented. The variation between jurisdictions is not a feature of federalism — it is a vulnerability.

Consider what this means in practice. A national organization headquartered in Ontario, with employees in Quebec and clients in British Columbia, faces three entirely different compliance regimes. Its Quebec employees' data requires TIAs for every US-parented SaaS tool. Its Ontario operations have no such obligation. Its BC public-sector clients may require data residency in Canada. None of this is coordinated. There is no mutual recognition framework. There is no baseline standard.

The EU solved a comparable coordination problem through the GDPR — a single, binding regulation that applies across all member states with consistent enforcement. Canada has gone the opposite direction: a patchwork of federal, provincial, and territorial frameworks with no unifying floor.

What the CPPA would change

If enacted in a form comparable to Bill C-27, the CPPA would raise the federal score significantly: penalties would increase to $25M or 5% of revenue, a private right of action would be introduced, the OPC would gain order-making power, and the proposed Tribunal would create an enforcement mechanism with teeth. The critical open question is whether the CPPA will include explicit cross-border transfer assessment requirements and CLOUD Act-specific provisions. If it does, the federal score could jump from 34 to the low 70s — which would automatically raise the floor for the seven provinces and three territories that rely on PIPEDA. If it doesn't address cross-border sovereignty explicitly, the CPPA will be a better privacy law but still an incomplete sovereignty framework.

Policy implications

Three things need to happen for Canada's data sovereignty posture to match its stated ambitions:

First, the federal government needs to pass CPPA — with explicit cross-border sovereignty provisions. The CPPA as proposed in Bill C-27 would significantly strengthen the penalty structure and enforcement capacity. But it needs to go further. Mandatory Transfer Impact Assessments for cross-border data flows, explicit CLOUD Act risk assessment requirements, and a sovereignty-aware procurement framework should be built into the legislation, not left to guidance documents that can be ignored.

Second, Ontario needs a private-sector privacy law. The largest province in Canada cannot continue to rely on a 25-year-old federal statute for private-sector privacy protection. Ontario's lack of legislation creates a sovereignty gap at the centre of the Canadian economy. Every other G7 country's largest economic jurisdiction has modern privacy legislation. Ontario is the outlier.

Third, Canada needs a coordination mechanism. The current fragmentation is not just inefficient — it is a strategic vulnerability. A national organization cannot manage 13 different sovereignty frameworks efficiently. The federal government, in consultation with provinces, should establish a minimum sovereignty standard — a floor that no jurisdiction falls below — while allowing provinces like Quebec to exceed it. This is not an unprecedented ask: Canada already does this in securities regulation, environmental assessment, and building codes.

How we'll track progress

This scorecard will be updated quarterly. As legislation is introduced, enacted, or amended, scores will be adjusted with full transparency about what changed and why. Alberta's expected PIPA amendments will be a significant early test — if the review committee's 12 recommendations are enacted, Alberta could move from a C to a B. The CPPA's passage (or continued absence) will be the single biggest score change on the next update.

Jurisdictions that want to improve their score know what to do. The methodology is transparent. The dimensions are weighted equally. There are no subjective style points. A province's score improves when its legal framework demonstrably strengthens the sovereignty of Canadian data within its borders.

About this research

This scorecard was developed by Joshua van Es at Upper Harbour, drawing on the analysis underlying the Canadian Technology Sovereignty Index (715 tools mapped), the Provincial Exposure Index, and the Government SaaS Stack Audit. Van Es has a background in corporate law and policy research, and his work has been published in Maclean's, OpenCanada, BetaKit, and by McGill-Queen's University Press. Questions, corrections, and feedback: [email protected].

Frequently asked questions

Which province scores highest on data sovereignty readiness?
Quebec, with 82 out of 100. Law 25 is the only Canadian provincial law that mandates Transfer Impact Assessments, carries penalties up to $25M or 4% of global turnover, and provides a private right of action. It is the only jurisdiction actively enforcing post-reform provisions.
Why does the federal government get a failing grade?
PIPEDA has not been materially updated since 2001. Maximum penalty: $100,000. No order-making power for the OPC. No mandatory TIA requirement. No private right of action. The CPPA died on the order paper in January 2025. The federal Digital Sovereignty Framework acknowledges the problem but hasn't produced binding requirements. The gap between sovereignty rhetoric and legal infrastructure is the largest of any jurisdiction.
How would the CPPA change the federal score?
If enacted in a form comparable to Bill C-27, the CPPA could raise the federal score from 34 to the low 70s — depending on whether it includes explicit cross-border sovereignty provisions. It would also automatically raise the floor for the seven provinces and three territories that rely on PIPEDA as their private-sector framework.
How is the scorecard calculated?
Six dimensions, each scored 0–4: Legislation Strength, Enforcement Capacity, Procurement Sovereignty, Cross-Border Transfer Controls, CLOUD Act Awareness, and Penalty & Accountability Structure. Scores are summed (max 24) and converted to a percentage. Full rubric descriptions are published in the methodology section above.
How often is the scorecard updated?
Quarterly. Score changes are documented with full transparency about what changed and why.

See how sovereignty affects your stack

HarbourScan maps your organization's SaaS tools to the jurisdictional framework that applies in your province. Free. Browser-based. No data stored.

Map Your Stack →

Need help operationalizing HarbourScan? Request a scoping call →