For storage, usually yes and you can buy it. For the model call, often not, and the honest answer is to know where it goes rather than to claim it never leaves.
Key takeaways
You can usually keep the stored data in Canada, because major cloud vendors sell that as a product. Keeping the processing in Canada is harder, because model capacity is allocated globally and vendors reserve the right to route elsewhere under load. The workable position for most Canadian firms is not “nothing ever leaves” but “we know what leaves, we contracted for how it is handled, and we can say so when a client asks.”
The Office of the Privacy Commissioner’s guidelines for processing personal data across borders are unambiguous. Canada has chosen an organisation-to-organisation approach rather than the state-to-state adequacy model used in the European Union; PIPEDA does not prohibit organisations in Canada from transferring personal information to an organisation in another jurisdiction for processing; and it does not distinguish between domestic and international transfers. What it does is make the transferring organisation accountable. Principle 4.1.3 of Schedule 1 requires contractual or other means providing a comparable level of protection while the information is processed by the third party — which the guidelines gloss as protection that is generally equivalent rather than identical.
Three further statements in that document matter for an AI decision. The organisation must be satisfied the third party has policies, processes, staff training and effective security measures, and should have and exercise a right to audit and inspect. What an organisation cannot do by contract or otherwise is override the laws of a foreign jurisdiction. And the guidelines accept that the result may be that some transfers are unwise given the foreign regime, or that some information is so sensitive it should not be sent to any foreign jurisdiction at all.
That last sentence is the one to hold onto. The law does not forbid the transfer; it makes the transfer your decision and your responsibility.
They come from tax and records law, not privacy law, and they catch accounting practices in particular.
Subsection 286(1.2) of the Excise Tax Act provides that, unless otherwise authorised by the Minister, a record shall be kept in Canada in English or in French. Subsection 286(1) requires every person carrying on business or engaged in a commercial activity in Canada, and every person required to file a return, to keep all records necessary to determine their liabilities and obligations. Subsection 286(3) sets the retention period at six years after the end of the year to which the records relate, and subsection 286(3.1) requires records kept electronically to be retained in an electronically readable format for that period.
Subsection 230(1) of the Income Tax Act requires every person carrying on business, and every person required to pay or collect taxes, to keep records and books of account at their place of business or residence in Canada or at such other place as may be designated by the Minister. Subsection 230(4)(b) sets the general six-year period, and subsection 230(4.1) again requires electronic records to be retained in an electronically readable format.
These are obligations on records, not on AI. But if a workflow moves a client’s books into a system whose only copy sits outside Canada, the obligation has been engaged by the workflow. That is a design question to settle before deployment, not a compliance question to discover afterwards.
The Commission d’accès à l’information states that since September 2023, before communicating personal information outside Quebec, an organisation must carry out an assessment of privacy-related factors; the communication may be made if the assessment shows the information would benefit from adequate protection; and it must be the subject of a written agreement meeting certain conditions. The Commission also states that an assessment is required for any project to acquire, develop or overhaul an information system involving personal information, and that in every case the assessment must be proportionate to the sensitivity, purpose, quantity, distribution and medium of the information.
Note the direction of travel: Quebec regulates the crossing, not the storage. A Quebec firm is not told it may never use a service outside the province; it is told to assess, document and contract before it does.
Data residency is a purchasable commitment with conditions attached, and reading them is part of the work. Microsoft’s Advanced Data Residency add-on lists Canada among the countries in its Local Region Geography, alongside Australia, France, Germany, India, Japan, the United Kingdom and others. It requires the tenant default geography to be one of those regions, requires specific licence types, and states that customers must cover one hundred per cent of paid licences in the tenant with the add-on for the tenant to receive the data residency commitment. Microsoft 365 Copilot is listed among the covered services.
The general lesson transfers to any vendor. Residency is scoped to named services, is conditional on how you are licensed, and rarely covers every component. Read which services are in scope, then check whether the AI feature you actually want is one of them.
Keeping data on Canadian soil does not by itself determine which government can compel its production; that turns on who controls the provider and under which laws it operates. The OPC guidelines say the same thing from the other direction — that no contract can override the laws of a foreign jurisdiction. Treat residency as one control among several, useful for client confidence and for the tax rules above, and not as an answer to every question a client might ask.
A Saskatchewan accounting practice wants an extraction tool for client source documents. It sets three requirements before shortlisting: the working copy of client books stays in a Canadian region, because of the Excise Tax Act location rule; any model call that leaves the country is disclosed and covered by the vendor agreement; and the firm can produce, on request, a plain statement of where client information goes. Two of five candidate tools meet all three. The firm documents why the other three were excluded, which turns out to be the most reused artefact of the whole exercise.
Countable: tools in production with a written residency scope, matters where a client asked and got an answer the same day, and exceptions logged and approved. Not hours saved.
This page is written for a firm that delivers work to a book of clients. If the question is really about the front desk — intake, scheduling, recall, reminders — that lives on the professional practice owners page. If it is about your own month-end, reconciliation and payables rather than client deliverables, that is accounting automation. The two overlap on tooling and almost never on risk.
Does PIPEDA require Canadian storage?
No. The OPC guidelines state the opposite in terms. What PIPEDA requires is accountability and a comparable level of protection.
Do we have to tell clients their information may be processed abroad?
The OPC guidelines say individuals should expect transparency from organisations about transfers to foreign jurisdictions, and that customers will ask. Treadstone Law’s answer on whether your business needs a privacy policy is the practical starting point for where to say it.
Can we just anonymise and stop worrying?
In Quebec, note the Commission’s statement that anonymisation must follow generally accepted best practices and the criteria set by government regulation. Elsewhere, the OPC asks organisations not to prompt a system to re-identify de-identified data and to treat inferences about an identifiable individual as personal information.
Is a Canadian vendor automatically safer?
Not automatically, but it removes one variable. Ask the same five questions you would ask anyone else, and ask which subprocessors sit behind them.
A 30-minute call is enough to tell you whether AI pays for itself here.
