Reviewing privacy when business tools change
Check personal information flows when adding AI, monitoring or cloud features, with clear collection purposes, supplier questions and usable privacy choices.

A software update can introduce a new way to use personal information: an AI assistant, a staff analytics report or another cloud integration. The feature may be available before your business has decided whether to use it.
Treat a change in collection or use as a reason to review the workflow. A vendor’s privacy badge won’t tell you whether your use of the feature meets your obligations.
Map what changes
Record the information entering the tool, the purpose, the people affected and the intended output. Include information inferred from activity as well as fields someone types into a form.
Ask which supplier and internal roles can reach it. Check copies in logs, exports, integrations and support systems. Draw a simple before-and-after flow so the change can be discussed with the business owner and privacy lead.
Check AI use separately
Canada’s privacy regulators’ generative AI principles address lawful authority, appropriate purposes, minimization and safeguards. Those questions apply when introducing an AI feature, even if the business already uses the underlying software.
Use non-personal test information where possible. Confirm whether prompts, source records and outputs are retained or used by the supplier, and read the service terms and check the settings yourself.
A tool that helps find sensitive records has to read them to do it, which can be a new use or disclosure of that information in itself.
Make privacy choices usable
Explain what the feature does in language the affected person can understand. Test whether notices and available choices work on a phone and with a keyboard.
Name the person who handles requests to see or correct personal information. A new settings page doesn’t replace that job. Rights differ between federal and provincial laws, so match the process to the ones that apply to you.
Ask more than where the server is
The Privacy Commissioner’s cross-border processing guidance explains accountability for outsourced processing under PIPEDA. A Canadian hosting location alone doesn’t settle supplier access, subcontracting or your full legal obligations.
Review the contract, processing locations, support access and incident responsibilities. Provincial laws, sector rules and contracts can add limits, so get advice for the use you have in mind.
Record the decision, required settings and a review trigger. That might be a new integration, a changed supplier term or a wider staff rollout. Our application development work can help document the technical flow for that privacy review.


