Canada version. Opens on the Canada filter: PIPEDA with its breach reporting duty and fines, Quebec Law 25 with privacy officers, impact assessments and penalties, and WCAG. US version
Software Compliance Checklist (Canada)
Build a software compliance checklist for Canada: PIPEDA breach reporting, Quebec Law 25 privacy impact assessments and fines, plus WCAG and global standards.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Software Compliance Checklist?
This version opens on the Canada filter, which lists PIPEDA, Quebec's Law 25 and WCAG. PIPEDA sets the rules for private-sector organizations handling personal information in commercial activities across Canada, except within Alberta, British Columbia and Quebec, which have their own substantially similar laws. PIPEDA still applies to information that crosses provincial or national borders, so most SaaS products meet it wherever they are based.
Quebec's Law 25 goes further and its penalties are larger. It requires a person in charge of protecting personal information with published contact details, privacy impact assessments before information leaves Quebec, reporting of confidentiality incidents with a risk of serious injury, privacy settings at the highest level by default, and data portability since September 22, 2024. Administrative penalties reach CA$10 million or 2% of worldwide turnover and penal fines CA$25 million or 4%, whichever is higher.
Under PIPEDA, breaches of security safeguards that pose a real risk of significant harm must be reported to the Privacy Commissioner and the people affected, and every breach must be recorded. Knowingly failing to do so can bring a fine of up to CA$100,000 per offence. Switch to Global for ISO 27001, SOC 2 and PCI DSS, which Canadian enterprise buyers often ask about.
- 31 laws, standards and frameworks with requirements and penalties
- Search plus domain and geography filters
- Custom checklist downloaded as Markdown task list
- CSV export of the filtered list
- Runs in your browser with no account
Updated
How to use the Software Compliance Checklist
- On the Browse Compliances tab, type in Search compliances (for example "cookies" or "health") and narrow with the Domain and Geography filters.
- Click a card to open its details: requirements, applicability, penalties, related items and official resources.
- Click the + on a card to add it to your checklist.
- Open the My Checklist tab, rename the checklist, and click Download MD to save a Markdown file with a checkbox for every requirement.
- Use Export Report on the Browse tab to download the currently filtered list as CSV.
Worked examples
Toronto SaaS with users in Quebec
Input
Geography: Canada
Output
3 results: WCAG, PIPEDA and Quebec Law 25
Selling to Quebec customers brings Law 25 on top of PIPEDA. The privacy impact assessment before data leaves Quebec affects hosting and vendor choices, so add it to the checklist early.
Quebec-only view
Input
Geography: Quebec
Output
1 result: Quebec Law 25
Use this filter to build a Law 25 checklist on its own, for example for a privacy officer reviewing incident registers and consent screens.
Background and insight
Most software teams meet compliance through a product decision rather than a legal memo: a signup form that collects a birth date, a checkout that stores card numbers, an analytics script that sets cookies for EU visitors. Each of those pulls in a different regime. Card data brings PCI DSS, health records held for a US covered entity bring HIPAA, children under 13 bring COPPA, and EU residents' personal data brings GDPR wherever the company is based.
The documents differ in kind. GDPR, CCPA and HIPAA are laws with regulators and fines; GDPR's upper tier is EUR 20 million or 4 percent of worldwide annual turnover, whichever is higher, and it requires breach notification to the authority within 72 hours. PCI DSS is a contractual standard set by the card brands (version 4.0 became the only active version in 2024). SOC 2 is an attestation report by an independent CPA firm against AICPA criteria, not a certification. WCAG 2.2, published by the W3C in October 2023, is the technical yardstick most accessibility laws point to.
Engineering work tends to repeat across regimes: an inventory of personal data, access control and audit logs, encryption in transit and at rest, retention and deletion, breach response, vendor contracts, and accessible UI. Building those once and mapping them to each framework is cheaper than treating every framework as a separate project.
Common use cases
Scoping a new product
List the regimes a feature might trigger before design starts, while changes are cheap.
Answering a security questionnaire
Get a quick summary of SOC 2, ISO 27001 or HIPAA terms an enterprise buyer asks about.
Planning an engineering roadmap
Download a Markdown checklist and turn requirement lines into tickets.
Onboarding new engineers
Give a team a shared vocabulary for the frameworks their product is subject to.
Tips and limitations
- Assess every breach for a real risk of significant harm and keep a record either way; the OPC can ask to see breach records.
- Publish the title and contact details of your person in charge of personal information if you serve Quebec.
- Check whether Alberta's or British Columbia's PIPA applies to employee data in those provinces.
- Commercial email to Canadians also falls under CASL, which this list does not cover; check consent separately.
Sources and further reading
- PIPEDA in brief, Office of the Privacy Commissioner of Canada
- What you need to know about mandatory reporting of breaches of security safeguards, Office of the Privacy Commissioner of Canada
- Principaux changements apportés par la Loi 25, Commission d'accès à l'information du Québec
- PIPEDA, section 28: offences and punishment, Justice Laws Website
Frequently asked questions
Does PIPEDA apply to my company?
If you are a private-sector organization collecting, using or disclosing personal information in the course of commercial activity in Canada, yes, except for activity entirely within Alberta, British Columbia or Quebec, where provincial laws apply. Information crossing borders stays under PIPEDA.
What are the fines under Quebec Law 25?
Administrative monetary penalties of up to CA$10 million or 2% of worldwide turnover, and penal fines of up to CA$25 million or 4% of worldwide turnover, whichever is higher in each case. Penal fines can be doubled for repeat offences.
When must a privacy breach be reported in Canada?
Under PIPEDA, as soon as feasible after you determine that a breach of security safeguards creates a real risk of significant harm, to the Privacy Commissioner and to the affected people. Under Law 25, confidentiality incidents with a risk of serious injury go to the CAI and the people concerned.
Do I need a privacy impact assessment for cloud hosting outside Quebec?
Law 25 requires one before personal information is communicated outside Quebec, which includes storing it with a provider elsewhere. The assessment looks at the sensitivity of the data, the purpose, the protection measures and the legal regime where it goes.
What is the maximum fine under PIPEDA?
Up to CA$100,000 per offence for knowingly failing to report or record breaches, or obstructing the Commissioner (section 28). Individuals can also seek damages in Federal Court after an OPC complaint.
Is there an in-depth guide to the Software Compliance Checklist?
Yes. “Which Compliance Rules Apply to Your Software? A Map for Engineers” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.