← Blog
ArticleReading: 5 min

Revised November 2026.

Bill 25 in a Quebec firm: what your tools can track

Bill 25 is more than a PDF policy. Here are the operational artifacts a firm can document — and what your tools can help track.

In this guide

In a firm of one to thirty lawyers, the privacy officer does not reread Law 25 inside the software. The officer asks what the tool recorded. The log says who opened the file, when, and whether there was an export. The time entry may contain the confidence. The trust movement names the client, the matter and the amount. The portal keeps the consent and the downloads. This text stops at those four traces. It does not restate the consent regime, the inventory or the assessment for a transfer outside Quebec, which the guide linked below covers. Professional secrecy, a matter of public order under section 9 of the Charter of Human Rights and Freedoms, remains: the firm produces the trace, not the consultation.

What the audit log must be able to produce

The person who exercises the highest authority, or that person’s written delegate, is the privacy officer. Who touched a file is answered in lines: user, date, action. The action separates viewing, editing, downloading and export. A log that says only “access” does not show that a document left. The officer filters by matter. The firm produces that metadata, not the legal memorandum. The incident register is another document: the wrongful export is entered there, and the log is the voucher.

The log is itself personal information: it names the employee and, through the matter, the client. Section 23 of the Act respecting the protection of personal information in the private sector requires the information to be destroyed, or anonymized, once the purpose is achieved, subject to a period set by statute. Proving an access, answering an incident and answering an inspection are purposes. Keeping every line with no period and no person responsible is not. The log’s period is written beside the file’s period. The two are not merged on the day the documents are destroyed.

The time entry and the trust movement

A time entry is not only a number of hours. The narrative often describes the meeting, a state of health, the family or the opposing party. That text is personal information and, inside the mandate, a confidence. Exporting it to an outside accountant, a portal or a personal mailbox is a communication. It is justified by the purpose, and it appears in the log. An entry whose narrative is too specific to leave the firm is rewritten before the export, or it does not leave. The rate and the duration remain. The clinical or family account does not travel with the invoice if the invoice does not need it.

The trust line is not the signed report

Each movement names the client, the matter, the date, the amount and the voucher. Those names are personal information and the books of the Barreau regulation and of the Chambre’s. The log that says who edited a line does not replace the signed report or the card. The account is not a fiducie under articles 1260 and following of the Civil Code of Québec. Articles 2138 and 2139 require an account of it. A pooled balance that hides the card documents neither Law 25 nor the inspection.

  1. The privacy officer filters the log by matter and by period, and produces the user, the date, the action and the export.
  2. The officer separates viewing, editing, downloading and a sending outside the firm.
  3. The officer enters in the incident register the export or the access that should not have happened, with the log as the voucher.
  4. The officer rereads the time narrative before an export, and removes what the invoice or the accountant does not need to read.
  5. The officer ties each trust line to a matter, to a date of receipt and to a voucher, not to a pooled balance.
  6. The officer keeps the portal consent with the date, the purpose and the channel, beside the client’s access.
  7. The officer sets a period for the log, separate from the file’s period, and names who decides to destroy it.
Four traces in the software and what they do not replace
TraceIt showsIt does not replace
Audit logUser, date, action, exportThe incident register
Time entryDuration, rate, and a narrative that may be confidentialA note that can be sent as it stands
Trust movementClient, matter, date, amount, voucherThe signed monthly report
PortalConsent, upload, view, downloadA clause buried in the retainer
Log periodPurpose, end date, person who decidesKeeping the file with no end
ExportRecipient, date, content that leftAn outside-Quebec assessment already done

The portal, then what the common law asks in addition

The portal is not a silent drop box. It records who signed in, what was filed, what was viewed and what was downloaded. Consent to electronic delivery is tied to it: date, purpose, channel, and the fact that it is separate from the other clauses of the retainer. A portal without that line and without an access log moves documents. It does not document Law 25. When the client files an identity document or health information, the access trace becomes the proof the firm can show without opening the rest of the file. Section 18.3 remains due toward the provider that hosts the portal. It is not restated here: the guide places it with hosting.

Outside Quebec, the trace remains. PIPEDA, and the PIPA statutes of Alberta and of British Columbia, hold the firm accountable for information entrusted to the tool. The log answers an access request within secrecy: who consulted, not the opinion. Law Society of Ontario By-Law 9, 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) judge the books. None says the audit log stands in for them.

Reference guide: Law 25, PIPEDA and data sovereignty