ClearBreach

← Guides·What is changing in Canadian privacy law →

Your SituationWe want our privacy basics in place →

PPCDAAll sectors

What Is a Privacy Management Program Under Bill C-36 (PPCDA)?

By Yong DuPublished Reviewed

Share on LinkedIn

Bill C-36 would make a documented privacy management program mandatory. What it must cover, scaled to a small business.

On this page

What section 9 of the PPCDA requires

Every organization subject to Bill C-36's Protecting Privacy and Consumer Data Act must implement and maintain a privacy management program. Section 9(1) states this obligation directly. Section 10 requires the organization to give the Digital Safety and Data Protection Commission access to the program on request, including before any complaint is filed.

Under PIPEDA, organizations were expected to have a designated privacy officer and privacy policies, but there was no explicit statutory requirement to maintain a documented program. The PPCDA changes that. The obligation at section 9 is not guidance. It is a statutory requirement with its own enforcement path.


What the program must include

Section 9(1) identifies four elements. Each must be present and documented.

1. Policies and practices to protect personal information

This is the governance layer of the program, how personal information is collected, stored, accessed, retained, and disposed of. It covers security safeguards, access controls, and the organization's response process if a breach occurs. Where the organization handles sensitive categories of personal information (health, financial, identity), the program must reflect that sensitivity in its policies.

2. How the organization receives and handles access requests and complaints

An individual whose personal information is held by the organization has the right to access it and to file a complaint if they believe it has been mishandled. The program must include a documented procedure for each: how the request or complaint is received, who handles it, what the response timeline is, and how the outcome is communicated in writing. The procedure does not need to be complex. It does need to be functional and documented.

3. Staff training policies and procedures

Staff who handle personal information need to know the organization's obligations and what they are personally responsible for. The program must document how training is delivered, how often, and how it is recorded. Annual acknowledgement of the privacy policy is a sensible minimum. Staff with access to sensitive categories of personal information need more.

4. Public-facing materials explaining the organization's privacy practices

The organization must have materials, typically a privacy notice or policy, that explain to the public what personal information it collects, why it collects it, how it is used, and how individuals can access or correct their information. Those materials must reflect what the organization actually does. A boilerplate template that does not match real practices does not satisfy this element.


The proportionality requirement

Section 9(2) ties the program to the organization's actual risk profile: the program must be proportionate to the volume and sensitivity of personal information the organization holds.

This matters for small organizations. A 10-person dental office handling patient records operates under a different risk profile than a 10-person software company handling email addresses. The program each one needs reflects that difference.

For a small organization handling modest volumes of personal information (contact details, billing records, appointment histories) a proportionate program looks like:

  • A named privacy officer (this can be the owner at a very small organization)
  • A written privacy policy that reflects what the organization actually does
  • A one-page complaint handling procedure
  • Annual staff training or acknowledgement, documented
  • A public privacy notice available on the website or on request

None of those elements requires external legal counsel to produce. They require documentation and consistency.


What the Commission can do with it

Section 10 is the provision most organizations underestimate. On request, the organization must give the Commission access to the policies, practices and procedures in its program, with no complaint needed to trigger the request. After reviewing them, the Commission can give guidance or recommend corrective measures (s.10(2)).

Under PIPEDA, the OPC's look at an organization's practices has been largely complaint-driven. Under the PPCDA, the Commission could look before any incident occurs, and an organization with no program at all would not be meeting section 9.

This makes the privacy management program an ongoing governance obligation, not a one-time document.


What the 2012 joint guidance showed regulators expect

In April 2012, the OPC, OIPC Alberta, and OIPC BC published joint guidance on privacy management programs, Getting Accountability Right with a Privacy Management Program. It builds a program in two parts: organizational commitment (support from the top, a designated privacy officer, and reporting) and program controls (a personal information inventory, policies, risk assessment tools, training, breach and incident response, service provider management, and external communication), followed by ongoing assessment and revision.

Section 9(1) of the bill covers much of the same ground. The 2012 guidance remains the most detailed public description of what regulators consider a functioning program, and it is the practical starting point for organizations building one today.

What most Canadian organizations currently have

The OPC's 2025–26 survey of consumer-facing businesses shows the gap: 28% had no designated privacy officer, 23% had no formal complaint handling procedure, and 38% did not regularly train staff on privacy. All three sit inside what section 9 would require.

More than a quarter of those businesses are missing at least one core component of what Bill C-36 would require. For very small organizations, the gaps are often larger, no named privacy officer, no complaint procedure, and a public privacy policy generated from a template and never reviewed against actual practices.

The gap is not about knowledge of privacy law. It is about having internal governance structures that are documented and functional.


Scope note

This article covers the PPCDA (Bill C-36), which would replace PIPEDA's private-sector rules and apply in the same way. Organizations primarily engaged in intra-provincial commercial activity in Quebec are governed by Quebec's Act respecting the protection of personal information in the private sector (Law 25 / Bill 64), which has its own privacy management program requirements. Quebec obligations are not covered here.


What to do before Bill C-36 comes into force

The PPCDA is not yet law. PIPEDA remains operative. But building a privacy management program now, before there is enforcement pressure, is easier than building one after the obligation is enforceable.

Five steps for a small organization:

  1. Designate a privacy officer by name. Write it down. The Commission needs to know who is accountable for the program.

  2. Write a one-page complaint handling procedure. Cover how a complaint is received, who handles it, what the response timeline is, and how the organization communicates the outcome in writing.

  3. Map your data flows. Know what personal information you collect, why, who has access, and how long you keep it. This is the foundation of your privacy policy and your program. Without it, you cannot write a policy that reflects actual practices.

  4. Publish a privacy policy that reflects reality. A boilerplate policy that diverges from actual practices is worse than a plain accurate one, because it misdescribes what you do.

  5. Document staff training. Annual acknowledgement of the privacy policy is a minimum for staff with access to personal information. For staff handling sensitive categories, more is appropriate.


This page is about a requirement that is coming. If you are asking what to do now, that is a different page. Bill C-36 would make a documented privacy management program a statutory obligation. Until it is in force, the duties you owe come from PIPEDA, Alberta PIPA and BC PIPA as they stand, and almost everything a documented program needs is already among them. Building a privacy program is that work, in the order to do it. Doing it now is also how you are ready for C-36 without a second project.


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


Start your breach assessment

Breach reporting obligations under the PPCDA are identical to PIPEDA. Your current breach assessment process transfers directly. Confirm it is in place now.

See a complete assessment →

The PPCDA's mandatory program requirement is what the compliance assessment is for, and it is released with everything else at launch. Walk one on a fictional clinic →

Frequently asked questions

Is a privacy management program required under Canadian federal law right now?

Not yet. Bill C-36 and the PPCDA are not yet in force. PIPEDA remains the operative federal privacy law. Under PIPEDA, the accountability principle (Principle 1) requires a designated privacy officer and privacy policies, but there is no explicit statutory requirement to maintain a documented 'privacy management program.' Section 9 of the PPCDA changes that. Building one now, before the obligation comes into force, is easier than building it under enforcement pressure.

What must a privacy management program include under the PPCDA?

Section 9(1) of the PPCDA identifies four mandatory elements: (1) policies and practices to protect personal information, (2) how the organization receives and handles access requests and privacy complaints, (3) staff training policies and procedures, and (4) public-facing materials explaining the organization's privacy practices. The program must also be proportionate to the volume and sensitivity of personal information the organization holds, under section 9(2).

What does 'proportionate' mean for a small organization?

A small organization does not need a 50-page compliance binder. Proportionate means the program matches the actual risk profile of the organization, the types of personal information it holds, how much of it, and the likely harm if something goes wrong. For a 10-person firm, proportionate typically means a written privacy policy, a named privacy officer, a one-page complaint procedure, annual staff acknowledgement, and a public privacy notice. That covers all four elements section 9(1) requires.

What happens if the Commission asks to see our privacy management program and we do not have one?

Section 10 requires an organization to give the Digital Safety and Data Protection Commission access to the program on request, without a complaint being filed first. After reviewing it, the Commission can give guidance or recommend corrective measures (s.10(2)). Having no program at all would itself be a failure to meet section 9, whether or not there has been a breach or a complaint.

What is the difference between a privacy policy and a privacy management program?

A privacy policy is one component of a privacy management program, the public-facing document that explains what the organization collects, why, and how. A privacy management program is the broader governance structure the policy sits inside. It includes internal practices, staff training, complaint handling procedures, and internal controls. A privacy policy is what the public sees. A privacy management program is what the Commission examines when it investigates.

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 →