Security & professional responsibility
Legal automation fails on ethics long before it fails on technology. Lexcadence is built around the duties that actually apply to a practising lawyer — ABA Formal Opinion 512 and state bar guidance in the United States, and Federation of Law Societies and provincial law society guidance in Canada.
The duties, and what we do about them
Competence
You must understand the benefits and risks of the tools you use on a client matter.
Every module states plainly what is deterministic template assembly and what is model-generated. Generated passages are marked in the document so a reviewer knows exactly what to check.
Confidentiality
Client information cannot be disclosed, including to a third-party model provider that would learn from it.
Firm data is never used to train third-party models, and it is not retained by model providers beyond the request. Enterprise firms can run in a private deployment. Data is encrypted in transit and at rest and segregated per firm.
Supervision
AI output is work product you are responsible for, the same as a junior's draft.
Nothing leaves the system without a named lawyer's sign-off. The sign-off gate records who approved what, when, and against which version.
Communication
Clients may need to be told how their matter is being handled.
Per-matter disclosure settings and an engagement-letter clause library, plus a client-facing summary of which automations touched their file.
Reasonable fees
You cannot bill hours the software actually saved, and costs passed on must be genuine.
Billing assist records the automation used on each entry so time narratives stay defensible, and per-matter module costs can be posted as disbursements where your rules allow.
Where we deliberately do not use a model
Operative legal language — the wording of a will, a release, a limitation clause, a statutory form field — is assembled from your own approved templates and clause library with deterministic rules. A model does not write it and cannot silently reword it. Models are used for the work where variation is the point: summarising records, extracting facts, comparing a contract against your playbook, and drafting narrative sections that then go to a lawyer.
Controls
US and Canadian hosting regions. Canadian firms can pin all storage and processing to Canada.
TLS 1.3 in transit, AES-256 at rest, per-firm key separation.
Role-based permissions, matter-level ethical walls, SSO and SCIM on Firm and Enterprise.
Every automated action, prompt, model version, output and approval is logged and exportable.
Configurable per matter type, with legal-hold support and verified deletion on termination.
BAAs available for US medical-record workflows; PHIPA and PIPEDA aligned handling in Canada.
Pinned model versions per module, change logs, and evaluation before any model swap.
Daily backups, point-in-time recovery, documented RTO/RPO, annual penetration testing.
What we are not
Lexcadence Legal Automation is a software provider to licensed legal professionals. It is not a law firm, it does not provide legal advice, and no output is a substitute for the judgement of a lawyer admitted in the relevant jurisdiction. Unauthorised practice of law rules differ by state and province; the firm using the software remains responsible for compliance.
Want the security questionnaire and DPA before you talk to sales?
Request the pack