Security
Built against the rules you already answer to
Data handling follows the regulation of the jurisdiction a matter sits in, not a single head-office standard applied everywhere.
Compliance isn’t an afterthought
One compliance architecture, built to hold a different regime for each of the 54 jurisdictions Lergal is designed to cover. These are the regimes it runs on today.
POPI Act
South Africa
B-BBEE
South Africa
ISO 27001
Information security posture
NDPR
Nigeria
Kenya DPA
Kenya
LPC
Legal practice regulation, by jurisdiction
Confidentiality doesn’t change because a tool is involved
Client data and confidentiality obligations don’t change when AI is doing the work. Before any document reaches Contract Intelligence, it passes through a classification step, and the two highest-risk classifications require an explicit, logged reason before proceeding.
- Confidentiality classification required before upload
- Client-confidential and privileged material logged, not silently allowed
- Firm-level audit trail for governance review
A person always signs off before you rely on it
AI-generated output, including well-cited output, can be confidently wrong. Every research answer, translation, and contract review carries a required verification step: a person has to confirm they checked it before it counts as reviewed.
- Sentence-level citations you can open and check
- Verification recorded with who reviewed it, and when
- No output marked reviewed without that step
