PIPEDA for a Canadian Small Business Website: Consent, Access and Breach Basics
Short answer: The federal Personal Information Protection and Electronic Documents Act (PIPEDA) applies to private businesses that collect, use or disclose personal information in the course of commercial activity. For a website, that means forms, newsletter sign-ups, analytics and customer accounts all need a clear purpose, a reasonable level of consent, and sensible limits on how long you keep data. Respond to access requests, protect what you hold, and report breaches that create a real risk of significant harm. Alberta, British Columbia and Quebec have their own private-sector privacy laws, so check which regime covers your province before you rely on this summary.
Where PIPEDA applies and where it does not
PIPEDA is built around ten fair information principles, which are the backbone of Canadian privacy practice. It covers commercial activity across provinces and territories, but a province with a privacy law that the federal government has recognised as substantially similar takes over much of the work inside its borders. Alberta, British Columbia and Quebec are the main examples. If your business operates only in one of those provinces, the provincial law is usually the first place to look, and PIPEDA still governs personal information that crosses provincial borders.
The ten principles are accountability, identifying purposes, consent, limiting collection, limiting use, disclosure and retention, accuracy, safeguards, openness, individual access and challenging compliance. You do not need to memorise them. You need to be able to show that your website reflects each one.
Accountability: name someone
Appoint a person in your business who handles privacy questions, and publish a contact address on your website, such as privacy@ with your domain. A small team can use the owner or the office manager. The important thing is that customers and regulators know who to contact and that the person knows where personal information lives.
Consent for forms, analytics and marketing
Consent should match what a reasonable person would expect. A quote request form that asks for a name, an email and a short job description needs no separate consent to answer the enquiry. Adding that email to a monthly newsletter is a different purpose and needs its own tick box, left empty by default.
Analytics is where many small sites slip. If you use a tool that sets cookies or sends visitor data to a third party, say so in your privacy policy and explain the purpose. For example:
We use an analytics tool to count visits to each page and find broken links. The tool does not receive your name or contact details.
Check the settings of the tool itself. Many analytics services let you turn off advertising features, shorten retention and mask IP addresses. Enable those options and record the settings you chose.
Limit collection and set retention
Collect only what you need. A bakery's wedding-cake enquiry form does not need a date of birth. Note a holding period for each type of record, for example "enquiry messages are removed after 12 months unless a contract follows". Then actually delete them. Retention rules that exist only on paper do not protect anyone.
A simple table helps:
| Data | Purpose | Keep for |
|---|---|---|
| Enquiry form (name, email, message) | Answer the enquiry | 12 months |
| Customer invoice | Accounting | Per tax rules, check CRA guidance |
| Newsletter sign-up | Send newsletter | Until the person unsubscribes |
| Analytics logs | Improve the site | As set in the tool |
Respond to access requests
Individuals can ask what personal information you hold about them and how you use it. PIPEDA generally requires a response within 30 days, though limited extensions exist. Plan the work before the first request arrives:
- Confirm the identity of the person asking, using a method proportionate to the risk.
- Search your email, contact database, booking tool and invoice folder for their name and email.
- Prepare a copy of the information and a short explanation of how it was used and who received it.
- Remove or correct anything that is wrong, if they ask.
- Keep a log of the request, the dates and what you sent.
Do not send personal information to an email address you cannot verify, even if the person is in a hurry.
Safeguards for your website
Use HTTPS on every page that collects information. Keep your website platform, plugins and password manager up to date. Give staff individual logins to your site admin and your email, and remove people who leave. Limit access to the database of form submissions to the people who need it.
These steps do not guarantee security, but they show that you took reasonable measures, which is what PIPEDA expects.
Breach reporting
A breach of security safeguards is any loss of, unauthorised access to or unauthorised disclosure of personal information. If a breach creates a real risk of significant harm, you must report it to the Office of the Privacy Commissioner of Canada and notify the affected individuals. You must also keep a record of every breach, even minor ones, and the rules require that records are kept for at least 24 months.
For example, imagine a fictional yoga studio called Still Point Studio whose booking system is accessed by a former employee. The owner should log the incident the same day, change passwords, check which records were visible, decide whether there is a real risk of harm, and then follow the reporting steps. A short breach record might include:
- Date and time discovered
- What information was involved
- How many people may be affected
- Steps taken to contain the incident
- Whether the risk was assessed as significant and why
- Who was notified and when
A short checklist
- Privacy contact address published on the site
- Forms collect only what is needed
- Newsletter and marketing consent is separate and unticked
- Analytics tool named in the privacy policy with its settings recorded
- Retention periods written down and applied
- Access request steps written and tested once
- Breach record template saved somewhere the team can find
FAQ
Does a contact form trigger a policy requirement?
It effectively does. Once a form gathers names or emails, a short notice stating the purpose and the contact route shows that you are open about your handling of that data.
Is an IP address personal information?
It can be, depending on the context. Treat IP addresses in analytics and logs as personal information unless your provider has confirmed otherwise, and mask them where the tool allows.
Can I refuse an access request because it is a nuisance?
Refusal is limited to specific grounds set out in the law. Ask the OPC or check its guidance before you say no, and keep a record of your reasons.
What if a customer in Alberta asks about their data?
Provincial law may apply to that information. Check the Alberta requirements and treat the request with the same care as a federal one.
Consent wording, a privacy page and a breach log can be set up in an afternoon once someone has mapped your forms, and we can do that mapping with you via the enquiry page.