ClearBreach

← Guides·Which law applies to you →

Your SituationWe want our privacy basics in place →

PIPEDAAll sectors

PIPEDA Compliance Requirements for Canadian Organizations

By Yong DuPublished Reviewed

Share on LinkedIn

The ten ongoing obligations every organization under PIPEDA must meet, whatever its size or industry.

PIPEDA compliance requirements for Canadian organizations

PIPEDA requires every organization it covers to meet ten ongoing obligations. They apply continuously, whether or not a breach has occurred or a complaint has been received. The OPC's 2025–26 survey found a substantial minority of consumer-facing businesses still missing the basics: more than a quarter have no privacy officer.


Who must comply with PIPEDA

PIPEDA applies to all private-sector organizations that collect, use, or disclose personal information in the course of commercial activity, regardless of size. There is no small-business exemption.

Alberta and British Columbia have provincial PIPA legislation deemed substantially similar to PIPEDA. Organizations operating purely within those provinces may be governed by provincial legislation for intraprovincial activity, but cross-border or interprovincial commercial activity triggers PIPEDA. Federally regulated sectors (banking, telecommunications, transportation, broadcasting) are subject to PIPEDA regardless of province.


The ten compliance obligations under PIPEDA

1. Accountability, Principle 1 Designate one or more individuals accountable for your organization's compliance with PIPEDA. That person must be named, available to receive complaints, and actually involved in privacy decisions. The OPC's 2025–26 survey found 28% of consumer-facing businesses have none. → Do I need a designated privacy officer?

2. Identifying purposes, Principle 2 Document why you are collecting each type of personal information before you collect it. Collection for one purpose does not authorize use for another.

3. Consent, Principle 3 Obtain meaningful consent for the collection, use, and disclosure of personal information. Individuals must understand what they are consenting to. Organizations should generally seek express consent where the information is likely to be sensitive (clause 4.3.6); implied consent can be appropriate where the information is less sensitive and the use is one the person would reasonably expect.

4. Limiting collection, Principle 4 Collect only the personal information necessary for the stated purpose. Collecting more than you need for operational convenience is not compliant.

5. Limiting use, disclosure, and retention, Principle 5 Use and disclose personal information only for the purpose for which it was collected, or as consented. Retain it only as long as necessary. Establish retention schedules and follow them.

6. Accuracy, Principle 6 Keep personal information accurate, complete, and up to date as necessary for its intended use.

7. Safeguards, Principle 7 Protect personal information with security safeguards appropriate to the sensitivity of the information. The standard is proportionate, a medical clinic holding health records requires stronger safeguards than a retail business holding mailing addresses. Encryption, access controls, and staff training are the OPC's baseline expectation for organizations holding sensitive personal information. The OPC's 2025–26 survey found 45% of consumer-facing businesses do not use encryption.

Having safeguards in place is not enough. During an OPC or OIPC investigation, you will be asked to produce evidence that those safeguards existed and were actively maintained before the incident occurred. Without that documentation, it is hard to show your safeguards were reasonable, whatever was actually in place.

What to retain to demonstrate Principle 7 compliance:

  • Access control records: documentation of who had access to systems containing personal information, and when that access was granted or revoked. Terminated employee access removal records carry particular weight with investigators.
  • Authentication records: records showing multi-factor authentication was enabled on accounts with access to personal information. Regulators have cited missing multi-factor authentication as a safeguard failure in ransomware and credential theft cases.
  • Patch and update logs: records of software updates and security patches applied to systems holding personal information. Unpatched systems appear repeatedly in OPC enforcement decisions as evidence of inadequate safeguards.
  • Encryption records: your encryption policy and configuration records showing encryption was applied to devices and systems holding personal information.
  • Staff training records: documentation of when employees completed privacy and security training, what the training covered, and which version of materials was in use at the time.
  • Incident response plan: a dated copy of your plan showing it existed before any incident occurred. Version history strengthens this.
  • Vendor security documentation: contracts with service providers that include security requirements, and records of any security reviews of those vendors.

No law sets a period for these; keeping them at least two years matches the federal breach-record period. If a breach occurs, preserve them immediately: they become the main evidence of your safeguards at the time.

8. Openness, Principle 8 Publish a privacy policy describing your organization's practices, the type of personal information held, how it is used, and how individuals can access their information or file a complaint. The information must be readily available (clause 4.8.1); for most organizations, that means a page on their website.

9. Individual access, Principle 9 Respond to access requests within 30 days (s.8(3)). Extensions of up to 30 more days are permitted in limited circumstances, by notice to the individual within the first 30.

10. Challenging compliance, Principle 10 Maintain a complaint handling procedure (clause 4.10.2). The OPC's 2025–26 survey found 23% of consumer-facing businesses have none.


What the OPC looks for in an investigation

When the OPC investigates a PIPEDA complaint, it will request your privacy policy, relevant internal procedures, and evidence that the specific obligation at issue is being met. The joint federal, Alberta and BC guidance on privacy management programs (April 17, 2012) builds a program on a designated privacy officer and support from the top, then program controls such as documented policies, staff training and complaint handling. Being able to produce them as soon as a complaint arrives is the simplest evidence that a program exists.

Complaints are rising: in 2025–26 the OPC received 3,044 PIPEDA complaints, up 109% on the year before, and closed 302 through early resolution, its shorter process.


Common compliance gaps

The OPC's 2025–26 survey of 800 consumer-facing businesses found:

  • 38% do not regularly train staff on privacy
  • 28% have no designated privacy officer
  • 26% have no documented staff privacy policies
  • 23% have no complaint handling procedure
  • 45% do not use encryption

These organizations are not failing to build enterprise-grade compliance programs. They are missing the basic documentation the OPC expects to find on first contact during an investigation.


Assess your compliance posture

A structured assessment against all ten PIPEDA principles is the most reliable way to identify gaps before a complaint or investigation occurs. ClearBreach's compliance assessment shows where you stand in all ten compliance areas, the gaps and the next step for each, with the documents to close them.

See a complete assessment →



This guide covers PIPEDA compliance obligations for private-sector organizations. It does not cover Quebec's Act respecting the protection of personal information in the private sector (Law 25 / Bill 64).

If your organization handles personal health information under provincial health legislation, additional obligations may apply that are not covered here.

Privacy case of the month

Once a month, a five-minute read: a real case a Canadian privacy commissioner investigated, what went wrong, and what to check in your own organization so it doesn't happen to you. Written for organizations under federal, Alberta and BC privacy law. Not written for Quebec.

We send one email to confirm. Nothing else arrives until you confirm, and an unconfirmed address is deleted after 7 days. Sent by ClearBreach Technologies Inc. Mailing address and contact details · Privacy policy

Frequently asked questions

Does PIPEDA compliance apply to small businesses?

Yes. PIPEDA applies to all private-sector organizations engaged in commercial activity in Canada, regardless of size. There is no small-business exemption. Organizations in Alberta and BC may be governed by provincial PIPA for intraprovincial activity, but any cross-border or interprovincial commercial activity triggers PIPEDA regardless of province.

What are the main PIPEDA compliance requirements?

PIPEDA's ten principles require organizations to: designate a privacy officer, document the purpose of collection before collecting, obtain meaningful consent, collect only what is necessary, use and retain personal information only as appropriate, maintain accuracy, protect personal information with appropriate safeguards, publish a privacy policy, respond to access requests within 30 days, and maintain a complaint handling procedure.

What does the OPC look for in a PIPEDA compliance investigation?

The OPC expects a named privacy officer, a written privacy policy that describes how individuals can file a complaint, documented consent practices, appropriate safeguards for the sensitivity of the information held, and evidence that access requests and complaints are handled in a structured way.

How do I know if my organization is PIPEDA compliant?

Common gaps in the OPC's 2025–26 survey of consumer-facing businesses: no regular staff privacy training (38%), no designated privacy officer (28%), no documented staff policies (26%), and no complaint handling procedure (23%). A structured assessment covering all ten PIPEDA principles against your current practices is the most reliable way to identify gaps before a complaint or investigation occurs.

What records should I keep to demonstrate PIPEDA Principle 7 safeguards?

Investigators expect documentation that safeguards existed and were actively maintained before any incident. The records that matter most: access control logs showing who had system access and when it was revoked, MFA configuration records, patch and update logs, encryption policy and device records, staff training completion records, a dated incident response plan, and vendor contracts with security requirements. No law sets a period for these; keeping them at least two years matches the federal breach-record period. If a breach occurs, preserve them immediately: they become the main evidence of your safeguards at the time.

This guide is educational and does not constitute legal advice. It is grounded in the text of PIPEDA, Alberta PIPA, and BC PIPA and published guidance from the OPC, OIPC Alberta, and OIPC BC. If your situation involves regulatory investigation, litigation risk, or circumstances not addressed here, engage a qualified privacy lawyer.

See where you stand

Answer four questions about a fictional property manager and see where it stands in each area the law covers.

How ClearBreach shows what you have in place →

See plans and pricing →