ABA Model Rule 1.6 Alignment
Model Rule 1.6(c) requires a lawyer to make reasonable efforts to prevent unauthorised disclosure of information relating to the representation. This is how each platform control maps to that duty.
Alignment mapping, not certification. Your state's rule and its comments govern; several states differ from the Model Rule text.
Comment [18] factors, mapped
- Sensitivity of the information — the most sensitive matters can be processed with the appliance in Offline mode, physically disconnected from any network.
- Likelihood of disclosure absent safeguards — there is no egress path for client content, and matter workspaces are isolated at the database level on the box.
- Cost of employing additional safeguards — 100% on-premise & contained operation is the default configuration, not a paid add-on you might forget to enable.
- Difficulty of implementing safeguards — the protection is structural. A user cannot turn off confidentiality from the UI, because there is nowhere for data to go.
- Extent to which safeguards adversely affect the lawyer's ability to represent clients — the full, unredacted matter is available to the local engine, so work product reads normally.
Rule 5.3 — supervising non-lawyer assistance
Treat the appliance as delegated work. The audit trail gives you the supervision record: what was asked, which local engine handled each step, and what came back. The citation-grounding pass surfaces claims your own indexed documents do not support, which is where supervisory review should start.
Rule 1.1 Comment [8] — technological competence
The platform is explicit about its limits: a local open-weight engine trades some raw capability for confidentiality, model outputs can be wrong, and grounding scores are indicators rather than guarantees. Those limits are documented so that a lawyer using the tool can be competent about it.
Need this in writing for your review?
We share the underlying documentation with security and risk teams under NDA, and will walk your counsel through anything on this page.
Request documentation