Web analytics, cookies, tag managers, CMPs, ad pixels, and session-replay tools as deployed on websites and apps targeting Quebec residents. Sectoral rules (health, finance, employment) are touched only where they intersect with the analytics layer. French-language obligations under the Charte de la langue française apply on top.
Applicable laws
The legal framework that governs personal data processing here.
National addons
Country-specific statutes layered on the EU baseline.
- § 3.1 Privacy Officer (Personne responsable de la protection des renseignements personnels) — mandatory for ALL businesses, no headcount threshold (Phase 1, 2022)
- § 3.5 Confidentiality incident reporting — mandatory notification to CAI + affected individuals when risk of serious injury (Phase 1, 2022)
- § 3.2 Privacy policies — must be published in clear plain language; governance framework mandatory (Phase 2, 2023)
- § 3.3 Privacy Impact Assessment (Évaluation des facteurs relatifs à la vie privée, ÉFVP) — mandatory before any high-risk processing or new IT system (Phase 2, 2023)
- § 14 Consent — must be express, free, informed, and granular for each purpose; bundled consent prohibited (Phase 2, 2023)
- § 17 Cross-border transfer impact assessment — mandatory written analysis before transferring personal information outside Quebec (Phase 2, 2023)
- § 27 Right to data portability — structured, commonly used, technological format (Phase 3, 2024)
- § 8.1 Profiling and automated decision-making — mandatory disclosure + opt-out for individual decisions based solely on automated processing
- § 90.1 Administrative monetary penalties up to CAD $10M or 2% of worldwide turnover (whichever is higher)
- § 91 Penal fines up to CAD $25M or 4% of worldwide turnover (whichever is higher) — among the highest in North America
- § 51-52.1 Inscriptions on a product, signage, commercial publications, websites — must be in French; other languages permitted only if French is at least as prominent
- § 52.1 Websites and social media — French version mandatory for any business doing business in Quebec
- § 205-208 Penalties — fines up to CAD $30,000 per offense for legal persons; doubled on repeat
- § 4-9 Collection — purpose limitation, minimization, transparency
- § 10-13 Use and disclosure — secondary-purpose restrictions; commercial-prospecting limits
- § 18-22 Retention, accuracy, and destruction obligations
Regulators
Supervisory authorities that interpret and enforce privacy law here.
Coordination body
- 2023-09-22 · Phase 2 transition — CAI published guidance on consent granularity, governance frameworks, and ÉFVP (PIA) methodology — aligned closely with EDPB guidelines on GDPR Art 7 and 35.
- 2024-06 · Cross-border transfers — CAI guidance on § 17 transfer impact assessments — written analysis required regardless of destination, including transfers to other Canadian provinces.
- 2025-08 · First Notice of Non-Compliance published — CAI issued its first publicly named Notice of Non-Compliance under Law 25 enforcement powers — signals end of the educational grace period.
Notable enforcement
The CAI ramped up enforcement gradually after Phase 1 (2022). The first major Law 25 inquiries opened in 2023 once Phase 2 substantive obligations applied. Phase 3 readiness checks dominated 2024 communications. The first publicly named Notice of Non-Compliance was issued in August 2025 — the CAI signalled that the educational grace period is over. Penalty exposure is substantial on paper (CAD $10M / 2% admin; CAD $25M / 4% penal — comparable to GDPR), but headline fines remain rare; the CAI's pattern so far is corrective orders, public naming, and follow-up audits rather than maximum monetary sanctions.
GA4 status
GA4 is usable in Quebec only with prior, express, granular consent under Law 25 § 14. The CAI has not issued a GA4-specific decision but its guidance on consent + § 17 cross-border transfer assessment aligns closely with the GDPR baseline applied to Google Analytics in the EU. Privacy notice + consent banner must be available in French per the Charter of the French Language. Server-side hosting in Canada and IP-anonymization are recommended supplementary measures.
| DPA | Stance |
|---|---|
| CAI | No GA4-specific ruling. Generic guidance: explicit consent for non-essential analytics, § 17 transfer impact assessment for US-hosted processing, privacy policy must list categories of recipients including Google. French-language disclosure mandatory. |
Cross-border transfers + Schrems II
Quebec Law 25 § 17 imposes a unique cross-border transfer impact assessment on any transfer of personal information outside Quebec — including to other Canadian provinces, not only to non-adequate jurisdictions. The controller must conduct and document a written analysis weighing the sensitivity of the data, the purposes, the protection measures, and the legal regime in the destination jurisdiction. CAI guidance (Jun 2024) clarifies the methodology. The EU-US Data Privacy Framework is not directly relevant — Quebec applies its own assessment regardless of US adequacy status under EU law.
No mandatory contractual template. CAI accepts contractual safeguards drafted to reflect the § 17 assessment. Many enterprises use IAPP / OPC model clauses adapted with Quebec-specific addenda (Privacy Officer designation, French-language data-subject communication, breach notification to CAI within prescribed time).
Employee data
Key thresholds
Vendor signals
Red / yellow / green markers are an editorial reading of public regulator guidance and published enforcement actions, applied to vendor behavior we can observe or that the vendor documents. They are not legal conclusions, not endorsements, and not advice about your specific processing. Configuration changes the picture — a "yellow" vendor in one configuration may be defensible in another.
Analytics tools · 4 · 0 green · 3 yellow · 1 red
| Vendor | Status | Rationale |
|---|---|---|
| YELLOW | Visitor ID cookie + cross-suite stitching with Experience Platform. DPIA strongly recommended; configure ECID + IP obfuscation. | |
| YELLOW | EU residency available on paid plans; default cloud is US. Persistent user IDs require config + DPA + DPF chain. | |
| YELLOW | EU cloud helps but session recording + autocapture default to PII collection. Disable autocapture and recordings or self-host for green. | |
| RED | Auto-capture grabs every click and form value — broad PII risk under GDPR Art 5(1)(c) data minimization. |
Consent management platforms · 5 · 5 green · 0 yellow · 0 red
| Vendor | Status | Rationale |
|---|---|---|
| GREEN | Danish-based, EU-hosted. Auto-blocks third-party scripts pre-consent — verify your manual scripts also gate. | |
| GREEN | Italian-based, EU-hosted. Free tier limits 5k pageviews/mo; granular per-vendor controls require paid plan. | |
| GREEN | Open-source, self-hosted. No managed updates — site owner maintains vendor list. | |
| GREEN | GDPR + CCPA + multi-region templates available. Common config error: GDPR/CCPA mode mismatch — verify per-region defaults. | |
| GREEN | German-based, EU-hosted. v3 SDK required for Consent Mode v2; TCF flow can over-collect for non-AdTech sites. |
Ad pixels · 3 · 0 green · 0 yellow · 3 red
| Vendor | Status | Rationale |
|---|---|---|
| RED | Loads pre-consent if naively placed; cross-device matching broad. Block until consent + IAB TCF string set. | |
| RED | Schrems II concerns persist; advanced matching hashes PII but does not fix EU→US transfer problem. | |
| RED | PRC-parent ownership flagged by Italian Garante and EDPB; transfers to China contested. Consent + risk acknowledgement required. |
Server-side · 3 · 2 green · 1 yellow · 0 red
| Vendor | Status | Rationale |
|---|---|---|
| GREEN | EU-only datacenters strong for FR/DE compliance; per-event pricing scales steeply at high traffic. | |
| GREEN | EU server containers handle the routing — but server-side tagging does NOT auto-fix consent. CMP must still gate browser-side pings. | |
| YELLOW | "EU server" ≠ EU data — clients still transmit to Google ad backends downstream. Use only for Google-ecosystem first-party-routing. |
Compare with neighbors
Side-by-side rule comparison.
Common questions
How is Quebec Law 25 different from PIPEDA?
When did Law 25 enter into force?
Do I need a French-language privacy notice?
Do I need a Privacy Officer if I'm a small business?
What is the § 17 cross-border transfer impact assessment?
What is the consent age in Quebec?
What fines does the CAI impose?
Is consent under Law 25 the same as under GDPR?
Does Law 25 apply if my business is outside Quebec?
What is an ÉFVP and when do I need one?
// EDITORIAL · NOT LEGAL ADVICE This page summarises Quebec's privacy framework as of 2026-05-05. Rules vary by sector, establishment, and DPA position. For binding interpretation, consult counsel admitted here.