Security and trust
Records that can be trusted because they cannot be quietly changed
Compliance evidence is only worth something if nobody can alter it afterwards. These are the controls built into the product, described as they work today.
Every workspace is walled off by the database
Tenant isolation is enforced inside the database itself with row-level security, not only in application code. A query made for one workspace cannot return another workspace's rows.
Maker cannot be checker
The person who prepares an item cannot approve it, and the person who raises an exception cannot decide it. The system refuses; it is not a policy to remember.
Evidence is immutable and versioned
Files are stored by their content and never overwritten. A correction is a new version beside the old. Files open only through short-lived, signed links.
A tamper-evident audit trail
Every change is written to an append-only history in the same step as the change, each entry chained to the one before. A verify action checks the chain, and the trail can be downloaded.
AI is advisory, never in charge
Where AI suggests something, the suggestion is stored separately and labelled. It is never applied automatically; a person decides, and that decision is recorded.
Public sharing is opt-in and revocable
A workspace's own topics are private unless shared by link, and a shared link can be switched off. Shared links are kept out of search engines and are never listed on this website.
Sign-in happens in the app only
This website has no sign-in form and collects no passwords. The Sign in button takes you to the CLEX Legal application, the one place credentials are typed.
What we do not claim
Plain about the limits
This page describes controls in the product. It is not a certification or an audit report, and we do not display badges we have not earned. If you need a security questionnaire answered, ask your CLEX Legal contact.
See your compliance in one calm place
Sign in to your workspace, or read what we publish for free.