Short answer: A Canadian website privacy policy is the public statement of how your business collects, uses, discloses and protects personal information — and in Canada it is not decoration. PIPEDA, the federal private-sector privacy law, requires organizations to be accountable for that information, to identify the purposes for collecting it, and in most cases to get meaningful consent before or when they collect it. Your contact form and newsletter signup are where the policy meets practice, and a second law, CASL — Canada’s anti-spam legislation — governs the commercial emails that follow a signup: consent before sending, clear identification in every message, and an unsubscribe mechanism that actually works.
Two laws, two different jobs
Owners often merge privacy and anti-spam into one vague worry, but they regulate different moments. Privacy law — federally, the Personal Information Protection and Electronic Documents Act, PIPEDA — governs the information itself: what you collect through your website, why, how long you keep it, who else receives it, and what rights the person has over it. The Office of the Privacy Commissioner of Canada explains the statute on its PIPEDA overview page, the authoritative plain-language source for this section.
CASL governs the message. Canada’s anti-spam legislation applies to commercial electronic messages — emails sent to encourage participation in a commercial activity. Its core requirements are simple to state and strict in practice: consent before you send, clear identification, and a functioning way to unsubscribe. The federal government’s Canada’s anti-spam legislation site — successor to the old fightspam.gc.ca pages — sets out the rules, including express versus implied consent.
Some provinces add a third layer: Alberta, British Columbia and Quebec have their own private-sector privacy statutes, and Quebec’s Law 25 has added specific duties around privacy policies and consent. A business selling across Canada needs a policy written for where its customers are — one more reason the copied American template is the wrong starting point. This article is general information, not legal advice.
What a Canadian website privacy policy actually has to cover
PIPEDA is built on fair information principles, and a compliant policy reads like those principles applied to your real website. It names someone accountable for personal information — for a small business, usually the owner — and how to reach them with privacy questions. It states the purposes for collecting information, in language a customer would recognize: answering enquiries, fulfilling orders, sending a subscribed newsletter, improving the website through analytics. Purposes stretched to cover anything (“for business purposes”) fail the principle that purposes be identified at or before collection.
The policy must describe consent honestly — what the person is agreeing to, and that they can withdraw it — and cover disclosure: the third parties who receive information because your website runs on them. For a typical small site that list is concrete: hosting company, email or newsletter platform, payment processor, booking tool, analytics provider, and embedded services such as maps or video players. It should state how long information is kept and what safeguards protect it, without promising security you do not actually operate. Finally, it must give individuals their rights in usable form: how to ask what information you hold, request a correction, and complain — first to you, then to the Privacy Commissioner. Write only what is true of your site today, and update the policy when the site changes.
The contact form: where consent is actually collected
A contact form looks too small to raise legal questions, which is exactly why it raises them. Every submission collects personal information — a name, an email address, often a phone number and the message itself — and PIPEDA applies to that collection. Ask only for what the enquiry needs: name, a reply address and the message cover most service businesses, and every extra field is information you must protect without a purpose to justify it.
State the purpose at the form itself, in a line a visitor reads before submitting: the information will be used to reply to the enquiry, and the full policy is linked nearby. Keep the submission’s journey in mind too: form entries land in an inbox, a website database and sometimes a customer-management tool — each belongs in the policy’s picture of your practices, and each needs ordinary safeguards such as limited access and old submissions deleted on a schedule.
One boundary deserves emphasis: an enquiry is not a subscription. A person who used your contact form consented to a reply about that enquiry, not to join your marketing list — and adding them turns a privacy problem into a CASL problem as well. If you want enquirers on your list, ask, with a separate, unticked checkbox that says plainly that checking it subscribes them to marketing emails. Pre-ticked boxes do not produce meaningful consent.
The newsletter signup: CASL consent, done properly
A newsletter signup is a request for express consent, and CASL is specific about what that request must contain. The person must be told, clearly and simply, the purpose — marketing emails from your business — and who is asking: your business’s name, with a mailing address and another contact route such as a phone number or email address. They must also be told they can unsubscribe at any time. The consent itself must be an active step: typing an address and pressing a subscribe button, or ticking an empty box. Consent buried in terms and conditions, or assumed from silence, is not express consent.
Implied consent exists but is narrower than most senders assume. It can arise from an existing business relationship — a customer who bought from you within the relevant period, or an enquiry within a shorter one — and CASL sets time limits after which it expires. It does not come from an address being published online: a publicly posted email address is not an invitation to market to it, and harvesting addresses offends CASL’s consent rules. Bought and rented lists sit in the same danger zone, because any consent was given to someone else, not to you.
Keep the evidence: for each subscriber you should be able to show when and how consent was given — the form’s wording at the time, the date, and whether consent was express or implied. Newsletter platforms record much of this automatically. Double opt-in is not strictly required by CASL, but it creates exactly that evidence trail, so treat it as the default.
Every commercial message must then carry CASL’s other two requirements: identification — your business name, mailing address, and a phone number, email or web address, accurate for at least 60 days after sending — and an unsubscribe mechanism that is clear, works without cost or extra steps, and is honoured within ten business days at the outside, in practice immediately through your platform.
Cookies, analytics and the quiet collectors
Forms are the visible collection; cookies and trackers are the invisible kind, and your policy has to cover them too. Analytics tools record how visitors use the site, advertising pixels connect visits to campaigns elsewhere, and embedded maps, videos and chat widgets contact third-party servers. Under PIPEDA, information that can identify an individual is personal information, and an honest policy names the tools in use and what they collect. Businesses get into trouble in the gaps — such as a policy claiming no third-party sharing on a site running a half-dozen trackers.
Keeping it true over time
Compliance decays on a schedule set by your website changes, not by the calendar. Review the policy whenever you add a tool, a form field, a platform or a market, and at least once a year regardless. Keep records only as long as their purpose lasts. Our services page describes what each service includes, our pricing page lists published figures such as Website Care at US$69 a month (taxes extra; CAD invoices available on request), and our article on what a small law firm’s website must do to earn trust shows how regulated professions take this accuracy seriously. None of this requires turning a small website into a legal project — one accurate page, two careful forms, and records you can produce if asked.
Frequently asked questions
What must a Canadian website privacy policy include?
It should name the person accountable for personal information and how to reach them, state the purposes for collecting information, describe consent and how to withdraw it, list the kinds of third parties information is disclosed to — hosting, email platform, payment processor, analytics — explain retention and safeguards, and tell individuals how to access or correct their information and complain. Above all, it must match what your site actually does.
Can I add people who used my contact form to my newsletter list?
Not on the strength of the enquiry alone. Submitting a contact form is consent to be contacted about that enquiry, not consent to receive marketing. To add enquirers lawfully, ask separately — for example with an unticked checkbox at the form that clearly describes the marketing emails — so their express consent under CASL is recorded.
What does CASL require in every marketing email?
Three things: consent obtained before sending — express, or implied within CASL’s time-limited categories such as a recent purchase; clear identification of your business, including a mailing address and another contact method valid for at least 60 days; and a functioning unsubscribe mechanism honoured within ten business days at the latest.
Is implied consent enough to build a mailing list?
Implied consent covers narrow, time-limited situations such as recent customers and recent enquiries; it does not cover purchased lists or addresses copied from websites. For a newsletter, express consent — an active signup with the required information stated at the point of signup — is the standard to build on, ideally with a double opt-in.
Do I need a lawyer to write my privacy policy?
Many small businesses can draft an accurate policy themselves using the Privacy Commissioner’s guidance, provided it describes their real practices. The risk is copying a template — especially a US one — that promises things the site does not do. Businesses handling sensitive information, or selling into Quebec under Law 25, should have a Canadian privacy lawyer review it.
One accurate page, two careful forms
Your policy earns its keep when a visitor, a subscriber or a regulator can compare it against your forms and find no gaps. If you would like your policy page, contact form and signup flow reviewed together so they say the same thing, Get a Free Quote and tell us which tools your site uses to collect, send and measure.

