A firm of one to thirty lawyers often hears that a tool is “compliant with the Barreau.” That sentence names neither the host, nor the subprocessors, nor who can open the file. Before a mandate is loaded into a cloud tool, the Barreau du Québec expects a written sheet: where the copies sit, who can reach them, and how professional secrecy is kept. If a notary practises in the same office, the Chambre des notaires expects its own sheet for the minute and the greffe. Law 25 and PIPEDA stand beside that sheet. Secrecy, a matter of public order, binds the advocate and the notary under section 9 of the Charter of Human Rights and Freedoms. A hosting contract does not release them.
What the sheet must name before the first mandate
A useful sheet is dated and signed by a person who can bind the provider. It states the legal name, the country of incorporation and, where there is one, the parent. It locates the servers, the backups, the logs and the copies support staff can open, with the country of each. The word Canada is not enough. The code of ethics of advocates and the Chambre’s rules add secrecy to the Charter duty: the firm must know who, at the provider, can read the content. A certification logo does not name that person. Without those names, do not open a pilot file.
Trust movements that pass through the tool remain books. The Barreau regulation on advocates’ accounting and standards of professional practice, and the Chambre regulation on trust accounting, judge the deposit register, the cheque register and the client cards. A screen that cannot give them to the inspector does not replace those books. The account is not a fiducie under articles 1260 and following of the Civil Code of Québec. Articles 2138 and 2139 still require an account of it. The hosting sheet and the extraction of the books are filed together.
The contract, the subprocessors and notice
Section 18.3 of the Act respecting the protection of personal information in the private sector requires a writing when the firm entrusts collection, use, communication or keeping to someone else. The writing limits use to the contract, sets out the measures and forbids keeping the information after expiry. The Barreau sheet and that writing are one bundle. If a copy leaves Quebec, section 17 requires a privacy impact assessment before the communication. Servers announced in Montreal do not answer that section when the backup goes elsewhere. The assessment comes before the pilot.
What the sheet should cause the firm to refuse
A subprocessor list “on request,” a hosting move without notice, support staff who open a file without a ticket from the firm, and an export whose price is not written are four reasons not to load a mandate. The firm records the gap, with the date, in the governance file. It does not hand over a real file to finish the demonstration. The marketing page remains a brochure until the letter names the entity, the countries, the subprocessors, notice and exit.
Audit progress: 0 / 8 control points verified (0%) —
- The firm records the contracting party’s name, its country of incorporation and the parent, and files that page with the contract.
- The firm notes the country of the servers, the backups, the logs and every copy support staff can open.
- The firm obtains a dated list of subprocessors, with the role of each and the confidentiality clause that binds them.
- The contract states who can decrypt the file and whether the firm must authorize each support access.
- The firm requires written notice before a change of hosting country, of parent, or of a subprocessor who can read.
- The firm requires incident notice within a delay that lets the privacy officer keep the register and give notice if required.
- The firm sets the format, the delay, the cost and the deletion of copies, including at subprocessors, when it leaves the tool.
- If a minute or the notary’s repertory must enter the tool, the Chambre’s sheet is signed first.
Cloud sheet: what must be named before a file is loaded
↔ Swipe| Document | It names | Gap that blocks loading |
|---|---|---|
| Hosting | Entity, country of incorporation, country of each copy | The word Canada with no country for the backup |
| Subprocessors | Name, country, role and confidentiality clause | An undated web page |
| Secrecy | Who may read, support ticket, key holder | Support staff who can open any file |
| Section 18.3 | Purpose, measures, end of retention at expiry | Click-through terms |
| Section 17 | Assessment if a copy leaves Quebec | An assessment started after the pilot |
| Chambre | Minute and greffe, if a notary practises | The advocate’s sheet reused for the minute |
| Exit | Format, delay, cost, deletion of copies | An export price “to be discussed” |
| Books | Deposit register, cheques, client cards | Books that exist only on a screen |
What does not change outside Quebec
The questions do not shrink when a matter is kept under the common law. The Law Society of Ontario’s rules hold the lawyer to confidentiality, and By-Law 9 requires books that can be produced, on a screen or on paper. Part 3, Division 7 of the Law Society of British Columbia, Rule 119 of the Law Society of Alberta and the rules of the Law Society of New Brunswick (LSNB) ask the same of the books. PIPEDA, and PIPA in British Columbia and in Alberta, leave the firm accountable for the provider. Common-law privilege does not have the reach of Quebec public-order secrecy. The written question remains: who hosts, who can be compelled, and how the books come out.
This text stops at what the Barreau, and the Chambre when a notary is present, ask to be written before the file moves. The guide linked below places that sheet inside Law 25, PIPEDA and the sovereignty of the file. Return to it if the parent is sold or a subprocessor is added. The date on the sheet can be read without opening the confidence.