Security for sensitive family-law data
Family court files can include children’s information, financial disclosure, private messages, medical details, and abuse allegations. Litigent’s security posture is built around minimizing exposure, preserving evidence integrity, and giving users control over their records.
Encryption and transport security
User sessions and file transfers should run over HTTPS/TLS. Sensitive files and derived text should be encrypted at rest using managed infrastructure controls.
Tenant and case isolation
Family-law data must be scoped to the authenticated user and case. Object-level authorization checks are required anywhere documents, events, drafts, or exports are read or written.
Audit logs
Sensitive actions — uploads, deletions, exports, sharing, AI generation, and administrator access — should be logged with timestamps and actor identity.
Retention and deletion
Users need clear controls for export and deletion. Retention periods should be documented and minimized for documents, extracted text, model prompts, and generated drafts.
No model training on case data
Litigent should use model providers and contracts that do not train on user case files, prompts, outputs, or uploaded documents. Provider retention terms must be documented.
Production-data discipline
Family-law records should not be copied into development, analytics, debugging, or support tools unless specifically authorized and protected.