Tenant and matter isolation
Each organization's users, matters, documents, conversations, workflows, and outputs are designed to remain separated.
Security and Privacy
Parassist is built around private deployment options, matter-level access controls, auditability, source-grounded outputs, and administrator-controlled model policy.
Matter files may include privileged communications, attorney work product, settlement materials, medical records, financial records, trade secrets, client proprietary information, and other sensitive documents.
Each organization's users, matters, documents, conversations, workflows, and outputs are designed to remain separated.
Administrators define which model providers are allowed, which data classifications can use each provider, and whether public AI services are permitted.
Document-based answers should connect back to source materials and flag when selected documents do not support an answer.
Audit logs are intended to show who accessed matters, uploaded or downloaded documents, changed settings, ran AI workflows, generated exports, or modified model policy.
Original documents and generated outputs are stored in private object storage with expiring signed links or controlled download routes.
For stronger isolation, Parassist can be planned for local database, local storage, local model inference, local embeddings, and no required outbound telemetry.
Parassist should be deployed with clear documentation for architecture, data flow, model-provider policy, audit events, retention settings, and backup procedures. Parassist should not be represented as certified under any security or compliance program unless that certification has actually been completed for the applicable deployment.
Share your deployment constraints, model-provider restrictions, and document sensitivity requirements. We will walk through how Parassist can be configured for your legal team.