Encryption and infrastructure.
- AES-256 encryption at rest, TLS 1.3 in transit
- Customer-managed keys via Azure Key Vault
- US-based Azure infrastructure
- Annual penetration testing
Built for firms that handle privileged materials and protected health information.
Four control surfaces — data protection, privilege isolation, AI data handling, and access & audit — each enforced at the platform layer.
Every portal operates in its own walled environment. No case data, work product, or analytical output crosses between sides.
Each portal runs in a separate data environment. Plaintiff, defense, and IME workspaces never share storage, compute, or access credentials.
Automated screening prevents the same matter from appearing in opposing portals. Conflicts are flagged before case data enters the system.
Role-based permissions ensure each user sees only the cases, documents, and outputs assigned to their portal and practice.
Every query, document access, and generated output is logged with timestamps, user identity, and portal origin for full traceability.
The short version of the security posture, suited for your IT team's intake form.
A reviewer-ready summary of the platform's technical security architecture, suitable for paste into a vendor security questionnaire.
Microsoft Azure US regions.
Customer-managed encryption keys through Azure Key Vault. AES-256 at rest, TLS 1.3 in transit.
Azure AD integration with SAML 2.0 SSO. OAuth 2.0 API authentication with scoped tokens.
Case-level data isolation enforced at the database query layer. Vector search scoped to single case partitions.
Immutable audit trail with cryptographic integrity, 7-year retention.
Zero-retention AI API configuration contractually enforced.
Annual penetration testing with remediation tracking.
Request the full technical security package for your IT team's vendor review.