Data Protection Monitor
Global Privacy & Data Protection Intelligence

Ontario, Canada Data Protection & Privacy Regulation

CA-ON schema gdpri-v2 trajectory: not yet assessed hybrid regime overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 84 claims · 49 sources in the cumulative register

Ontario's private-sector data protection landscape is currently defined less by settled law than by overlapping and potentially conflicting federal reform tracks.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Regulator & Framework, Lawful Processing & Special Data, Cross-Border & Adequacy, AdTech & Commercial Privacy, Children & Vulnerable Groups (6 open gaps).

Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-10-26

Framework postureHybrid regime10 of 10 modules populated · AI-synthesised · Tier-1/2 verified
Lead supervisory authorityOffice of the Privacy Commissioner of Canada (OPC)Primary statutory & supervisory perimeter
Next milestone (> 2026-10-26)2028-01-01Next EU Commission periodic review of Canada's PIPEDA adequacy decision
Module coverage & confidence10 / 10 modules assessed0 Confirmed · 9 Probable · 1 Uncertain

Canada federal law that applies in Ontario, Canada is covered once, on the Canada page. This page covers Ontario, Canada’s own layer: its own law, regulators and enforcement.

Jurisdiction lead brief

Latest update · 4 November 2026

Lead Signal

The most consequential activity for Ontario this period sits at the federal level, where the Office of the Privacy Commissioner of Canada moved on several fronts simultaneously. The OPC closed its investigation into WestJet's cyberattack-related security measures on October 14, 2026, separately secured a commitment from Loblaw to strengthen security measures following a privacy breach, and, on October 27, 2026, opened a new investigation into a breach disclosed by Navigate360 (operating in connection with Crime Stoppers) that stemmed from a cybersecurity incident originally occurring in March 2026. A parallel consumer proceeding reportedly alleges violations of both PIPEDA and provincial Consumer Protection Act provisions over delayed notification, though this reporting rests on third-party press coverage rather than the OPC's own case file.

Key regulatory facts for Ontario, Canada
Regulatory DimensionOntario, Canada Standing Position
JurisdictionOntario, Canada (CA-ON)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 84 sourced findings)
Regulator & FrameworkFramework is mature and well-documented but structurally fragmented across two regulators and multiple statutes with no unified Ontario private-sector code; federal reform (PIPEDA modernization) remains incomplete.
Lawful Processing & Special DataConsent framework is well-established and judicially tested, but the absence of a codified special-categories list and of a statutory anonymization safe-harbour (features recommended by the Commissioner for the...
Data Subject RightsCore access/correction rights exist and are enforced, but portability, explicit restriction/objection, and erasure/de-indexing rights are either absent or only proposed, not yet in force.
Controller/Processor DutiesBreach notification and accountability duties are in force and judicially reinforced, but DPIA/DPO/ROPA equivalents remain non-statutory, and enforcement of breach obligations is indirect (referral-based, no OPC...
Primary Instruments CitedOPC, OPC, OPC, OPC, IAPP
Last Confirmed / Updated2026-11-04 (49 sources in cumulative register)

#

Framework is mature and well-documented but structurally fragmented across two regulators and multiple statutes with no unified Ontario private-sector code; federal reform (PIPEDA modernization) remains incomplete.

Primary frameworkPIPEDA (federal, private sector) + PHIPA/FIPPA/CYFSA Part X (Ontario sectoral/public sector)
Traffic-light rationale — AmberFramework is mature and well-documented but structurally fragmented across two regulators and multiple statutes with no unified Ontario private-sector code; federal reform (PIPEDA modernization) remains incomplete.

Sub-modules (5)

Regulator And AuthorityGreen

OPC (federal, Gatineau HQ with a Toronto regional office) enforces PIPEDA; IPC Ontario enforces PHIPA/FIPPA/CYFSA Part X. The two regulators operate under a 2025-updated MOU enabling joint investigations.

Claims (5):

  • The Office of the Privacy Commissioner of Canada oversees compliance with PIPEDA, Canada's federal private-sector privacy law, and maintains a Toronto regional office to promote PIPEDA compliance in Ontario.
  • The Information and Privacy Commissioner of Ontario has oversight of personal information and personal health information under FIPPA, PHIPA, and Part X of the CYFSA (the 'Ontario Statutes').
  • organisations engaged in commercial activities; provincial laws of substantially similar force (Quebec, BC, Alberta) take precedence only in those provinces; Ontario has no such law so PIPEDA governs directly
  • PIPEDA (federal) — General commercial private-sector processing in Ontario is governed directly by the federal PIPEDA, not by a provincial statute; the IPC's own jurisdiction is limited to the public sector (FIPPA/MFIPPA) and health sector (PHIPA)
  • Information and Privacy Commissioner of Ontario / Office of the Privacy Commissioner of Canada — Ontario has no general private-sector data-protection statute; the IPC Ontario's statutory mandate is confined to the public sector under FIPPA/MFIPPA and the health sector under PHIPA, while general commercial private-sector activity in Ontario is governed directly by federal PIPEDA under OPC supervision.

Act And InstrumentsGreen

Core instruments: PIPEDA (Royal Assent 2000-04-13); PHIPA 2004; FIPPA R.S.O. 1990; CYFSA 2017 Part X.

Claims (4):

  • PIPEDA is the complete version that received Royal Assent on April 13, 2000, and Schedule 1 contains the 10 fair information principles referred to throughout the Act.
  • Bill 97, A Plan to Protect Ontario Act (Budget Measures), 2026 — Amended FIPPA and MFIPPA with further amendments in force 2026-07-01 and 2026-09-15, and additional provisions scheduled to commence 2027-01-01; as a result some IPC guidance is under review and subject to change
  • Bill C-36 (Protecting Privacy and Consumer Data Act) — received first reading in the House of Commons June 15, 2026; not yet in force; would replace Part 1 of PIPEDA and create the Digital Safety and Data Protection Commission of Canada
  • Bill C-15 PIPEDA Division 1.2 (data mobility) — Received Royal Assent 26 March 2026 but not yet in force; no implementing regulations published; Bill C-36's coordinating amendments would repeal this Division if C-36 commences first

Material ScopeGreen

PIPEDA covers factual or subjective recorded/unrecorded information about an identifiable individual collected in commercial activity.

Claims (1):

  • Under PIPEDA, personal information includes any factual or subjective information, recorded or not, about an identifiable individual, collected in the course of commercial activity.

Territorial ScopeGreen

PIPEDA applies to interprovincial/international transfers and to organizations doing business in/into Canada regardless of headquarters location, as confirmed by Federal Court/FCA rulings on Google's search service.

Claims (1):

  • The Federal Court (2021) and Federal Court of Appeal (2023) confirmed PIPEDA applies to Google's search engine service, establishing that PIPEDA's application is not limited by an organization's foreign incorporation where it collects, uses, or discloses personal information in the course of commercial activities connected to Canada.

Regulator Registration And FilingAmber

PIPEDA imposes no general registration/filing regime on controllers; the only affirmative filing-adjacent duty is mandatory breach record-keeping (2-year retention, producible to OPC on request).

Claims (1):

  • PIPEDA requires organizations to keep and maintain a record of every breach of security safeguards involving personal information under their control, regardless of harm level, for at least two years.
Category narrative 80 words

CA-ON sits inside Canada's federated privacy architecture: the federal Office of the Privacy Commissioner of Canada (OPC) enforces PIPEDA as the general private-sector omnibus statute across Ontario (no substantially-similar provincial private-sector law exists in Ontario, unlike AB/BC/QC), while the Ontario Information and Privacy Commissioner (IPC) enforces three Ontario-specific sectoral/public statutes: PHIPA (health), FIPPA (provincial public sector access/privacy) and Part X of the CYFSA (child welfare privacy). This creates a dual-regulator, sector-stacked model rather than a single comprehensive Ontario private-sector statute.

Periodic update · new data 2026-10-25

Regulator & Framework

Federal PIPEDA governs general private-sector commercial activity directly in Ontario, since no substantially-similar provincial private-sector law exists; the Information and Privacy Commissioner of Ontario's mandate under FIPPA/MFIPPA and PHIPA is limited to the public sector and the health sector respectively, so PIPEDA remains the applicable general commercial-privacy statute for Ontario organisations. Two federal reform tracks are now in motion simultaneously. Bill C-36, the Protecting Privacy and Consumer Data Act, was tabled on 15 June 2026 and would repeal Part 1 of PIPEDA in full, replacing the Office of the Privacy Commissioner with a newly created Digital Safety and Data Protection Commission of Canada; as at its Charter Statement of 28 August 2026, the bill remained before Parliament without Royal Assent. Separately, Bill C-15's PIPEDA Division 1.2, the data-mobility provision, received Royal Assent on 26 March 2026 but is not yet in force, with no implementing regulations yet published. Bill C-36 contains coordinating amendments that would repeal this data-mobility Division if C-36 commences first, creating a direct sequencing conflict between the two reform paths.

Outlook

Which bill commences first, and whether Bill C-36 is enacted at all, will determine whether Ontario organisations plan around an enhanced single federal regulator model or around the existing OPC structure with an added data-mobility right. The current reading or committee stage of Bill C-36 following its 28 August 2026 Charter Statement was not located, leaving the near-term legislative trajectory uncertain.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (12)
  1. Confirmed OPC — The Office of the Privacy Commissioner of Canada oversees compliance with PIPEDA, Canada's federal private-sector privacy law, and maintains a Toronto regional office to promote PIPEDA compliance in Ontario. observed
  2. Confirmed OPC — The Information and Privacy Commissioner of Ontario has oversight of personal information and personal health information under FIPPA, PHIPA, and Part X of the CYFSA (the 'Ontario Statutes'). observed
  3. Confirmed OPC — PIPEDA is the complete version that received Royal Assent on April 13, 2000, and Schedule 1 contains the 10 fair information principles referred to throughout the Act. observed
  4. Confirmed OPC — Under PIPEDA, personal information includes any factual or subjective information, recorded or not, about an identifiable individual, collected in the course of commercial activity. observed
  5. Confirmed OPC — The Federal Court (2021) and Federal Court of Appeal (2023) confirmed PIPEDA applies to Google's search engine service, establishing that PIPEDA's application is not limited by an organization's foreign incorporation where it collects, uses, or discloses personal information in the course of commercial activities connected to Canada. observed
  6. Confirmed IAPP — PIPEDA requires organizations to keep and maintain a record of every breach of security safeguards involving personal information under their control, regardless of harm level, for at least two years. observed
  7. Confirmed Information and Privacy Commissioner of Ontario — Bill 97, A Plan to Protect Ontario Act (Budget Measures), 2026 — Amended FIPPA and MFIPPA with further amendments in force 2026-07-01 and 2026-09-15, and additional provisions scheduled to commence 2027-01-01; as a result some IPC guidance is under review and subject to change observed
  8. Probable Questa AI — Bill C-36 (Protecting Privacy and Consumer Data Act) — received first reading in the House of Commons June 15, 2026; not yet in force; would replace Part 1 of PIPEDA and create the Digital Safety and Data Protection Commission of Canada observed
  9. Probable recordinglaw.com — Bill C-15 PIPEDA Division 1.2 (data mobility) — Received Royal Assent 26 March 2026 but not yet in force; no implementing regulations published; Bill C-36's coordinating amendments would repeal this Division if C-36 commences first observed
  10. Probable callsphere.ai — organisations engaged in commercial activities; provincial laws of substantially similar force (Quebec, BC, Alberta) take precedence only in those provinces; Ontario has no such law so PIPEDA governs directly observed
  11. Confirmed Information and Privacy Commissioner of Ontario — PIPEDA (federal) — General commercial private-sector processing in Ontario is governed directly by the federal PIPEDA, not by a provincial statute; the IPC's own jurisdiction is limited to the public sector (FIPPA/MFIPPA) and health sector (PHIPA) observed
  12. Confirmed Information and Privacy Commissioner of Ontario — Information and Privacy Commissioner of Ontario / Office of the Privacy Commissioner of Canada — Ontario has no general private-sector data-protection statute; the IPC Ontario's statutory mandate is confined to the public sector under FIPPA/MFIPPA and the health sector under PHIPA, while general commercial private-sector activity in Ontario is governed directly by federal PIPEDA under OPC supervision. observed

#

Consent framework is well-established and judicially tested, but the absence of a codified special-categories list and of a statutory anonymization safe-harbour (features recommended by the Commissioner for the stalled CPPA reform) leaves gaps relative to GDPR-equivalent regimes.

Primary frameworkPIPEDA Schedule 1 (Fair Information Principles) + PHIPA (health data)
Traffic-light rationale — AmberConsent framework is well-established and judicially tested, but the absence of a codified special-categories list and of a statutory anonymization safe-harbour (features recommended by the Commissioner for the stalled CPPA reform) leaves gaps relative to GDPR-equivalent regimes.
Periodic update · new data 2026-10-25

Lawful Processing & Special Data

Bill C-36 proposes expanded consent exceptions alongside de-identification provisions as part of its broader restructuring of the federal privacy framework, though the bill remained before Parliament without Royal Assent as at its 28 August 2026 Charter Statement. These proposed exceptions would sit within the same Bill that would repeal Part 1 of PIPEDA and create the Digital Safety and Data Protection Commission of Canada, meaning the lawful-processing framework currently governing PIPEDA-regulated organisations continues to apply unchanged until any such replacement takes effect. No enacted change to the lawful-basis or special-category-data provisions currently binding Ontario commercial organisations under PIPEDA was identified.

Outlook

Whether Bill C-36's proposed consent-exception and de-identification provisions advance will depend on the bill's progress through Parliament following its 28 August 2026 Charter Statement, the current stage of which was not located. Organisations should continue to apply PIPEDA's existing consent and lawful-processing requirements pending any enactment.

D2 · Lawful Processing — Full Module Record4 sub-modules · 67 words · 7 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Core access/correction rights exist and are enforced, but portability, explicit restriction/objection, and erasure/de-indexing rights are either absent or only proposed, not yet in force.

Primary frameworkPIPEDA Schedule 1 (Principles 4.9-4.9.4) + proposed Bill C-15 data-mobility provisions
Traffic-light rationale — AmberCore access/correction rights exist and are enforced, but portability, explicit restriction/objection, and erasure/de-indexing rights are either absent or only proposed, not yet in force.

Sub-modules (5)

Access RightGreen

PIPEDA Principle 4.9.4 requires organizations to respond to individual access requests within a reasonable time frame and at minimal or no cost.

Claims (1):

  • Principle 4.9.4 of PIPEDA Schedule 1 requires an organization to respond to an individual's request for access to personal information within a reasonable time frame and at minimal or no cost to the individual.

Rectification And ErasureAmber

PIPEDA's 'challenging compliance' principle allows individuals to dispute accuracy, but the OPC/Federal Court found no extension of accuracy obligations to underlying linked article content, leaving broad erasure/de-indexing rights unresolved.

Claims (1):

  • After investigating a complaint, the OPC found that Google's accuracy-related obligations under PIPEDA do not extend to the underlying content of linked articles, leaving the scope of any de-indexing/erasure right unsettled at the federal level.

Restriction And ObjectionRed

No explicit statutory restriction-of-processing or objection-to-profiling right exists under PIPEDA in force today.

Data PortabilityAmber

Bill C-15 proposes a new Division 1.2 in PIPEDA requiring an organization, on request, to disclose an individual's collected personal information to a designated organization under a data-mobility framework — not yet in force.

Claims (1):

  • Bill C-15 would add a new Division 1.2 to PIPEDA requiring an organization, upon an individual's request, to disclose personal information collected from them to a designated organization under a data-mobility framework, subject to regulations.

Deadlines And Response WindowsAmber

Access requests must be answered within a reasonable time and at minimal or no cost under Principle 4.9.4; no fixed statutory day-count deadline (e.g., 30 days) was identified for PIPEDA generally.

Claims (1):

  • Principle 4.9.4 of PIPEDA Schedule 1 requires an organization to respond to an individual's request for access to personal information within a reasonable time frame and at minimal or no cost to the individual.
Category narrative 77 words

PIPEDA provides an access right and a 'challenging compliance' right functioning as an implicit correction mechanism, with a 'reasonable time and minimal/no cost' response standard (Principle 4.9.4). There is no explicit statutory restriction/objection right or portability right in force; a right to data mobility is only now being proposed via Bill C-15 amendments to PIPEDA. De-indexing/erasure remains contested — the OPC/Federal Court found Google's accuracy obligations do not extend to underlying linked content, leaving right-to-be-forgotten scope unresolved.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (3)
  1. Confirmed OPC — Principle 4.9.4 of PIPEDA Schedule 1 requires an organization to respond to an individual's request for access to personal information within a reasonable time frame and at minimal or no cost to the individual. observed
  2. Confirmed OPC — After investigating a complaint, the OPC found that Google's accuracy-related obligations under PIPEDA do not extend to the underlying content of linked articles, leaving the scope of any de-indexing/erasure right unsettled at the federal level. observed
  3. Probable OPC — Bill C-15 would add a new Division 1.2 to PIPEDA requiring an organization, upon an individual's request, to disclose personal information collected from them to a designated organization under a data-mobility framework, subject to regulations. observed

#

Breach notification and accountability duties are in force and judicially reinforced, but DPIA/DPO/ROPA equivalents remain non-statutory, and enforcement of breach obligations is indirect (referral-based, no OPC fining power).

Primary frameworkPIPEDA Schedule 1 (Accountability, Safeguards) + Breach of Security Safeguards Regulations (2018)
Traffic-light rationale — AmberBreach notification and accountability duties are in force and judicially reinforced, but DPIA/DPO/ROPA equivalents remain non-statutory, and enforcement of breach obligations is indirect (referral-based, no OPC fining power).
D4 · Controller & Processor — Full Module Record7 sub-modules · 90 words · 14 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Adequacy status is currently confirmed and stable, but is explicitly conditioned by the European Commission on further legislative modernization of PIPEDA that has stalled since the death of Bill C-27 in 2025.

Primary frameworkPIPEDA (no dedicated transfer chapter) + EU Commission Decision 2002/2/EC as reviewed 2024
Traffic-light rationale — AmberAdequacy status is currently confirmed and stable, but is explicitly conditioned by the European Commission on further legislative modernization of PIPEDA that has stalled since the death of Bill C-27 in 2025.
D5 · Cross-Border & Adequacy — Full Module Record6 sub-modules · 87 words · 8 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Health sector overlay is robust and actively enforced (first PHIPA AMPs issued 2025); employment-data overlay is a documented, commissioner-flagged legislative gap; credit-scoring/insurance sectoral rules could not be confirmed in this pass.

Primary frameworkPHIPA (health) + CASL (telecoms/e-marketing) + PIPEDA (federally-regulated employment)
Traffic-light rationale — AmberHealth sector overlay is robust and actively enforced (first PHIPA AMPs issued 2025); employment-data overlay is a documented, commissioner-flagged legislative gap; credit-scoring/insurance sectoral rules could not be confirmed in this pass.
D6 · Sectoral Watch — Full Module Record7 sub-modules · 81 words · 8 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Direct marketing and address-harvesting rules are mature and actively enforced via CASL/CRTC precedent, but adtech-specific concepts (opt-out signals, clean rooms, cross-context advertising) have no dedicated CA-ON statutory analogue.

Primary frameworkCASL + PIPEDA (address harvesting provisions)
Traffic-light rationale — AmberDirect marketing and address-harvesting rules are mature and actively enforced via CASL/CRTC precedent, but adtech-specific concepts (opt-out signals, clean rooms, cross-context advertising) have no dedicated CA-ON statutory analogue.
D7 · AdTech & Marketing — Full Module Record6 sub-modules · 84 words · 4 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

No comprehensive AI statute is in force federally following AIDA's death; ADM transparency rights remain proposal-stage only, while active regulator guidance (OPC biometrics, IPC-OHRC AI principles) partially fills the gap without statutory force.

Primary frameworkNone in force (AIDA/CPPA died with Bill C-27, 2025) — governed ad hoc via PIPEDA general principles and IPC/OPC guidance
Traffic-light rationale — RedNo comprehensive AI statute is in force federally following AIDA's death; ADM transparency rights remain proposal-stage only, while active regulator guidance (OPC biometrics, IPC-OHRC AI principles) partially fills the gap without statutory force.
D8 · AI, Biometrics & Automated — Full Module Record6 sub-modules · 104 words · 9 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Red), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

A concrete statutory protection exists for children in provincial care (CYFSA Part X) and regulator attention to children's/EdTech privacy is active, but general age-verification, parental-consent, and dependent-adult regimes were not confirmed in this pass.

Primary frameworkCYFSA Part X (children in care) + PIPEDA general consent principles
Traffic-light rationale — AmberA concrete statutory protection exists for children in provincial care (CYFSA Part X) and regulator attention to children's/EdTech privacy is active, but general age-verification, parental-consent, and dependent-adult regimes were not confirmed in this pass.
D9 · Children's Privacy — Full Module Record5 sub-modules · 77 words · 3 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Ontario's IPC now has and is actively using real monetary-penalty power (PHIPA), but the federal OPC — the primary regulator for most Ontario private-sector data — still lacks direct fining authority, and PIPEDA modernization (to add order-making/AMP powers via the stalled CPPA) remains unresolved.

Primary frameworkPIPEDA enforcement provisions (ss.11-17, s.28) + PHIPA s.61.1 AMP regime
Traffic-light rationale — AmberOntario's IPC now has and is actively using real monetary-penalty power (PHIPA), but the federal OPC — the primary regulator for most Ontario private-sector data — still lacks direct fining authority, and PIPEDA modernization (to add order-making/AMP powers via the stalled CPPA) remains unresolved.
Periodic update · new data 2026-11-04

Enforcement & Redress

Federal enforcement activity touching Ontario-based or Ontario-operating organizations was notably active this period, even though none of it originates with the province's own regulator. The Office of the Privacy Commissioner of Canada closed its investigation into WestJet's cyberattack-related security measures on October 14, 2026, marking the conclusion of that matter. Separately, the OPC secured a commitment from Loblaw to strengthen its security measures following a privacy breach, announced October 26, 2026. Most recently, the OPC opened a new investigation on October 27, 2026 into a breach disclosed by Navigate360, which operates in connection with Crime Stoppers, stemming from a cybersecurity incident that originally occurred in March 2026. A parallel consumer proceeding is reported to allege violations of both PIPEDA and a provincial Consumer Protection Act arising from delayed notification of that breach, though this account rests on third-party press reporting rather than the OPC's own case file, and the precise scope of the investigation itself has not been independently confirmed from the regulator's own materials this period.

Taken together, the closure of the WestJet matter, the Loblaw security commitment, and the newly opened Navigate360 investigation describe an escalating federal enforcement cadence over the period, with three distinct organizations subject to federal privacy-regulator attention in close succession. None of this activity falls to the Information and Privacy Commissioner of Ontario, whose own enforcement mandate remains confined to the public sector under the Freedom of Information and Protection of Privacy Act and the Municipal Freedom of Information and Protection of Privacy Act, and to the health sector under the Personal Health Information Protection Act.

Outlook

Whether the Navigate360 investigation proceeds independently of, or in coordination with, the reported parallel consumer litigation over delayed notification remains to be seen; as scheduled, no outcome has yet been reported for either the investigation or the class proceeding. The closure of the WestJet matter and the Loblaw commitment stand as concluded or settled this period, while Navigate360 remains an open matter going into the next period.

D10 · Enforcement & Redress — Full Module Record6 sub-modules · 122 words · 17 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

No categories match.

Filters combine as OR inside a group and AND across groups.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-04. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 84 claim(s) (85 category placement(s)), 49 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 3 Nov 2026: upheld (13 confirmed against the cited source; 4 could not be checked). An automated, adversarial test run by a second model; no person has assessed the result.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (33 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 9Lawful Processing & Special Dataspecial categories
Art. 13Data Subject Rightsdeadlines and response windows
Art. 15Data Subject Rightsaccess right
Art. 16Data Subject Rightsrectification and erasure
Art. 17Data Subject Rightsrectification and erasure
Art. 18Data Subject Rightsrestriction and objection
Art. 20Data Subject Rightsdata portability
Art. 21Data Subject Rightsrestriction and objection
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 32Controller/Processor Dutiessecurity measures
Art. 33Controller/Processor Dutiesbreach notification
Art. 34Controller/Processor Dutiesbreach notification
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 37Controller/Processor Dutiesdpo requirements
Art. 38Controller/Processor Dutiesdpo requirements
Art. 39Controller/Processor Dutiesdpo requirements
Art. 44Cross-Border & Adequacytransfer mechanisms
Art. 45Cross-Border & Adequacyadequacy received
Art. 46Cross-Border & Adequacyadequacy received
Art. 49Cross-Border & Adequacysccs and bcrs
Art. 77Enforcement & Redressregulator powers and penalties
Art. 78Enforcement & Redresscollective redress and class actions
Art. 79Enforcement & Redressprivate right of action
Art. 80Enforcement & Redressregulator powers and penalties
Art. 82Enforcement & Redressregulator powers and penalties
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties