Website Privacy Basics for Small Businesses in Canada

If your website collects personal information through contact forms, bookings, chat, newsletter sign-ups, analytics or advertising tags, Canadian privacy law applies to it. Most small businesses fall under the federal PIPEDA, or under the provincial law in Quebec, Alberta or British Columbia. The basics are the same everywhere: say clearly what you collect and why, get meaningful consent, collect only what you need, protect it, and deal properly with breaches.
This guide covers those basics for a typical business website. It is general information, not legal advice; confirm your own obligations with a privacy lawyer. Quebec has extra rules on cookies and consent banners, covered in our guide to Quebec Law 25 for websites.
Which privacy law covers your website
The Personal Information Protection and Electronic Documents Act (PIPEDA) applies to private-sector organizations that collect, use or disclose personal information in commercial activities. Organizations covered by a substantially similar provincial law are generally exempt for activity inside that province; Alberta, British Columbia and Quebec have such laws. Ontario, New Brunswick, Nova Scotia and Newfoundland and Labrador have separate laws for personal health information, which matter for clinics and other health providers.
PIPEDA rests on 10 fair information principles: accountability, identifying purposes, consent, limiting collection, limiting use, disclosure and retention, accuracy, safeguards, openness, individual access and challenging compliance. A website touches almost all of them.
What counts as personal information on a website
The OPC explains that under PIPEDA, personal information includes “any factual or subjective information, recorded or not, about an identifiable individual.” On a website that includes names, email addresses, phone numbers, messages, booking details and uploaded files. It can also include data that analytics, chat and advertising tags connect to a particular visitor.
A privacy policy people can actually read
The Office of the Privacy Commissioner of Canada’s guidelines for obtaining meaningful consent say organizations should not simply move a paper policy onto a web page, and that information buried in a long privacy policy or terms of use does little for people with limited time. Four elements should be easy to find:
We plan and deliver website maintenance and security for businesses in Toronto and across Canada, scoped in writing after a free review.
- what personal information you collect;
- who you share it with, including service providers;
- why you collect it;
- the risks of harm and other consequences that remain.
Layered notices work well on websites: a short line beside each form, with a link to the full policy. The guidelines also recommend just-in-time notices at the moment information is collected, and formats that read well on phones.
Consent for forms, analytics and advertising tags
- Give a clear yes or no for anything that is not needed to provide what the visitor asked for, such as marketing email or advertising cookies. You cannot require consent beyond what the service needs.
- Use express consent where information is sensitive, such as health or financial details, or where a use falls outside what visitors would reasonably expect.
- Let people withdraw consent, and get fresh consent before a new purpose or a new third party.
- Keep sensitive details out of analytics and ad platforms. A booking form for a clinic should never pass the reason for the visit into tracking.
Visitors from Quebec need an opt-in before tracking that can identify, locate or profile them. Marketing email has its own consent rules under Canada’s anti-spam law; see our guide to CASL.
Children and teens
On October 20, 2026, the OPC launched a Children’s Privacy Code for organizations that handle children’s personal information, including websites and mobile apps. It expects parental consent for children under 13, opt-in consent for non-essential uses, privacy-protective defaults, no profiling of children for marketing and no deceptive design that pushes children to share more than needed. The OPC is taking comments until January 20, 2027, and may update the code after that. If your site sells to families, schools or teens, read it now.
Vendors that touch your website data
Form tools, booking systems, chat widgets, email platforms, analytics and hosting all handle data on your behalf. Under the OPC’s accountability principle, you remain responsible for personal information you transfer to a third party for processing, and you should limit, by contract or other means, how that third party uses it. Keep a list of every service that receives website data, what it receives and where it stores it.
If something goes wrong: breaches
The OPC’s breach guidance for businesses sets out the rules under PIPEDA. If a breach of security safeguards creates a real risk of significant harm to anyone, report it to the OPC and notify the affected people as soon as feasible. Keep a record of every breach, whether or not it meets that threshold, for at least two years. Website breaches often start with an outdated plugin, a weak admin password or a form that emails full submissions to a shared inbox, which is why ongoing website maintenance and security is part of privacy.
A website privacy checklist
- List every form, tag, widget and service on the site that collects or receives personal information.
- Remove fields you do not need.
- Add a short notice beside each form and link the full privacy policy.
- Name the person accountable for privacy and give a way to contact them.
- Separate marketing consent from the form’s main purpose, with its own unticked box.
- Check that no sensitive details reach analytics or advertising platforms.
- Set an opt-in banner for visitors from Quebec.
- Keep plugins, themes and admin accounts up to date, with two-step login for administrators.
- Write down what you would do in the first 24 hours after a breach, and who decides whether to report it.
If you want this built into the site itself, our security and compliance team can review forms, tags and vendors against these points.