Skip to the main content

8 min readPublished Last updated

Privacy Policy Guide for Canadian Small Businesses

Written by UXPro Design Studio. Kitchener, ON. Prepared with AI assistance and checked against the sources listed below. General information, not legal advice.

What does a small business website privacy policy need to cover in Canada?

A Canadian small-business privacy policy should say what personal information your website collects and why, who you share it with (including the tools that process it for you), how people can see, correct or complain about their information, and who to contact about privacy. PIPEDA requires that information to be clear and readily available, and a privacy policy is the usual place to put it.

Key facts
The law for most private businessesPIPEDA, for personal information collected in commercial activity (Alberta, BC and Quebec have their own laws for activity inside those provinces)
What it asks forInformation about your privacy practices that is clear, easy to understand and readily available
Who must be namedThe person accountable for privacy, by name or title, with contact details
Access requestsAnswer within 30 days, at minimal or no cost
QuebecA published website privacy policy is required if you collect personal information by technological means

Does PIPEDA apply to my small business website?

Most likely, yes. The Personal Information Protection and Electronic Documents Act (PIPEDA) applies to private-sector organizations that collect, use or disclose personal information in the course of commercial activity. Personal information a business collects through its website, such as a contact form, is generally collected in the course of commercial activity.

Three provinces have their own private-sector laws that the federal government treats as substantially similar: Alberta, British Columbia and Quebec. Businesses covered by those laws are generally exempt from PIPEDA for activity inside the province, but PIPEDA still applies when information crosses provincial or national borders. Ontario's substantially similar law covers health information only, so PIPEDA generally applies to private businesses in Ontario.

Two common exceptions: not-for-profits and charities are generally outside PIPEDA unless they carry on commercial activity, and business contact information used only to reach someone about their work is excluded. If you run a clinic, health information falls under Ontario's PHIPA instead; our guide to what a clinic website form can collect under PHIPA covers that.

A federal bill, C-36, was introduced on 15 June 2026. It would enact a new Protecting Privacy and Consumer Data Act and amend PIPEDA. It is not law. PIPEDA is the law in force today.

What must a privacy policy say?

The Office of the Privacy Commissioner of Canada's (OPC) Privacy Guide for Businesses lists what you should make available, in plain terms, under its openness principle:

  • the name or title and contact details of the person accountable for privacy in your business
  • where to send a request to see personal information, and how that works
  • how to make a complaint
  • what personal information you disclose to other organizations, including third parties, and why

The OPC's ten tips for a better online privacy policy add the practical layer. The policy should name:

  • what you collect, and why;
  • which vendors or third parties receive it, by name or by the service they provide;
  • every tracking method, not only cookies (pixels, embeds, server logs);
  • the choices people have, such as opting out of marketing;
  • how to ask for access, correction or deletion;
  • the date of the last review, updated whenever your practices change.

The OPC also says you must answer an access request within 30 days, at minimal or no cost, with a longer period allowed only in specific cases and with notice.

On breaches, the OPC's breach guidance says you must report a breach that creates a real risk of significant harm to the OPC, notify the people affected as soon as feasible, and keep a record of every breach, reportable or not, for two years.

What should it say about each part of your website?

Go element by element: each tool that touches a visitor's information gets a line. The middle column is typical; check your own settings and each vendor's documentation.

Table · scrolls sideways

Website elementWhat it usually collectsWhat to say in the policy
Contact formName, email, phone, messageWhich fields you ask for and why, where submissions go (inbox, form service), who reads them, how long you keep them
Booking or scheduling toolName, contact details, appointment time, sometimes notesThe vendor by name or by what it does, that it processes data for you, and that data may be stored outside Canada
Google Analytics or other analyticsDevice and browser data, pages visited, often through cookies or similar identifiersThat you use it, that it uses cookies, how the provider processes data, how to opt out
Embedded video (for example, YouTube)Viewing data sent to the video hostThat the player comes from a third party with its own policy. YouTube's privacy-enhanced mode stops embedded views from being used to personalize YouTube or ads, but the player still comes from Google, and viewers who click through are covered by YouTube's own policies
Email sign-upEmail address, name, the consent recordWhat you will send, which service sends it, how to unsubscribe
Chat widgetMessages, sometimes name and emailThe vendor, whether chats are stored, who reads them, any automated or AI processing
Ad pixels and retargetingBrowsing behaviour, sometimes across sitesThe purpose in plain words and how to opt out (see the cookie section below)
Hosting and server logsIP address, request detailsYour host by name or service, what the logs keep, where data is processed

Two OPC points sit behind several rows. Handing data to a vendor that processes it for you counts as a use, not a disclosure, so you do not need fresh consent for the same purpose, but you stay accountable and should say that information may be processed in another country and be accessible to its authorities (OPC cross-border guidelines). And for Google Analytics specifically, Google's Analytics terms require you to post a privacy policy that notes your use of cookies and discloses that you use Google Analytics. That is a contract term with Google, not a law, but you agreed to it.

Email sign-ups also need CASL consent, which is separate from privacy law; see CASL-compliant sign-up forms.

For a real, short example, our own privacy page names each form on the site, each service that processes what people type, and says the site sets no cookies.

Not by name. PIPEDA has no cookie rule, but if you run ad pixels or retargeting, the OPC expects you to tell visitors before tracking starts and give an easy opt-out, and a banner is the usual way to do that.

Tracking falls under the OPC's general guidelines for obtaining meaningful consent, which say express consent is generally needed when information is sensitive, when a use falls outside what a person would reasonably expect, or when there is a meaningful residual risk of significant harm. The OPC also says a line buried in a policy is not enough to get consent for something people would not expect.

For ad tracking across sites, the OPC's online behavioural advertising guidelines say opt-out consent can be reasonable only when the purpose is made obvious and not buried in a privacy policy, people are told at or before collection, opting out is easy, immediate and lasting, the information is non-sensitive, and it is destroyed or de-identified quickly. The OPC also advises against tracking children or tracking on sites aimed at children.

In short:

  • A banner is one way to tell people at the right moment and record their choice, not a requirement by name.
  • If you run ad pixels or retargeting, people need to be told up front, not only in the policy, and given an easy opt-out.
  • If you sell into Quebec and use tools that profile visitors, read the next section.

What if you sell into Quebec?

Quebec's private-sector privacy law, as amended by Law 25, is stricter on websites. Under the Act respecting the protection of personal information in the private sector (CQLR c. P-39.1), since 22 September 2023:

  • If you collect personal information by technological means, you must publish a privacy policy on your website in clear and simple terms, and give notice of changes (s. 8.2).
  • If you use technology that can identify, locate or profile a person, you must tell them beforehand and explain how to turn those functions on (s. 8.1). Quebec's privacy regulator, the Commission d'accès à l'information (CAI), says those functions must be off by default.

Section 3.1 also requires the title and contact information of the person in charge of protecting personal information to be published on your website. The CAI's guide to writing a privacy policy (in French) lists what to include and says the policy must be separate from your terms of use.

Why is a template not enough?

The OPC's first tip is to make the policy specific to your business and avoid templates. The CAI asks for the actual means you use to collect information. A template lists tools you do not use and misses the ones you do: the form plugin, the booking vendor, the chat widget someone added last spring. Keep a list of every tool on the site, and update the policy and its review date whenever that list changes. Who controls the accounts behind those tools matters too; see who owns what on your website.

How UXPro can help

We are not lawyers and do not write legal policies. When we build a site, we publish the privacy policy you provide and link it from every form that collects personal information. See website design and build for what a build includes. Our compliance passes cover the LSO, PHIPA and AODA rules for regulated sectors; they are not a PIPEDA or Law 25 review.

What people ask next

The questions this guide gets asked after it has been read. Each answer is on the page, so the FAQ markup and the visible text are the same words.

PIPEDA requires a business to make information about its privacy policies and practices readily available and easy to understand. It does not name a document, but a privacy policy on your website is the usual way to meet that duty. Quebec's private-sector law goes further: if you collect personal information by technological means, you must publish a privacy policy on your website.

Generally, yes, for personal information collected in commercial activity. Ontario's own substantially similar law covers health information only, through PHIPA.

You can read one for structure, but the OPC advises making your policy specific to your business and avoiding templates, because a template misses the tools you actually use.

Yes, if you use it. Google's Analytics terms require a privacy policy that notes your use of cookies and discloses that you use Google Analytics and how it collects and processes data.

The person accountable for privacy in your business, by name or title, with contact details, plus where to send a request to see personal information. In Quebec, the title and contact information of the person in charge of protecting personal information must be published on your website.

Next step

What to do with this.

List every form, embed, script and tool on your site, then check your policy names each one. For a second look at the page itself, request a free Redline: we redline one page of your site at phone width, up to ten notes, sent as a PDF.

General information, not legal advice; a privacy lawyer can confirm what applies to you. Sources: OPC, Parliament of Canada, Google, YouTube Help, LégisQuébec and the CAI (Commission d'accès à l'information), all checked 14 November 2026.

What you get

We read your site by hand and reply with written findings.

No turnaround time is published yet. We would rather say nothing than publish a window we have not tested.

Written by

UXPro Design Studio

UXPro Design Studio · Kitchener, ON

Prepared with AI assistance and checked against the sources listed below.

General information, not legal advice.

Sources

For AI agents

Read as Markdown — the same guide as plain text, served as text/markdown. The feed for every published guide is at /blog/rss.xml.