The Sovereign profile of Tonia pairs tonia with an on-site tonia: review of a discovery file, analysis of a draft contract, assisted case-law research — every request touching professional secrecy executes on-site, never cross-border. The Frontier profile routes the rest to a frontier-model provider with redaction, policy, and signed audit. You start on Frontier, you switch to Sovereign by adding on-site tonia; your audit log for the syndic carries over.
A Quebec law firm operates under two simultaneous regimes: Bill 25 (CQLR, c. P-39.1) like any private organization, and the Code of professional conduct of lawyers (CQLR B-1, r. 3.1), which imposes a professional-secrecy duty stricter than the cross-sector norm.
The practical consequence is sharp: a lawyer pasting a draft contract or a client memo into ChatGPT communicates professional secrecy to a Delaware corporation subject to the CLOUD Act — without client consent, without an art. 17 assessment, without a contractual framework. This communication is, on its own, a potential breach of art. 60 and a non-compliant transfer under Bill 25 art. 17.
(contracts, memos, pleadings). The most common case. The Bill 25 / art. 60 friction is immediate: pasting a real draft — which carries the client's name, contact information, file facts — into ChatGPT communicates professional secrecy to a U.S. corporation. No client consent has covered this act.
(decision summaries, precedent search). Less sensitive if the request carries no client identifier. Still problematic if the question wording reveals unique factual elements of the file — "my client, a Quebec auto manufacturer in a federal patent-infringement dispute for 18 months" identifies the case to a judgment.
. This is the highest-economic-leverage case for commercial-litigation firms: review of large document volumes (often in English, often coming from the opposing party). It is also the highest-risk case — the mass transfer of potentially confidential documents to a U.S. cloud provider exposes the firm to a simultaneous breach of art. 17, art. 60, and art. 78.
Sensitive categories execute on the on-site tonia installed in your firm. No document leaves. Bill 25 art. 17 does not apply, for lack of transfer. The locally signed audit log documents every request for the syndic's annual review.
The Frontier profile routes approved requests to a frontier-model provider with PII redaction (client names, file identifiers) and policy signed by the file's responsible partner. The exportable audit log answers the syndic's request in case of audit; redaction guarantees no identifier leaves Québec.
Preliminary draft (standard contract template, general orientation memo) → Frontier profile. Active confidential document (contract with client facts, active litigation memo) → Sovereign profile. The firm switches from Frontier to Sovereign by adding on-site tonia; the audit log carries over, and Tonia keeps the same policy and history.
Mid-sized commercial-litigation firm, federal and provincial practice, 12 lawyers + 8 support, deployed under Tonia — Sovereign profile in Q2-2026. Anonymization required absent written agreement. Barreau review for pre-publication deontology validation.
The firm had been running its discovery document review on a U.S. cloud service since 2023. The new Barreau administration and the 2026 update of the AI guide triggered a review of the setup. Internal Bill 25 audit in March: 4 categories non-compliant with art. 17, 1 category in potential non-compliance with art. 60.
Switch in Q2: on-site tonia installed in the firm's server room, policy configured by the PRPRP in collaboration with the managing partner, 2-h training of the 20 users. The Sovereign profile absorbs the full document review — 100% of discovery requests execute on-site. The Frontier profile remains enabled for case-law research (category classified as non-sensitive), with active PII redaction.
BLOCK event count (PII patterns detected by the DLP engine)Want to see how this applies in your firm? Start with the free Loi 25 audit, then request a 30-min consultation. We will review your three use cases, sector obligations, and on-site tonia sizing if your context calls for it.
Disclosure notice: this page is editorial and reflects Tonia's commercial position. Regulatory references are verifiable at the indicated links. Before acting, validate the obligations specific to your organization with your counsel.