Guide · June 22, 2026 · 3 min read
Privacy-First Document AI: FIPPA, Canadian Residency, and Never Training on Client Data
Case files are among the most sensitive records an institution holds. The non-negotiables: data stays in Canada, client data never trains models, access is need-to-know and logged, and the vendor can prove all of it in a threat and risk assessment.
A case file is a person’s medical history, employment history, and misfortunes, bound in one folder. Putting that through an AI pipeline is a privacy decision before it is a technology decision. Institutions governed by Ontario’s Freedom of Information and Protection of Privacy Act (FIPPA) — and their equivalents across Canada — carry obligations that no vendor’s enthusiasm can waive. The good news: a document pipeline can be designed so those obligations are met by architecture, not by policy documents alone.
Residency: where the data is, all of it
Canadian data residency means more than picking a Canadian cloud region for the primary database. It means storage, processing, backups, replicas, and support access all remain in Canada — including the AI services doing OCR and generation. If pages are sent to a model endpoint in another jurisdiction for inference, residency is broken no matter where the database sits. A privacy-first design inventories every sub-processor and every data flow, and can show — on one diagram — that personal information never leaves the country.
Never train on client data
This should be contractual and technical, not a promise. Client documents must never be used to train, fine-tune, or improve models that serve anyone else. Technically, that means inference-only use of models, retention settings that do not feed provider training pipelines, and contractual terms with every sub-processor that say the same. The one exception is the client’s own system improving for the client: corrections and QA data can tune the client’s own classifiers and golden datasets, inside their boundary, under their control. Anything beyond that is a breach of trust and, in a public-sector context, of obligation.
Access: need-to-know, logged, revocable
Inside the pipeline, personal information is accessible only to the people and services that need it for a defined step — and in many designs, the vendor’s own staff should have no routine access to file contents at all. Role-based access, strong authentication, encryption in transit and at rest, and comprehensive audit logs (who or what accessed which file, when, for what operation) are the baseline. Logs are not bureaucracy: when an incident is suspected, the log is the difference between “we can show exactly what was touched” and a notification to everyone.
The lifecycle: retention and destruction
Privacy obligations do not end at go-live. The design must cover retention (records kept per the institution’s schedule, no longer), retrieval (the institution can get all of its data back, in usable form, at contract end), and secure destruction with evidence when retention expires. A vendor who cannot describe their exit and destruction process in detail has not finished designing the system.
Prove it: the TRA
Public-sector buyers will — and should — run a threat and risk assessment before execution. A privacy-first vendor arrives ready: security and privacy assessment forms completed honestly, controls mapped to recognised standards such as Ontario’s GO-ITS 25.21 cloud security requirements, incident notification commitments measured in hours, and named accountability for security. The assessment is not an obstacle to the sale. It is the mechanism by which a sensitive system earns the right to exist — and vendors who treat it that way tend to build systems that deserve to pass.