Security, described by what the product does

LegalBook is shared by many firms, so separating them is the first requirement of every change. Every firm-owned record carries its firm, every query runs inside the firm of the person asking, and a record of another firm answers “not found”, never “forbidden”, so the product does not confirm it exists.

An automated gate scans every registered route and fails the test run if one lacks an authorization check, and isolation tests prove that one firm cannot read, list, search, export or receive events about another firm’s records.

People sign in through LegalBook’s own sign-in service; the application itself stores no passwords.

There are 29 roles, across firm staff, the shared workforce, clients, outside parties and LegalBook’s own platform staff. Receptionists see what a live interaction needs, not whole records. A matter can be restricted to attorneys, with access granted person by person, and a worker holds a work item under a lease that sets what they may do with it.

No LegalBook platform role holds a legal-judgment permission: deciding a conflict, accepting an intake, verifying a deadline or approving a filing needs an attorney of the firm.

Creating, changing, downloading, sharing, approving and transferring firm data each write an audit record, as do refused attempts on sensitive records. The log is append-only and hash-chained per firm; there is no way to update or delete an entry, and the chain is verified every day.

Every upload is hashed, scanned for malware and content-checked; a file that fails is quarantined. Viewing, downloading and printing go through signed, time-bound links minted after a permission check, a print token works once, and every mint and download is audited. Document versions are never changed or deleted by the application.

Phone, payment, email and integration credentials are encrypted with AES-256-GCM before they are stored, and the application never returns them once saved. No credential is kept in a log line, a job or a URL.

If LegalBook support needs to see what a person in your firm sees, it asks: impersonation requires your firm’s consent and is audited, and an impersonated session can never act as your attorney. Emergency break-glass access is time-bound, approved and reviewed afterwards. Access reviews list who can reach your firm.

Retention schedules decide when records are disposed of, and a legal hold stops disposal. Firms can export a client file, a person file or the whole firm. A deletion request is decided by compliance, not by whoever asked, and permanent legal records such as decisions and filings are kept.

AI suggestions are not available yet. When they are, every suggestion goes to a person to accept, edit or reject; input is redacted before it is sent; requests for legal advice, eligibility decisions, conflict waivers and deadline dismissal are refused; and each feature is switched on by the firm.

LegalBook has not completed a third-party certification or audit. Certification of the live vendor connections, production disaster-recovery drills and penetration testing are still to come. When any of them is done, this page will say so, with the date.