What should Canadian leaders check before an AI pilot?

A Canadian AI pilot needs more than a Canadian hosting label. Before personal information enters the proposed workflow, identify the privacy rules that apply to the organization, establish where the information will actually be handled, and resolve any assessment required before the project or transfer proceeds.

Those questions can change the first step. A private business in Québec may need to involve its privacy lead while acquiring the system, rather than waiting for a final launch review. A processing location elsewhere in Canada can also be outside Québec. Treating both places as simply “Canadian” loses a distinction that matters.

This article focuses on private-sector pilots. Public bodies, health organizations and other regulated activities need their own applicable requirements established. The wider AI adoption strategy still matters, but a national rollout plan cannot settle the conditions for a particular use of personal information.

Start with the applicable privacy regime

Do not put “PIPEDA compliant” into a pilot brief as if it answered every Canadian privacy question. PIPEDA is the federal private-sector privacy law, but Alberta, British Columbia and Québec have substantially similar private-sector laws that generally apply within those provinces. PIPEDA remains relevant to federally regulated businesses and commercial personal-information flows across provincial or national borders. Its employee-information coverage is also limited to federally regulated businesses. The Office of the Privacy Commissioner explains these boundaries.

Give the responsible privacy lead enough detail to identify the applicable regime. Useful questions include:

• What kind of organization is proposing the pilot, and where does it operate?
• Whose personal information would be involved, and for what purpose?
• Which organizations would receive or handle that information, and in which locations?
• Would the use involve employees, customers or another group with different requirements?

These are questions to resolve, not a self-service legal classification. A national company may need a more specific answer than the province on its head office address. Ask for the conclusion and its implications for this pilot, including anything that must happen before acquisition or testing.

Follow the processing beyond the hosting label

A supplier's answer about storage may cover only part of the service. Ask what happens when the feature you intend to use runs, including associated services and any relevant support or subcontracted handling. Obtain an answer for the proposed product, configuration and contract, rather than relying on the supplier's general description of its Canadian presence.

Cloud consultant Martin Bunting's October 2026 discussion of data residency and sovereignty makes this tangible through a contact-centre example. The location of the core platform does not, by itself, answer where associated transcription or AI processing takes place. His architectural example gives a useful procurement question: does the location answer cover the capability you will actually enable?

For a proposed workflow, ask the supplier to explain:

• The input path. Where would the information go when someone submits it?
• The processing path. Which services would handle it to produce the requested result?
• The retained material. What inputs, outputs or other records would remain, where, and under what terms?
• The unconfirmed parts. Which answers still require confirmation for this configuration?

A missing answer should remain visible in the proposal. It should not become “Canada” because one part of the product has a Canadian location. For deeper supplier and contract questions, use the AI vendor evaluation guide.

Canadian handling is not a complete approval test either. The OPC's outsourcing guidance for businesses explains that PIPEDA permits outsourcing while retaining the organization's responsibility for protecting personal information, whether processing occurs in Canada or abroad. That does not override other applicable requirements or the organization's contracts.

Compare the two Canadian proposals

Suppose Alex Morgan coordinates operations at a private professional training company in Québec. The company wants to use AI to analyze course-registration emails and draft a list of common questions for staff. The emails contain names and contact details. Staff would check the draft before using it; the pilot would not decide individual enrolment eligibility or send messages to applicants.

The supplier offers a Montréal-processing proposal and a Toronto-processing proposal. Alex has not yet established the complete information path for either option. The useful comparison is therefore about the questions each proposal raises, not which city receives an approval tick.

Where Québec's private-sector requirements apply, the Commission d'accès à l'information explains that acquiring, developing or redesigning an information system or electronic service involving personal information requires an assessment of privacy-related factors, called an EFVP in French. The person responsible for personal-information protection must be consulted from the outset. The CAI's guidance for private enterprises describes this project requirement and the assessment's proportionate scope.

That makes the privacy lead part of Alex's early project discussion. Choosing a Montréal option would not remove the project question. Nor should Alex promise to complete the review only after staff have tested real registration emails.

Toronto introduces another distinction. The CAI explicitly treats a destination elsewhere in Canada as outside Québec. Its private-enterprise guidance on use and communication describes the assessment before communicating information outside Québec or entrusting an outside entity with its collection, use, communication or storage, together with adequate protection and a written agreement.

Location review is only part of the decision; the privacy lead must also establish the conditions for the proposed use, including any applicable consent requirements. This does not mean the Toronto proposal automatically fails. It means “still in Canada” does not resolve the applicable assessment and agreement. Likewise, the Montréal proposal's name does not prove that every relevant activity stays within Québec. Alex needs the actual arrangement reviewed, including any handling beyond the advertised location.

Make the next decision specific

Alex can now bring the two proposals to the privacy and procurement owners with a concrete question: what must be resolved before registration emails can enter either arrangement?

The answer should distinguish what is known from what is still pending. A short decision record can identify:

• The proposed registration-email use and its limits.
• The applicable requirements and the owners responsible for resolving them.
• The supplier's confirmed arrangement and the review that addresses it.
• The conditions that must be met before personal information enters the workflow.

An unexplained “approved in Canada” label would hide those decisions.

For Alex's team, a separately permitted rehearsal could use invented registration questions containing no personal information. That would let staff examine whether the proposed output is understandable and useful while the personal-data proposal awaits review. It would not test the handling of real emails or substitute for the assessment required for the proposed system.

Keep that distinction clear when reporting progress. “Staff rehearsed the draft FAQ task with invented questions” is more informative than “the Canadian pilot passed.” The latter hides both what people practiced and what remains unresolved.

The workflow launch review guide covers the wider review of the actual task, permissions and safeguards. For a multinational program, the local adoption coordination guide explains why a shared tool does not establish that every local task is ready. Use these alongside the Canadian requirements, with each question given to an owner who can resolve it.

Questions and answers

Does PIPEDA cover every Canadian private business in the same way?

No. Provincial private-sector laws, federally regulated activities and cross-border commercial flows affect the answer. PIPEDA's employee-information coverage is not universal either. Start with the OPC's applicability explanation, then have the responsible privacy lead identify which requirements govern the organization and proposed information use. A general vendor compliance statement cannot make that determination for your pilot.

Must every Canadian AI pilot keep all information in Canada?

There is no universal Canada-only rule established by PIPEDA's outsourcing guidance. The organization remains responsible for protection when it outsources processing, including abroad. Other applicable requirements and contractual commitments may constrain the proposal. Read the OPC's outsourcing guidance and verify the full arrangement with the responsible owners before entering personal information. Canadian storage alone does not establish approval.

Is Toronto outside Québec for the location assessment?

Yes. The CAI's private-enterprise guidance includes destinations elsewhere in Canada within its outside-Québec discussion. For a proposed Toronto arrangement subject to those requirements, resolve the applicable assessment and agreement before the relevant handling proceeds. Check the CAI's explanation, including the actual activities entrusted to an outside entity. Neither a Toronto nor a Montréal product label establishes the complete information path.

Does a private firm have to use the federal Algorithmic Impact Assessment?

The federal Directive on Automated Decision-Making concerns federal departments and administrative decisions within its scope. It is not a blanket requirement for every private firm's AI pilot. The Treasury Board's scope guide explains the boundary. A private organization may find a framework useful voluntarily, but completing it does not replace the privacy or other review applicable to its own proposed use.

Can staff practice while the personal-information proposal awaits review?

A separately permitted exercise using invented material without personal information can help staff rehearse a task. For the registration-email example, that means invented questions used to inspect a draft FAQ, with the real emails excluded. Confirm permission for that exercise and describe its limited purpose. It does not clear the system for personal-data use or replace a required pre-project assessment. Keep the wider launch review tied to the actual proposed workflow.