Québec Law 25
Find the Québec-specific rules for privacy governance, systems projects and disclosures outside Québec.
Personal Information Protection and Electronic Documents Act · Canada
Apply Canadian private-sector privacy principles and determine which federal or provincial law governs.
Organizations handling personal information in commercial activities covered by PIPEDA, including qualifying interprovincial and international transactions.
Documented privacy accountability with incident and breach records.
Alberta, British Columbia and Québec have substantially similar general private-sector laws. Check applicable health and provincial laws for the specific activity.
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Fill this in with your sponsor and send it to the people who own the work.
PIPEDA kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Determine federal and provincial scope · Privacy counsel + operations [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
Checklist, instructions and 11 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Determine federal and provincial scope | Privacy counsel + operations | At initiation | Set a start date | Jurisdiction matrix; Data flows | Open |
| Assign accountability and document consent | Privacy officer + product | Before covered collection | Set a start date | Accountability charter; Consent and purpose record; Notices | Open |
| Implement safeguards and individual access | Security + privacy operations | Ongoing | Set a start date | Safeguard matrix; Supplier terms; Rights runbook | Open |
| Record breaches and escalate reportable cases | Incident lead + privacy officer | At incident and ongoing | Set a start date | Risk determination; Breach register; Notices | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Map jurisdictions, commercial activities and data flows, then identify applicable provincial and sector regimes.
Fictional details. Use the same fields with evidence from your work.
A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.
Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.
Fictional details. Use the same fields with evidence from your work.
An engineer can trace collection to deletion, and a reviewer can see every crossing or third-party handoff.
Use the worksheet to design the diagram. Share the diagram with the people confirming scope, transfers or controls.
Set purposes, design meaningful consent or document an exception, limit collection and publish clear privacy practices.
Fictional details. Use the same fields with evidence from your work.
The signer can explain the basis for each statement and the record reflects the required scope and period.
Give the executed document to the relevant recipient under the engagement or regulation. Use the worksheet to organize review.
Fictional details. Use the same fields with evidence from your work.
The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.
Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.
Fictional details. Use the same fields with evidence from your work.
A reader can understand the intended use and reach the correct rights channel. The notice matches what the service actually does.
Send approved text to the publishing owner and give support teams the version and effective date.
Apply safeguards appropriate to sensitivity, control third-party handling, and test access and challenge procedures.
Fictional details. Use the same fields with evidence from your work.
A different person can operate the control or test it using the matrix and its evidence links.
Give the baseline to control owners and the assessor before walkthroughs or sampling.
Fictional details. Use the same fields with evidence from your work.
The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.
Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.
Fictional details. Use the same fields with evidence from your work.
A new case worker can follow the procedure and deliver a test response without inventing missing steps or timings.
Train intake, operational and backup staff. Make the intake instructions and current contact list easy to find.
Assess real risk of significant harm. Notify the OPC and individuals where required and retain records of all breaches of security safeguards.
Fictional details. Use the same fields with evidence from your work.
The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.
Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.
Fictional details. Use the same fields with evidence from your work.
Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.
Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.
Fictional details. Use the same fields with evidence from your work.
A reader can understand the intended use and reach the correct rights channel. The notice matches what the service actually does.
Send approved text to the publishing owner and give support teams the version and effective date.