Website privacy checklist for Canadian businesses
Review what your website collects, how consent works, which suppliers receive information and whether your privacy notice matches the site you run.

A privacy notice can drift away from the website it describes. Someone adds a booking tool, marketing connects a tracking service, or contact-form messages start going into a new customer database. The notice stays the same.
Use this checklist when reviewing your site or approving a new integration. It helps you gather evidence for a privacy review. Confirm the laws that apply to your organization with your privacy or legal adviser.
Walk through the site as a visitor
Submit each form with test information. Follow a booking link, sign up for the newsletter and check any chat, payment or account features. Record:
- The information requested and which fields are required.
- Why each field is needed.
- Where the submission goes and who can read it.
- Any browser storage, analytics or advertising services loaded.
- The suppliers involved and the settings you’ve chosen.
Include mobile pages and embedded tools. Check what loads before someone makes a choice, as well as what loads afterwards. Ask the site maintainer to confirm anything you can’t see from the page.
Check each consent request
The Privacy Commissioner’s consent guidance calls for clear information about collection, sharing, purposes and significant risks. Give optional uses a meaningful choice. Review new purposes or disclosures before assuming an earlier consent covers them.
For every optional feature, test both acceptance and refusal. Does the feature respect the choice? Can the visitor change it later? Keep the wording and the evidence your organization needs to demonstrate consent.
If your site collects information from people in Quebec, check that province’s private-sector privacy law too. It requires you to tell visitors about technology that can identify, locate or profile them, and to give them a way to turn those functions on.
Email marketing has its own rules. The CRTC’s CASL guidance explains consent, sender identification and unsubscribe requirements for commercial electronic messages. Don’t treat a contact-form submission as permanent permission to send marketing. Test the signup and unsubscribe processes all the way through your mailing-list provider.
Compare the privacy notice with the evidence
Read the notice beside your inventory. Replace broad statements with a description of the services you use. Explain the purposes, sharing, retention and privacy contact in language visitors can understand.
Avoid promises your systems can’t support, such as immediate removal from every backup or a guarantee that information never leaves Canada. Have the responsible person confirm those statements against the suppliers’ terms.
The PIPEDA accountability guidance calls for a designated privacy official and implemented policies, training and procedures. Give that person the inventory and a list of discrepancies with owners and correction dates.
Test requests and incident handling
Send a test privacy enquiry to the published contact. Check that someone receives it and knows how to route it. Under PIPEDA, access and correction requests need an established process; the ordinary access response deadline is 30 days, with defined grounds for extension. The Commissioner’s individual-access guidance sets out the details.
Confirm who receives a supplier’s breach notice and where the incident plan is kept. Set retention rules for enquiry messages in inboxes as well as in the website’s database or delivery service.
Review changes before they go live
Keep a dated record of the review and the issues you’ve corrected. Check privacy before you add a new form, analytics service or AI feature. After a supplier or setting changes, repeat the relevant visitor journey and update the notice if the information handling has changed.


