Security at Legalnaut A Markdown version of this page is available at https://legalnaut.com/security.md for AI and LLM tools. Nothing goes in a filing unverified. ====================================== This page is written for the person at your firm who has to sign off on the tool. It says what is true today, and names what is out of scope. SOC 2 TYPE II CERTIFIED INFRASTRUCTURE One case file per workspace --------------------------- Each workspace has its own content database and its own file-storage prefix. A query issued in one workspace has no path to another: the isolation is at the database and storage level, not a filter applied to a shared table. A plan with several cases holds several of them, one per client file, and the same boundary sits between each pair. A client invited as a viewer sees one workspace and nothing beyond it. Evidence cannot be rewritten ---------------------------- A document's checksum, its stored path, its extracted text and the quoted text of any claim drawn from it are fixed when the document enters the file. The application refuses to overwrite them. Descriptions generated by AI, such as summaries and explanations, are separate columns and can be regenerated without touching the evidence underneath. Every file is hashed with sha256 on arrival. That fingerprint is what proves the file has not changed since, and it is also what stops the same document being imported twice under two names. No public URLs to case material ------------------------------- Documents are streamed through the application after an authorisation check. There is no signed public link, no bucket set to public, and no URL that keeps working once someone leaves the workspace. Roles, and the one that can delete ---------------------------------- Five roles: owner, admin, lawyer, specialist, viewer. Deleting shared material is restricted to owner and admin. A viewer can read and export, and can change nothing at all. Every consequential action is written to an append-only audit log that the people it records cannot edit. AI, and where it stops ---------------------- Analysis runs on commercial language models under agreements that prohibit training on customer content. Anything a model drafts is labelled a draft and marked review-required. Legalnaut does not give legal advice, does not file anything, and does not decide what a document means. Every generated answer carries the documents it was built from, and every draft and chat answer passes a citation check before it is shown: the cited document exists and the reader may see it, the cited page exists, a quotation appears in a document cited in the same paragraph, a case number is one the file knows. What fails the check is reported, never quietly repaired. That is the mechanism that makes a wrong answer visible instead of persuasive. A contradiction the model finds is stored as a suggestion. A lawyer confirms or dismisses it, the verdict carries their name and the time, a dismissed pair never returns, and only a confirmed pair reaches a draft, a report or a chat answer as a fact. The assistant reaches the records only through read-only tools. A document the team has hidden, or one outside a user's permissions, is absent from everything those tools return, the database query included. The two things it can write are an entry in a matter and a note, and a note it writes is marked as the assistant's. Sub-processors -------------- PROCESSOR PURPOSE Language model providers Document analysis, summaries, chat answers Cloud hosting and object storage Application hosting and case-file storage Amazon Textract OCR for scanned documents, when local extraction fails Stripe Subscription billing and invoices Zoho Mail The forwarding address that imports correspondence The current named list, with jurisdictions, is in the [data processing agreement](https://legalnaut.com/dpa). Retention --------- No plan puts a time limit on your case file. Nothing deletes case material on a schedule, because these are case records and an automatic sweep is the wrong default for them. If a subscription lapses, the workspace becomes read-only and stays that way; clearing it is a deliberate action, never a cron job. Reporting something ------------------- If you believe an account has been compromised or you have found a vulnerability, write to . Legalnaut is operated by A2Z WEB PTE. LTD., registered in Singapore under 202614429R. SCREENSHOT ![]()