PIPEDA Compliance: A Practical Guide for Canadian Businesses

PIPEDA compliance means following the 10 fair information principles in the Personal Information Protection and Electronic Documents Act, Canada’s federal privacy law for the private sector. In practice, you get meaningful consent, protect the personal information you hold, and report serious breaches. In 2025-26, the Office of the Privacy Commissioner of Canada (OPC) received 696 breach reports from businesses. The OPC found that 78% of those business breaches involved unauthorized access.

The OPC says those reports affected 20,328,495 Canadians. Look again at that 78% figure. Most privacy failures at Canadian businesses start with someone getting into systems they shouldn’t. That makes compliance largely a security job, and a small team can get it under control. Whatever you’ve heard about Bill C-36, PIPEDA is still the rulebook in 2026.

PIPEDA Is Still the Law You’re Measured Against in 2026

PIPEDA has governed how private-sector organizations handle personal information in Canada since 2000, and it remains in force today. It sets the rules for collecting, using and disclosing personal information during commercial activity. Being compliant means your daily habits match those rules. That covers everything from the sign-up form on your website to the customer spreadsheet on a sales rep’s laptop.

Size doesn’t buy you an exemption. A small bookkeeping firm carries the same core duties as a national retailer, scaled to the data it holds.

The law also gives individuals real rights. Do Canadians have a right to privacy when dealing with businesses? Yes. Under PIPEDA, people can see the personal information you hold about them, ask you to correct it, withdraw consent and complain to the OPC. Federal government institutions follow a separate law, the Privacy Act.

PIPEDA Covers Most Commercial Activity, With Narrow Exemptions

PIPEDA reaches further than most owners expect, because it follows the data as well as the business. It applies to businesses across most of Canada, to all businesses in the three territories, and to personal information that crosses provincial or national borders. Federally regulated businesses, such as banks, airlines and telecom companies, fall under it nationwide. Foreign companies can be covered too, when they have a real and substantial connection to Canada.

The table below shows common situations and whether PIPEDA applies.

SituationDoes PIPEDA apply?
Commercial activity in Ontario, Saskatchewan or ManitobaYes
Any business in Yukon, NWT or NunavutYes
Federally regulated business anywhere in CanadaYes
Customer data sent across a provincial or national borderYes
Foreign company with a real and substantial Canadian connectionYes
Federal government institutionNo, the Privacy Act applies
Personal or household useNo
Journalistic, artistic or literary purposesNo
Non-commercial work of a nonprofit or political partyGenerally no
Core activities of universities and hospitalsGenerally no

Read the exemptions narrowly. A nonprofit’s donation drives and programs usually sit outside PIPEDA. Activity with a commercial character can bring it back in, such as selling or renting a donor list. The exemption follows the purpose of the activity, whatever the organization calls itself.

Alberta, BC and Quebec Run Their Own Privacy Laws

Three provinces have private-sector privacy laws that the federal government has deemed substantially similar to PIPEDA. Alberta and British Columbia each have a Personal Information Protection Act (PIPA). Quebec has its own private-sector law, updated by Law 25. Ontario has a substantially similar law for health information only, the Personal Health Information Protection Act (PHIPA).

Here is how the main laws divide the work.

Where or whatMain lawWhat it covers
AlbertaAlberta PIPAPrivate-sector data handled within Alberta
British ColumbiaBC PIPAPrivate-sector data handled within BC
QuebecQuebec law, as amended by Law 25Private-sector data handled within Quebec
Ontario health informationPHIPAPersonal health information
Rest of Canada and cross-border dataPIPEDACommercial activity and data crossing borders

Border crossings catch many businesses off guard. Provincial laws cover activity inside the province. Once data moves across a provincial or national line, PIPEDA applies to that transfer. A Calgary retailer storing customer data on a US-hosted platform deals with both Alberta PIPA and PIPEDA. Federally regulated businesses stay under PIPEDA in every province.

Privacy law is rarely the only rulebook you follow. For most Canadian SMBs, the five regulations to know are PIPEDA, the provincial privacy laws in Alberta, BC and Quebec, health laws such as PHIPA, Canada’s Anti-Spam Legislation (CASL) for marketing email, and the PCI DSS standard if you take card payments. Listing which ones touch your business is the first step in sorting out your cybersecurity compliance requirements.

Personal Information Is Broader Than Names and Email Addresses

Your business almost certainly holds more personal information than you think, including IP addresses and video images. PIPEDA covers any information about an identifiable individual. If a piece of data could reasonably be linked back to a person, treat it as personal information.

Pyramid ranking fitness studio data from newsletter list at low risk up to injury notes as the most sensitive information

Ranking your own data this way tells you where express consent and encryption matter most, and where lighter handling is reasonable.

Business contact information is the main exclusion. A name, job title, work phone and work email used to reach someone about their job sits outside PIPEDA. Use that same work email to market personal products to the person, and you’re back under the law.

Picture a local fitness studio and what it holds. Security footage of the front desk is personal information, because members can be identified in it. The newsletter list of names and emails is personal but fairly low risk. Credit card details on file are sensitive. Injury notes from intake forms are the most sensitive data in the building.

Each of those deserves different handling. The studio can reasonably rely on implied consent to use an email address for booking confirmations. The injury notes call for express consent, access limited to the trainers who need them, and encryption wherever they’re stored. The rule of thumb is simple. The more harm a leak could cause, the stronger your consent and safeguards need to be.

So what qualifies as sensitive personal information? PIPEDA has no closed list. Health and financial records are almost always sensitive. Context matters too. A magazine’s subscriber list looks harmless, until the magazine is about a specific medical condition.

The 10 Fair Information Principles, Translated for Small Businesses

Each of PIPEDA’s 10 fair information principles turns into a task you can hand to a named person. Together, the principles in Schedule 1 are the compliance requirements. The OPC lists them as accountability through challenging compliance. The table below shows what each requires and what it looks like in a small business.

PrincipleWhat it requiresSMB example
1. AccountabilitySomeone is responsible for privacyOffice manager named as privacy officer
2. Identifying PurposesExplain why you collect data, at or before collectionSign-up form says what the email is for
3. ConsentGet meaningful consent to collect, use and discloseSeparate, unticked box for marketing
4. Limiting CollectionCollect only what you needDate of birth removed from the quote form
5. Limiting Use, Disclosure and RetentionUse data only as stated, keep it only as neededOld leads purged on a set schedule
6. AccuracyKeep data accurate enough for its purposeAddresses confirmed before shipping
7. SafeguardsProtect data in line with its sensitivityMFA on email and the CRM
8. OpennessMake your privacy practices easy to findPlain-language policy linked in the footer
9. Individual AccessLet people see and correct their dataDedicated inbox for access requests
10. Challenging ComplianceGive people a way to complainComplaint steps listed in your policy

Three principles carry the most weight for a small team. Accountability, safeguards and individual access each need an owner and a routine. A sentence in your privacy policy doesn’t run itself.

Meaningful Consent Means People Know What They Agreed To

A checkbox alone doesn’t prove consent. Under section 6.1, consent is valid only when the person would reasonably understand what they’re agreeing to. That means they grasp the nature, purpose and consequences of what you’ll do with their information.

Start with the wording. Say what you collect, why, who you share it with and what happens as a result. Use language a customer can read in seconds. Burying the important parts deep in a terms page fails the test.

Next, match the type of consent to the sensitivity of the data. Express consent is a clear, active yes, like ticking an empty box. Implied consent works when the use is obvious and the data isn’t sensitive, such as using a shipping address to ship an order. Health details, financial information and any use a customer would be surprised by call for express consent.

Make withdrawal easy too. People can withdraw consent, subject to legal or contractual limits. Explain what withdrawing means for them, then act on it in every system where their data lives. Keep a record of when and how each person consented, and when they withdrew.

Treat marketing email as its own consent. CASL is a separate law from PIPEDA, enforced by the CRTC. Commercial electronic messages need consent, identification of the sender and a working unsubscribe mechanism. A customer who accepted your privacy policy has not signed up for your newsletter.

Safeguards Are Where Most SMBs Fall Short

Unauthorized access sits behind most of the breaches businesses report to the OPC, so weak safeguards are the likeliest way to land on the regulator’s desk. The good news for a small team is that PIPEDA asks for safeguards proportional to the sensitivity of the data. You don’t need a bank’s security budget to protect a newsletter list. You do need serious controls around health notes, payment data and ID documents.

78% of business breaches reported to the OPC in 2025-26 involved unauthorized access

Because most breaches start with a login, controls like MFA and same-day offboarding give small teams the biggest return on effort.

Security Controls That Stop Unauthorized Access

Unauthorized access can mean a phished password, a shared login, or a former employee whose account was never closed. A firewall and antivirus won’t stop any of those. These controls do most of the work against unauthorized access:

  • Multi-factor authentication (MFA) on email, cloud storage, the CRM and online banking.
  • Role-based access, so each person sees only the data their job needs.
  • Encryption on laptops, phones and any files holding sensitive data.
  • Same-day offboarding that removes every account when someone leaves.
  • Short, regular staff training on phishing and safe data handling.
  • A quick privacy impact assessment before you adopt a new tool that touches personal data.

None of these require a large budget, and together they reduce cyber risks more than any single product. They’re the core of any serious effort to protect your customers’ data. Back them with a written data breach response plan that names who does what when something goes wrong. Deciding roles in advance saves hours on the worst day.

Retention Rules: Old Data Is Risk You Don’t Need

Personal information should be kept only as long as you need it for the purpose you collected it, then destroyed or anonymized. PIPEDA doesn’t hand you fixed retention periods, so set your own and write them down. A customer file from a long-closed account earns your business nothing. If it’s stolen, it still counts as a breach.

Build retention into your routine. Pick a date each quarter to purge old leads, closed accounts and expired files. Note what was deleted and when, so you can show the policy is followed.

Vendors: You Stay Accountable for Their Mistakes

Handing personal information to a vendor for processing doesn’t hand off your responsibility. Under the accountability principle, your business stays responsible for that data. You’re expected to use contracts or other means to make sure the vendor protects it to a comparable standard.

Start by listing every vendor that touches personal data, such as payroll, your email platform, cloud storage and your IT provider. Check where each one stores data, since a server outside Canada brings cross-border rules into play. A simple vendor risk assessment process lets you rank vendors by the sensitivity of what they hold. Then make sure contracts cover security expectations and prompt notice if the vendor has a breach.

Breach Reporting Turns on the RROSH Test and a 24-Month Log

Every breach of security safeguards must be logged, but only breaches that create a real risk of significant harm (RROSH) must be reported to the OPC and affected individuals. That obligation has been in place since November 1, 2018. Significant harm includes outcomes like identity theft, financial loss, humiliation and damage to reputation. To judge the risk, weigh how sensitive the data is and how likely it is to be misused.

Five breach response steps under PIPEDA compliance rules, from containing the breach to recording it in a log

Steps one and two often happen within hours; the log entry must still be kept for 24 months even when no report is filed.

When a breach happens, work through these steps in order.

  1. Contain it. Reset passwords, revoke access and isolate affected systems.
  2. Assess the risk. Ask what data was involved, who has it now and how it could be misused.
  3. Report to the OPC if the RROSH threshold is met. The OPC expects reports as soon as feasible after you determine a breach occurred, even before you know every detail.
  4. Notify affected individuals. Tell them directly where possible, with enough detail to protect themselves.
  5. Record the breach, whatever its size. Keep a record of every breach, including those below the RROSH threshold, for 24 months from the day you determine it happened.

PIPEDA sets no fixed deadline in hours. “As soon as feasible” means you shouldn’t wait for a complete investigation before reporting. The record-keeping duty is separate from reporting. A lost unencrypted laptop with no sensitive data still belongs in your log. For the mechanics of filing, see our walkthrough on how to report a data breach.

Access Requests Need an Answer Within 30 Days

When someone asks what personal information your business holds about them, PIPEDA gives you 30 days to respond, at minimal or no cost to them. They can also ask you to correct inaccurate information, withdraw consent and complain to the OPC if they’re unhappy with your answer. Each right needs a process behind it.

A workable intake routine fits on one page. Use one channel for requests, such as a privacy email address named in your policy. Verify the person’s identity without collecting more data than you need. Then search every system on your data map, gather what you find and reply in plain language. Log the date received and the date answered.

Your data map is what makes the 30-day window realistic. Without one, staff end up searching inboxes and shared drives by memory. When someone asks for a correction, fix the record, and pass the update to any vendor that holds a copy where it makes sense.

PIPEDA Plays Out Differently in Finance, Health, Marketing and Nonprofits

The same 10 principles land differently by sector, because sensitivity and overlapping laws change what reasonable protection looks like.

Finance and Lending

Financial services draw more breach reports than other sectors. In 2024-25, the OPC found finance was the sector hit hardest, accounting for 172 of the 555 breach reports that involved unauthorized access. Financial data is sensitive by default. Expect to need express consent, MFA on every account that touches client records, and tight limits on who can export data. Banks are federally regulated, so PIPEDA follows them into every province.

Health and Wellness Clinics

Health information is about as sensitive as personal data gets. In Ontario, personal health information falls under PHIPA. Elsewhere, a private clinic’s client data sits under PIPEDA or its provincial equivalent. Either way, get express consent, keep access to the people who treat the client, and check where your booking and charting software stores data. A US-hosted tool brings cross-border rules into the picture.

Email Marketing

Marketing teams answer to two laws at once. CASL governs whether you can send the message, and the CRTC sets the stakes high. Under CASL, the maximum penalty is $10 million per violation for a business. PIPEDA governs the list itself as personal information. That means a stated purpose, retention limits and safeguards on your email platform. A purchased list fails on both fronts, since you can’t show the people on it agreed to hear from you.

Nonprofits and Charities

Most nonprofit activity sits outside PIPEDA, but donors still expect their data to be handled with care. Commercial activities, like selling or trading a donor list, can pull your organization under the law. If you operate in Alberta or BC, check the provincial law as well. Applying PIPEDA’s principles to donor data, even where the law doesn’t strictly require it, protects the trust your donations depend on.

Your PIPEDA Compliance Checklist in 10 Steps

This checklist turns the principles into work you can schedule. Copy it into your task tracker and assign an owner to each line.

  1. Appoint a privacy officer. Name one person who owns privacy and put their contact details in your policy.
  2. Map your data. List what personal information you collect, where it lives, who can see it and which vendors hold it.
  3. Cut what you don’t need. Remove form fields and data stores that serve no stated purpose.
  4. Publish a plain-language privacy policy. Cover what you collect, why, who you share it with, how long you keep it, how to request access and how to complain.
  5. Fix your consent flows. Use express consent for sensitive data and separate consent for marketing email.
  6. Set retention rules. Write a retention period for each data type and schedule regular purges.
  7. Apply safeguards to match sensitivity. Start with MFA, access controls, encryption and fast offboarding.
  8. Manage your vendors. Assess each one and put security and breach-notice terms in contracts.
  9. Train your staff. Cover phishing, data handling and how to escalate a suspected breach.
  10. Keep a breach log and audit yearly. Log every incident for 24 months, and review the whole program at least once a year.

OPC Fines Are Small Next to the Cost of a Breach

The breach itself is the bigger threat to your budget, not the fine. IBM puts the average cost of a data breach in Canada at a record CA$7.11 million in its 2026 report. The Canadian Press, covering the same report, noted the average Canadian breach took 205 days to identify and contain. That’s more than half a year of exposure before anyone closes the door.

Maximum PIPEDA fine of $100,000 compared with the CA$7.11 million average cost of a data breach in Canada

The fine applies only to knowing violations, while breach costs hit any business, which is why safeguards deserve the bigger share of budget.

Fines exist, but they’re narrow. Under the Act, knowingly breaking the breach-reporting, record-keeping or whistleblower rules, or obstructing the Commissioner, can bring fines of up to $10,000 on summary conviction or up to $100,000 on indictment. Add lost customers and a damaged reputation to a breach, and the $100,000 maximum fine looks like the smallest line on the bill.

The OPC itself works as an ombudsman. It investigates complaints and makes recommendations rather than issuing fines. It is also busier than ever. The OPC reported 3,044 PIPEDA complaints in 2025-26, up 109% from the year before. The OPC’s fiscal year runs from April to March.

After an OPC complaint, a matter can go to the Federal Court. The court can order you to change your practices and award damages to the people affected.

Bill C-27 Died, and Bill C-36 Is Still Only a Proposal

Canada has tried to replace PIPEDA twice, and neither attempt has become law. Bill C-27, introduced on June 16, 2022, would have replaced PIPEDA with the Consumer Privacy Protection Act. It died on the Order Paper when Parliament was prorogued on January 6, 2025.

Timeline of Bill C-27 introduced in 2022 and dying in 2025, then Bill C-36 reaching first reading on June 15, 2026

A bill can stall at any reading, so until Royal Assent the existing federal privacy law stays the standard regulators apply.

Bill C-36 received first reading on June 15, 2026. It would create the Protecting Privacy and Consumer Data Act, repeal Part 1 of PIPEDA, and move private-sector privacy oversight to a new Digital Safety and Data Protection Commission of Canada. The proposed penalties are far steeper than PIPEDA’s. As introduced, Osler’s analysis shows the bill would allow administrative penalties of up to the greater of $10 million or 3% of gross global revenue. Offence fines could reach the greater of $25 million or 5% of gross global revenue.

Don’t rebuild your program around a bill that hasn’t passed. As of around September 20, 2026, Bill C-36 had passed only first reading. The sensible move is to comply fully with PIPEDA now. A business with a data map, solid safeguards and a breach log is already doing the groundwork any future law will demand. Review your program as the bill moves, and adjust once the final text is known.

Quick Answers

Do Canadians have a right to privacy?

Yes. Under PIPEDA, Canadians can access the personal information businesses hold about them, correct it, withdraw consent and complain to the OPC. Federal government institutions are covered by the Privacy Act instead.

What are the top 5 compliance regulations for Canadian businesses?

For most Canadian SMBs, the five to know are PIPEDA, the provincial privacy laws in Alberta, BC and Quebec, health laws such as Ontario’s PHIPA, CASL for marketing email, and PCI DSS if you take card payments.

What qualifies as sensitive personal information?

PIPEDA has no closed list, but health and financial records are almost always sensitive. Context matters too, so information that seems harmless can become sensitive depending on what it reveals about a person.

Does PIPEDA have 8 privacy principles?

No. PIPEDA has 10 fair information principles, set out in Schedule 1. Lists of eight come from a different framework, so Canadian businesses should work from the 10.

Start With Three Moves This Week

You don’t need to finish the checklist this month. Take the first three steps this week. Name your privacy officer, list where your customer data lives, and open a breach log, even if it’s a simple spreadsheet. Those three alone put you ahead of many businesses your size.

Your next question is how your safeguards hold up against unauthorized access, the risk behind 78% of the business breaches reported to the OPC. RiskAware’s free cybersecurity score shows where your cyber risks sit. If you’d rather talk it through, a discovery call with the team that hundreds of SMBs and nonprofits already trust is the fastest way to find your gaps and close them.

Share the Post: