PIPEDA is Canada's federal privacy law for the private sector. Its full name is the Personal Information Protection and Electronic Documents Act (S.C. 2000, c. 5), and it applies to any organization that collects, uses or discloses personal information in the course of commercial activity. It does not ask where your company is based. It asks whether there is a real and substantial connection to Canada.
For a website owner, the practical answer is short. If you have Canadian visitors, run tracking on that traffic and do it as a business, PIPEDA is probably already in scope. Unlike the GDPR, the logic is not a list of legal bases. In Canada, almost everything is settled inside consent.
PIPEDA took effect in three phases between 2001 and 2004. It rests on ten principles in Schedule 1 of the Act, running from accountability (4.1) to challenging compliance (4.10). Section 5(1) makes those principles mandatory, but only where the text says "shall". Where Schedule 1 says "should", section 5(2) treats it as a recommendation.
Section 5(3) adds a filter that matters for tracking. An organization may collect, use or disclose personal information only for purposes that a reasonable person would consider appropriate in the circumstances. Consent does not cure an inappropriate purpose.
Two kinds of material circulate under the PIPEDA name, and they are easy to mix up. The Act and its regulations are binding. The guidelines of the Office of the Privacy Commissioner of Canada (OPC) are the regulator's reading of the Act, and they shape how it investigates, but they are not statute.
This article marks the difference each time it matters. A rule that comes from the OPC is described as the OPC's position, not as the law.
PIPEDA applies under section 4(1) to organizations that handle personal information in commercial activity, and to federal works, undertakings and businesses. Employee data only falls in when the employer is a federal work or business.
A Canadian court applied the real-and-substantial-connection test to a foreign operator in A.T. v. Globe24h.com (2017 FC 114). The Federal Court took jurisdiction over a company based in Romania because its audience and the impact of its conduct were in Canada.
Quebec, Alberta and British Columbia have their own private-sector laws, and the federal government has recognized them as substantially similar through orders under section 26(2)(b). Those orders exempt organizations from PIPEDA for activity inside the province. They do not cover cross-border flows or federal businesses, so PIPEDA can still apply to the same company on the same day.
The practical rule: if your visitors are in Quebec, read the provincial layer below. If they are spread across Canada, PIPEDA is your baseline, and it is worth choosing a cookie banner that can show the right notice for each region.
Here is the difference most guides get wrong. PIPEDA has no provision equivalent to article 5(3) of the ePrivacy Directive. Nothing in the text says "ask before the first cookie". What the Act asks for is valid consent under section 6.1, and that depends on whether people understand what they are agreeing to.
The OPC fills the gap with two documents. The first is the guidelines for obtaining meaningful consent, published on 24 May 2018 and expected to be followed from 1 January 2019. They set out seven guiding principles and four key elements that must be easy to find: what is collected, who it is shared with, why, and the risk of harm.
The second is the OPC policy position on online behavioural advertising, issued in December 2015 and modified on 11 August 2025.
For behavioural advertising, the OPC accepts opt-out consent, but only if six conditions are all met. In short, people are told clearly about the purposes and the parties involved, the opt-out is easy and takes effect immediately, the data collected is limited and not sensitive, and it is deleted or made anonymous as soon as possible.
The same position says that zombie cookies, supercookies and device fingerprinting should not be allowed at this time. If your stack uses any of these, opt-out is not available to you.
The consent guidelines call for express opt-in consent when information is sensitive, or when the collection or use falls outside what people reasonably expect, or when it creates a meaningful residual risk of significant harm. Health and financial data are the usual examples.
Not in practice. A banner is not required by name, but without one you have a hard time showing meaningful consent, an easy opt-out and a record of the choice. A consent management platform such as AdOpt gives you the notice, the choice and the proof in one place.
Quebec has the strictest layer. Law 25 amended the Act respecting the protection of personal information in the private sector (P-39.1), with phased dates on 22 September 2022, 2023 and 2024. Section 8.1 requires informing people when a technology can identify, locate or profile them, and section 14 requires consent that is clear, free and informed. Administrative penalties can reach CAD 10 million or 2%, and penal fines CAD 25 million or 4%, doubled for repeat offences.
Alberta (PIPA, S.A. 2003, c. P-6.5) has mandatory breach notification in section 34.1. British Columbia's PIPA (S.B.C. 2003, c. 63) has no mandatory private-sector breach notification, to our last check. Neither province has a cookie-specific provision.
PIPEDA gives people a right of access (section 8 and principle 4.9), a right to challenge accuracy and have information corrected, and a right to withdraw consent (4.3.8). It does not give a general right to erasure or to portability. Quebec added portability in section 27 of its law from 22 September 2024.
The full procedure, with deadlines, is in our guide to the PIPEDA DSAR privacy portal.
The OPC investigates complaints, issues findings and can take a case to the Federal Court. It has no power to issue orders or administrative fines. The only money penalties in the Act are the criminal fines in section 28: up to CAD 10,000 on summary conviction and CAD 100,000 on indictment, imposed by a court.
That is why enforcement looks light on paper. The real exposure is a public finding, a court-ordered remedy under section 16, and contract and reputation risk with Canadian customers.
Sections 10.1 to 10.3 require reporting a breach of security safeguards to the OPC and notifying affected people when there is a real risk of significant harm, "as soon as feasible". Records of every breach must be kept for 24 months under the breach regulations (SOR/2018-64).
Earlier reform bills C-11 and C-27 did not pass. The current attempt is Bill C-36 in the 45th Parliament, introduced on 15 June 2026. It would repeal Part 1 of PIPEDA and create a new regime with administrative penalties. As of this writing it is at second reading in the House of Commons and has not received royal assent.
PIPEDA remains the law in force. Do not plan around penalty amounts that have not been confirmed in the bill text.
If your marketing stack uses Google tags, Google Consent Mode lets tags adjust to the visitor's choice.
It can. The test is a real and substantial connection to Canada, applied in A.T. v. Globe24h.com, 2017 FC 114, where the Federal Court took jurisdiction over a Romanian operator because its audience and impact were in Canada. If you target Canadian visitors and track them commercially, assume PIPEDA applies.
No provision says so by name, because PIPEDA has no equivalent of the ePrivacy Directive's article 5(3). The OPC accepts opt-out consent for behavioural advertising only under six cumulative conditions. For sensitive data or unexpected uses, it expects opt-in. A banner is the practical way to meet either standard.
Not under PIPEDA. The OPC has no power to issue orders or administrative fines. It investigates, reports and can take a case to the Federal Court. The money penalties that exist are criminal fines under section 28, up to CAD 10,000 or CAD 100,000, and a court imposes them.
Thirty days from receipt under section 8(3). Section 8(4) allows an extension of up to 30 more days in specific cases, but the notice must go out within the original 30 days. Under section 8(5), silence counts as a refusal, which opens the door to a complaint to the OPC.
Less than you would think, but it is not automatic. The GDPR lets you rely on several legal bases, while PIPEDA centres on consent plus the appropriate-purposes test in section 5(3). Check your notice wording, opt-out conditions, breach record-keeping and the Quebec layer. Our comparison of GDPR, LGPD and CCPA shows where laws diverge.
Understanding the General Data Protection Regulation (GDPR) and its impact on cookies is essential. So, let's break it down, step by step.
Utah UCPA explained: the most business-friendly US state privacy law, dual threshold requirement, opt-out for sensitive data, no right to correct, guaranteed 30-day cure period, and key differences from other state laws.
How does your website handle LGPD? What strategies does it use to comply with the General Data Protection Law? Have you thought about using a cookie notice but don't know if your site has cookies or if it's enough? If you can't answer these questions, be cautious! Your page may be exposed to fines and other sanctions.
Your website have users accessing from Texas? So be ready… the Texas Data Privacy and Security Act is here to shake things up. Don't worry; we've got your back. This guide will walk you through everything you need to know to ensure your website complies with the new regulations.
What the California CCPA/CPRA requires from your Privacy Policy: 12-month lookback, annual updates, Do Not Sell link, sensitive PI disclosures, toll-free number, and the 7 consumer rights.
What the Virginia VCDPA requires from your Cookies Policy: targeted advertising disclosure, consent standards, tracker categories, opt-out mechanisms, and the 30-day cure period explained.
In this article, we'll explore the GDPR foundations and provide practical insights from the basics to more advanced concepts of its legal basis.
How to handle DSARs under the Connecticut CTDPA: 5 consumer rights, opt-outs without mandatory authentication, 60-day appeal deadline, 15-day consent revocation, and AG-only enforcement.
Having a cookie banner on your brand's website has become indispensable for many. However, for e-commerce websites, it has practically become an obligation to have one. This is because this type of website has a technological composition in which cookies are a structural part. Login flow, items in the shopping cart, recommendation showcases, remarketing... Most of them rely on cookies.
Everything about the Oregon OCPA: who must comply, the payment transaction exclusion, 25% revenue threshold, derived data in scope, GPC requirement from January 2026, and elimination of the cure period.
While both regulations share the goal of safeguarding individuals' rights regarding the processing of their personal data, there are some important differences between them. It is crucial to understand these distinctions and their implications, particularly in the context of internet cookies.
Google Consent Mode (GCM) is nothing more than a way for you to integrate the consent you collect from your visitors into Google technologies. In this way, upon receiving this consent information, collection can only occur with authorization, thus complying with the legislation and having direct evidence of compliance as defense for both you and Google.
What the Oregon OCPA requires from your Cookies Policy: opt-out link, GPC from January 2026, opt-out without authentication, derived data in scope, teen protections, and the elimination of the cure period.
Want to understand why there are cookie banners on every website you visit today? This article is for you!
What the Oregon OCPA requires from your Privacy Policy: actively monitored contact channel, detailed third-party descriptions, derived data in scope, GPC from January 2026, and the elimination of the cure period.
What the Iowa ICDPA requires from your Cookies Policy: opt-out for data sales and targeted advertising, opt-out model for sensitive data, no GPC requirement, no specific link text required, and the 90-day cure period.
Using a CMP (Consent Management Platform) is a great way to make efforts to adapt to new privacy regulations like GDPR, LGPD, DPDPA, CCPA and more...
What the Florida FDBR requires from your Cookies Policy: targeted advertising across affiliated sites, opt-out for sensitive data and voice recognition, dark patterns, and tripled penalties.
The Connecticut Data Privacy Act (CTDPA) is a state regulation designed to protect the privacy of Connecticut residents. It also regards cookies, so in this article we will help you understand all about this new privacy regulation.
How to handle DSARs under the California CCPA/CPRA: 7 consumer rights, 45-day deadline, toll-free number required, 12-month lookback, private right of action for breaches, and CPPA enforcement.
What is a DSAR under NHDPA? Complete guide to consumer rights, response deadlines, and building a compliant Privacy Portal for your site.
Despite cookies being more well-known, what is the main difference between cookies and session storage and local storage? Why choose one over the other? This article will help you with these doubts!
What the Florida FDBR requires from your Privacy Policy: annual updates, 6 mandatory content categories, specific notices for sensitive and biometric data sales, and the 7 consumer rights.
Brazilian LGPD - General Data Protection Law brought with it several acronyms and specific terms. Many of them are imported from other countries and regulations. One of them is ROPA (Record Of Processing Activities), adapted in Brazil to Registros das Atividades de Tratamento. An essential document for any DPO, Data Processor.
What are the criteria for this choice, and what are the strengths and weaknesses of each option? Well, we're here to help you because this decision needs to be well thought out!
Discover what the New Hampshire Privacy Act (NHDPA) means for your business. Learn about compliance steps, consumer rights, penalties, and how to simplify it all with AdOpt, a Google-certified CMP.
A privacy policy is a document that outlines how an organization collects, uses, discloses, and manages a customer's data. It's essential for building trust with users and complying with legal requirements. However, if you're not familiar with it, don't worry as we're here to help you.
LGPD is in effect. Despite that, there are still many companies ignoring it, but is that possible? How long can we ignore LGPD?
Learn what your Privacy Policy must contain under the NHDPA. We break down the 8 mandatory elements and how to comply with New Hampshire's data privacy law.
Ignoring Terms of Use and their significance within a website, particularly now with LGPD, is a common mistake that both consumers and website owners frequently commit.
Learn what your TIPA Privacy Policy must include to comply with the Tennessee Information Protection Act from consumer rights and targeted advertising disclosures to the NIST affirmative defense, appeal mechanisms, and how to keep your notice aligned with your operational program.
Learn about how to apply Montana MTCDPA Cookies Policy in your site
Here is a step-by-step explanation of how consent registration works in AdOpt.
How to handle DSARs under the Virginia VCDPA: consumer rights, 45-day response deadlines, the appeal process, free requests twice per year, and how to build a compliant Privacy Portal.
If you're looking to understand how this law impacts businesses in Tennessee, especially those dealing with digital cookies, you're in the right place. This article will simplify the complexities of compliance and make them easy to grasp, even if you're just starting to learn about data privacy.
California CPRA explained: CCPA vs CPRA timeline and key differences, sensitive personal information, sharing of data, CPPA enforcement, GPC requirement, and tripled penalties for minors.
Google Analytics 4 cookie consent explained: what GA4 does when a visitor says no, what changes in your reports, and how to check your setup.
LGPD, GDPR, and CCPA are data privacy regulations. In this article, we discuss their similarities and differences for practical application.
Tired of the ads from that site you visited following you around? Is your computer running slow when accessing a particular website? Want to delete all cookies from a specific service or site?
California CPRA DSAR guide: new rights to correct and limit SPI, opt-out without multiple steps, GPC as valid opt-out, 12-month minor rule, private right of action, and CPPA enforcement.
Oregon OCPA DSAR guide: the L.O.C.K.E.D. rights, opt-out without authentication, derived data in deletion scope, 15-day revocation deadline, GPC from January 2026, and the elimination of the cure period.
The Texas Data Privacy and Security Act (TDPSA) introduces sweeping changes to how businesses collect, use, and disclose personal data—and your privacy policy is now a frontline compliance tool. This article is a comprehensive guide for any company serving Texas residents, explaining how to align your privacy practices with the new legal standards.
Axeptio acquires Brazil's AdOpt, expanding global reach in consent management and LGPD compliance.
Everything you need to know about the Florida Digital Bill of Rights (FDBR): who must comply, the $1 billion threshold, 7 consumer rights, FIPA vs FDBR explained, penalties, and cookies.
Iowa ICDPA explained: the longest response deadline of all US state privacy laws (90 days), 90-day cure period, opt-out for sensitive data, limited deletion scope, no right to correct, and how it compares to UCPA, VCDPA, and OCPA.
16 Oct 2026
Address: 7345 W Sand Lake Road, Ste 210 Office 5898 Orlando, FL 32819
15 Rue du Général Campredon, 34000 Montpellier, France
207 Rue de Bercy, 75012 Paris, France
EIN: 86-3965064
Phone: +1 (407) 768-3792
AdOpt
Resources
Product
Certifications