← Guides·All compliance guides →
Your SituationWe want our privacy basics in place →
Do I Need a Written Privacy Policy? What Canadian Privacy Law Requires
By Yong DuPublished Reviewed
PIPEDA requires your privacy practices to be readily available, and the provincial Acts on request. What to include.
On this page
Do I need a written privacy policy?
Yes. If your organization collects, uses, or discloses personal information in the course of commercial activity in Canada, PIPEDA Principle 8 requires you to make information about your practices readily available, and a written privacy policy is the usual way to do it. Alberta PIPA s.6 and BC PIPA s.5 require that information to be available on request. This is a current legal obligation, not a recommendation.
Yes. PIPEDA requires you to make information about your privacy practices readily available, and Alberta and BC PIPA require written policies. In practice that means a page on your website. It does not need to be long, but it must describe what you actually do: a template that does not match your practices is worse than none.
What the law actually requires
PIPEDA Principle 8 (Openness) requires you to make specific information about how you handle personal information readily available, in plain language.
Clause 4.8.2 lists what the information must include:
- the name or title, and address, of the person accountable for the organization's policies and practices, and to whom complaints or inquiries can be sent
- how to gain access to personal information the organization holds
- a description of the type of personal information held, with a general account of its use
- a copy of any brochures or other information explaining its policies, standards or codes
- what personal information is made available to related organizations, such as subsidiaries
Alberta PIPA requires a person responsible for compliance (s.5(3)) and reasonable policies and practices, with written information about them available on request (s.6). If you use a service provider outside Canada, those policies must say so. BC PIPA s.4(3) and s.5 say much the same, and s.5 adds a complaint process.
In practice, that means a public page on your website, reachable from the homepage.
What this looks like for a small organization
For a 12-person accounting firm, the policy does not need to be a 30-page legal document. It needs to describe accurately:
- the client information you collect: names, contact details, financial and tax records
- why: to provide accounting services and meet filing obligations
- who receives it: CRA, provincial revenue agencies, banks where authorized
- how long you keep records
- how a client can see their file or complain
How detailed the policy is should follow how complex your practices are, not how big you are. For a five-person firm with simple client contracts, one page can do it. Cover seven things: what you collect, why, how you use it, who you share it with, how long you keep it, how people can see their information, and how to reach your privacy officer. If that page is accurate, it meets Principle 8.
The real test: the policy must describe what you actually do. A template that does not match your practices is worse than no policy, because it puts on record practices you do not follow. In an OPC investigation, a policy that contradicts how you operate damages your credibility well beyond the complaint at hand.
What regulators look for
The OPC expects a public policy that names a privacy contact, says how to complain, and is specific enough to your practices that it could be checked against the facts in an investigation.
The 2012 joint guidance on privacy management programs, from the OPC, OIPC Alberta and OIPC BC, treats written policies as a core control, resting on a designated privacy officer and support from the top. A policy that says nothing about the matter under investigation does not show good faith. An example is a policy that describes what you collect but not that you pass it to vendors.
Being able to produce the policy, name the privacy officer and show that staff know the policy is the simplest evidence that a program exists, for any of the three regulators.
The gap most organizations have
The OPC's 2025–26 survey of 800 consumer-facing businesses found 72% rated themselves highly aware of their privacy duties, and 84% said they have a privacy policy. The content is where they fall short. A quarter of those policies do not say how long information is kept, and 30% do not say how it is disposed of. A template never checked against what the business does has the same weakness.
The underlying problem: a template tells you what a policy should contain. It cannot tell you whether what you wrote is true of your organization. The OPC's guidance sets out the required elements. Checking each one against your real practices is the step most organizations skip, and the one that decides whether the policy holds up.
A policy page never compared with your actual practices looks compliant. It may not hold up when the OPC asks for evidence that you do what it says.
How to close this gap
- Audit what personal information your organization actually collects, list every category (names, contact information, financial records, health information, employee information, website visitor data).
- For each category, document the purpose of collection and all the ways you use or disclose it.
- Identify all third parties who receive personal information and the basis for each disclosure.
- Establish your retention practice, how long each category is kept and how it is disposed of.
- Designate a privacy contact, include the role and how to reach them (a personal name is not required, but a reachable role is).
- Publish the policy on your website, reachable from the homepage.
- Review the policy annually and whenever your practices change, new software, new vendor, new service line.
Annual review
Your policy must match what you do now. Update it when you add a vendor that receives personal information, adopt software that collects data, or change your retention schedule. The OPC's privacy management program guidance includes a yearly review. That is what turns a one-time exercise into an ongoing practice.
ClearBreach's compliance assessment shows where you stand in each of the ten areas PIPEDA covers, including whether your privacy policy is current, accurate and complete. It lists the gaps and the next step for each, with the documents to close them.
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
Related guides
- PIPEDA Compliance Requirements, all ten PIPEDA obligations in one place
- Alberta PIPA Compliance Requirements, AB PIPA obligations for Alberta organizations
- BC PIPA Compliance Requirements, BC PIPA obligations for BC organizations
- What to Do When You Receive a PIPEDA Privacy Complaint, Principle 10 complaint handling
- Do You Need a Privacy Impact Assessment?, when a PIA is required or recommended
This guide covers PIPEDA, Alberta PIPA, and BC PIPA 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), which has its own privacy policy requirements.
If your organization handles personal health information under provincial health legislation such as Alberta's Health Information Act or BC's health statutes, additional obligations may apply that are not covered here.
Frequently asked questions
Is a privacy policy legally required for a small business in Canada?
Yes. PIPEDA Principle 8 requires every organization subject to it to make information about its privacy practices readily available, regardless of size. There is no small-business exemption. Alberta PIPA (s.6) and BC PIPA (s.5) require written information about your policies and practices to be available on request.
What must a PIPEDA-compliant privacy policy contain?
At minimum: what personal information you collect, why you collect it, how you use and disclose it, how long you retain it, the safeguards in place, how individuals can access or correct their information, and how to file a complaint. The policy must identify a privacy contact. A generic template that does not match your actual practices is not compliant.
Where does the privacy policy need to be published?
For most organizations, a publicly accessible page on the organization's website is the standard the OPC expects. It should be reachable from the homepage, typically linked in the footer. A policy that exists internally but is not accessible to the individuals whose information you hold does not satisfy Principle 8.
How is a privacy policy different from a cookie consent banner?
A cookie consent banner addresses one specific collection practice, tracking through cookies. A privacy policy addresses all personal information your organization collects, for all purposes, through all channels. The banner is often a component of the broader policy for organizations that operate websites; it does not substitute for the full policy.
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 →