A privacy impact assessment (PIA) is a written check, done before launch, of what personal information a project touches, where it goes, what could go wrong for the people it describes and what you will do about it. For a private Canadian business, a PIA is a legal requirement in Quebec for new information systems and for transfers outside Quebec, and in Alberta for health custodians. Everywhere else it is the practical way to show the accountability that PIPEDA already demands. The template below is a starting point you can adapt, not legal advice.
When a PIA Is Legally Required, and When It Is Good Practice
What matters is which law governs the information, not company size.
| Situation | PIA status | Source |
|---|---|---|
| Business under Quebec's private sector act acquires, develops or overhauls an information system or electronic service delivery system involving personal information | Required (s. 3.3) | LégisQuébec, 2026 |
| Same business communicates personal information outside Quebec, or entrusts a provider outside Quebec with collecting, using or keeping it | Required, plus a written agreement (s. 17) | LégisQuébec, 2026 |
| Same business discloses personal information without consent for research or statistics | Required (s. 21) | LégisQuébec, 2026 |
| Alberta health custodian implementing or changing a system or practice that handles identifying health information | Must submit to the Commissioner (HIA s. 64) | OIPC Alberta |
| Federal institution under the Privacy Act | Required, using a mandatory template | TBS, 2024 |
| Ontario provincial institution under FIPPA | Required since July 1, 2025 (s. 38) | Ontario e-Laws, 2026 |
| Business under PIPEDA or Alberta's PIPA | Not required by statute; expected as good practice | OPC, 2012; OIPC Alberta |
Quebec: The Strictest Private Sector Rule
Under section 3.3, the person in charge of the protection of personal information must be consulted from the outset, the new system must be able to return computerized information to the individual in a structured, commonly used format, and the assessment must be proportionate to the sensitivity, purpose, quantity, distribution and storage medium of the information (LégisQuébec, current to October 15, 2026). The Commission d'accès à l'information (CAI) lists examples of "information systems" that include collaboration and videoconferencing software, payroll systems, video surveillance and AI systems, and examples of electronic service delivery such as a member area on a website or a mobile app (CAI, 2024). That covers most SaaS purchases.
Section 17 requires the assessment to weigh the information's sensitivity, the purposes, the protection measures (including contractual ones) and the legal framework of the destination. The transfer may proceed if the assessment establishes that the information would receive adequate protection, and it must be covered by a written agreement that reflects the results (LégisQuébec, 2026). The CAI's guide is blunt: if you conclude protection would not be adequate, you must refuse to send the data (CAI, 2024). Both obligations have applied since September 22, 2023, and the CAI recommends a PIA even outside the mandatory cases (CAI, 2024). For which businesses outside Quebec the act reaches, see our Quebec Law 25 explainer and our review of the CAI's enforcement record.
Federal: A Useful Model, Not Your Obligation
Many guides still cite the federal Directive on Privacy Impact Assessment, but the Directive on Privacy Practices, effective October 9, 2024, replaced it and added a Standard on Privacy Impact Assessment as Appendix C (TBS, 2024). It binds government institutions, but two ideas transfer well to a business: a short documented checklist to decide whether a PIA is needed, and updates triggered by substantial changes, including new or modified technology or a new third party under contract, with mitigation measures reviewed annually. Institutions must send completed PIAs to the Treasury Board of Canada Secretariat (TBS) and the OPC (TBS, 2024); since July 9, 2025, TBS has strongly encouraged them to use the OPC's online PIA form, though it is not mandatory (TBS, 2025).
Ontario and Health
Amendments to Ontario's FIPPA in force July 1, 2025 require the head of each institution, unless the regulations provide otherwise, to have a written PIA prepared before collecting personal information. It must cover, among other things, purpose, necessity, legal authority, data types and sources, who can access the data, retention, safeguards and a summary of risks with mitigation steps, and must be updated before a significant change of purpose and provided to the IPC on request (FIPPA s. 38(3) to (6), Ontario e-Laws, consolidated from September 15, 2026). The rule binds public institutions, not private businesses. We could not confirm a general statutory PIA duty for Ontario health custodians under PHIPA, so we make no claim about one. In Alberta, by contrast, health custodians must submit PIAs before implementing or changing systems that handle identifying health information (OIPC Alberta, read November 16, 2026).
PIPEDA: No Rule, but a Clear Expectation
PIPEDA does not mention privacy impact assessments (Justice Laws, current to October 19, 2026). It does make you responsible for information transferred to a third party for processing and requires contractual or other means to give it comparable protection (Schedule 1, clause 4.1.3). The OPC, with the Alberta and BC commissioners, has said that assessments should be required for all new projects involving personal information, using PIAs and security threat and risk assessments (OPC, 2012). The OPC repeats the expectation for generative AI (OPC, 2023), and on September 10, 2026 it published guidance on assessing third-party service providers before working with them, open for comment until December 4, 2026 (OPC, 2026). Federal reform is pending: as of November 16, 2026, Bill C-36 is at second reading in the House of Commons (LEGISinfo, 2026). Our PIPEDA explainer covers the basics.
Laptop stolen from an employee's vehicle, Laval
Unencrypted drive. 1,840 clients in QC, ON and AB: names, SIN, banking details.
Notification letters prepared: 412 of 1,840
Step 1
Personal information under your control involved?
Step 2
Real risk of significant harm?
PIPEDA
Report to OPC
Notify individuals
As soon as feasible
Quebec Law 25
Report to CAI
Notify persons concerned
Promptly
Alberta PIPA
Notify Alberta OIPC
Notify individuals
Without unreasonable delay
The Template: Sections and the Questions to Answer
This starting point draws on the CAI's six-step process, the OPC's third-party checklist and the content Ontario requires of its institutions. It is not legal advice or an official form. Scale it: the CAI accepts that a smaller project can be documented with meeting notes or emails, provided the reasoning is recorded (CAI, 2024).
0. Screening (one page)
Does the project involve information about identifiable people, including data that becomes identifying when combined? Is it a new, acquired or overhauled system? Will any data leave the province or Canada? Is any of it sensitive (health, financial, biometric, children's)? If the answer is "no PIA", write down why.
1. Project description
What are you doing, why, who owns it, and when does it go live? Who is the privacy officer, and when were they consulted?
2. Personal information inventory
Which data elements, about whom (customers, staff, patients, minors), from which sources, and in what volume?
3. Data flow map
Where is each element collected, stored, backed up, accessed and sent? Include the vendor's subcontractors and storage locations, which the OPC's third-party guidance specifically asks you to map (OPC, 2026).
4. Purpose, necessity and proportionality
Is every element needed for a stated purpose? Is there a less intrusive way? The CAI notes that a project that is not necessary and proportionate is not legal (CAI, 2024).
5. Authority, consent and transparency
What is the legal basis or consent for each use? Does your privacy notice cover it? Will the vendor use the data for its own purposes, such as training a model?
6. Third parties and jurisdictions
Which providers and subcontractors are involved, in which countries? What does the contract say about use limits, breach notice, audits, return and deletion? For Quebec data leaving Quebec, record the section 17 factors and your adequacy conclusion.
7. Safeguards
Access control and MFA, encryption, logging, backup and the vendor's independent assurance. Who manages the security settings, you or the vendor? A cyber risk assessment can feed this section.
8. Retention and destruction
How long is each element kept, and how is it destroyed, including in backups and at contract end?
9. Individual rights
How will you answer access and correction requests, and in Quebec, portability?
10. Risk register
For each risk: what could happen to the individual, likelihood, impact, mitigation, owner and due date.
11. Decision and sign-off
Proceed, proceed with conditions, or stop. Who approved it, and on what date?
12. Review
What changes trigger an update (new feature, new vendor, new data, new country), and when is the next scheduled review?
Worked Example: A Retailer Adopts a US-Hosted Marketing Platform
This example is illustrative and generic, not a real client. For example, a 40-person home goods retailer with stores in Ontario and Quebec plans to replace spreadsheets with a SaaS customer and SMS marketing platform hosted in the United States. It will hold names, mobile numbers, email addresses, postal codes and purchase history for loyalty members.
- ScreeningQuebec's act applies to the Quebec stores' customer data, so section 3.3 applies (an acquired information system) and so does section 17 (hosting outside Quebec). PIPEDA governs the Ontario side. A full PIA is needed.
- Inventory and flow mapThe team finds the vendor also collects device and location data through its SMS link tracking, and uses a subprocessor for message delivery.
- NecessityBirthdates were on the vendor's default form. Marketing only needs month, so the team drops full birthdates. Location tracking is switched off because no stated purpose needs it.
- Third party and jurisdictionThe contract is amended to bar the vendor from using customer data to train its models, require breach notice within a set number of hours, list subprocessors and require deletion at termination. The team records the section 17 factors and concludes protection is adequate with those terms, and the written agreement references the PIA.
- SafeguardsSingle sign-on with MFA for staff, role-based exports limited to two managers, audit logs reviewed monthly.
- TransparencyThe privacy notice is updated to say that data is stored in the United States and may be accessed by authorities there.
- DecisionProceed with conditions, signed by the owner and the privacy officer, with review in 12 months or at the next new feature.
The result: less data collected, a tighter contract and a record a regulator can read.
What to Do Now
- List the systems you have bought or changed since September 22, 2023 that touch Quebec residents' data, and check each for a PIA.
- Add the screening questions to your purchasing process, so no SaaS contract is signed without one.
- Name a privacy officer who is consulted at the start of projects, not after go-live.
- Keep a short vendor questionnaire based on the OPC's third-party guidance and attach answers to each PIA.
- Link your PIA risk register to your breach plan, so the same data map supports breach response.
- Diarize reviews: the federal standard's annual review of mitigation is a sensible cadence for a business too.
How Cyberphore Can Help
Cyberphore helps Canadian organizations decide when a PIA is required, run assessments of new systems and SaaS providers, and turn the findings into contract terms and security controls. Our team holds industry certifications (CISSP, CISM, OSCP, GIAC and vendor certifications), and pricing is quote-only after a free scoping call. Learn more about our privacy compliance service.


