Professional secrecy for lawyers and notaries, protected by the Charter and the Code des professions, is not the same duty as personal-information governance. A firm still holds both: what the client tells counsel becomes a file that is hosted, consulted, exported and sometimes entrusted to a vendor. Quebec’s Law 25, federal PIPEDA, and the PIPA statutes of British Columbia and Alberta now require written proof — consent, an audit log, an incident register — that a law society and the Commission d’accès à l’information (CAI) can ask for. This guide maps those regimes and separates geographic hosting from true legal sovereignty.
Regulatory foundations and reference texts
Quebec — Barreau du Québec
CQLR c. B-1, r. 5, ss. 49–56
The named accounting file stays under professional secrecy.
Ontario — Law Society of Ontario
LSO By-Law 9, ss. 7–18
Trust books are not a freely shared commercial file.
British Columbia — LSBC
LSBC Rules, Part 3, Division 7
A law society inspection does not displace the provincial PIPA.
Alberta — Law Society of Alberta
LSA Rule 119
Rule 119 does not displace Alberta PIPA.
Quebec — Law 25
CQLR c. P-39.1, ss. 3.1–3.8
Privacy officer, consent, a PIA and an incident register.
Federal — PIPEDA
S.C. 2000, c. 5, Schedule 1
Consent and safeguards under the Schedule 1 principles.
Inspection pitfall versus the law society standard
Risky practice at inspection
Treating a Montreal server as enough while a U.S. vendor stays under the CLOUD Act.
Regulatory requirement and deterministic control
A contract, an audit log and proof the subcontractor does not take professional secrecy outside the firm.
Professional secrecy and statutory duties: two duties, one matter file
Professional secrecy covers the confidence. Privacy statutes cover the life cycle of the information: collection, retention, access, destruction, subcontracting. A firm can honour secrecy and still fail Law 25 if it does not document consent, has not appointed a privacy officer, or entrusts the file to a vendor without a privacy impact assessment (PIA). Conversely, a perfect register does not excuse a breach of secrecy when an access request is too broad. Modern governance requires both proofs, side by side.
Canadian hosting versus legal sovereignty: the CLOUD Act
A U.S. vendor can place its servers in Montreal or Toronto. The physical location reassures. It does not settle legal control. The Clarifying Lawful Overseas Use of Data Act — the US CLOUD Act, 18 U.S.C. § 2713 — lets a U.S. authority order production of data a U.S.-controlled provider holds, even when the bits sit outside the United States. Without a prior Canadian court process, the firm learns after the fact that a confidential file was extracted. True sovereignty therefore combines a Canadian contracting entity, Canadian hosting and backups, and no U.S. control over keys and access. Marketing “data residency” alone is not enough for professional secrecy, Law 25 governance or a PIPEDA accountability review.
For a law firm the question is therefore not “is the server in Canada?” It is “who can order production of the file, and before which court?” If the answer runs through a U.S. authority without a Canadian filter, professional secrecy and Law 25 / PIPEDA duties are exposed — even with a handsome map of Beauharnois or Toronto data centres on the vendor’s marketing site.
Four Canadian personal-information regimes
The table compares the control points a firm meets in practice across Quebec’s Law 25, federal PIPEDA and the PIPA statutes of British Columbia and Alberta. Always confirm the current text with counsel and, in Quebec, with the Commission d’accès à l’information before adopting a new vendor or a new cross-border transfer pattern.
Law 25, PIPEDA and PIPA: governance for law firms
↔ Swipe| Regime | Territory | Privacy officer / governance | PIA and transfers | Incidents and notification |
|---|---|---|---|---|
| Law 25 (Quebec) | Quebec | Designated privacy officer, written policies, registers | PIA before certain transfers outside Quebec; cloud documentation | Confidentiality incident register and notification by threshold |
| PIPEDA | Federal and provinces without substantially similar private-sector law | Firm accountability, consent, access, reasonable security | The firm remains responsible for the subprocessor | Breach notification under the federal regulation |
| PIPA — British Columbia | British Columbia | Responsible organization, policies and access | Documented transfers; vendor accountability | Notification under provincial requirements |
| PIPA — Alberta | Alberta | Responsible organization, policies and access | Documented transfers; vendor accountability | Notification under provincial requirements |
Operational checklist in six pillars
- Appoint the privacy officer — Name the person responsible for personal information and document the mandate.
- Timestamped consent — Collect and keep consent with a timestamp, purpose and channel (portal, form, email).
- Ethical walls and roles — Segment matters behind ethical walls and control access by role, including support staff.
- Immutable logging — Record views, exports and edits in an audit log no one can rewrite.
- Incident register — Keep the confidentiality incident register, with the notification decision and attachments.
- Retention and destruction — Apply a retention policy by matter type and prove secure destruction.
Ethical walls, PIPEDA and the client portal: one audit trail
Ethical walls do not only protect against conflicts of interest. They limit who may view personal information, which ties directly to PIPEDA and Law 25. A properly segmented client portal reduces unencrypted email of exhibits. Every portal view, every export and every time-limited share must leave a line in the log. That trail — not a PDF policy forgotten on a network drive — is what the CAI and the law society can ask for. Without it, the firm reconstructs access history under pressure and often discovers gaps that should never have existed.
Software built for Canadian firms embeds these registers in daily work: portal consent, ethical walls when a matter opens, an audit log on every export. The tool does not absolve the firm. It makes visible, in minutes, what the law society and the CAI expect to see. Data sovereignty then stops being a slogan: it becomes an audit trail the firm can produce, including when a U.S. vendor’s marketing page claims Canadian residency while remaining subject to the CLOUD Act. That is the standard Canadian counsel should demand.
Deterministic check
Law 25 / PIPEDA express diagnostic
Optimal sovereignty and compliance (100/100)
Associated requirements: Law 25, ss. 3.1 to 3.8; PIPEDA Schedule 1; the professional code of conduct.
Inspection questions — privacy
01
Is a server in Montreal enough against the CLOUD Act?
No, if the publisher or a subcontractor remains subject to 18 U.S.C. § 2713. The location of the disk does not decide who can compel production of the file.
02
When must the CAI be notified?
As soon as an incident presents a risk of serious injury, under sections 3.5 and following of Law 25. The register records the date of awareness, even if notice has not yet gone out.
03
Does professional secrecy displace Law 25?
No. Secrecy limits what may be disclosed. Law 25, PIPEDA and the code of conduct still require an officer, a register and an audit trail.