Security and confidentiality

Your data stays in your building.

LitigatorOS is built for serious matters where confidentiality is not optional. This page explains how your data is handled, who can access it, and the safeguards that are active by default. The long-term architecture is a standalone Linux appliance — air-gapped, self-hosted, no cloud dependency.

Appliance roadmap

Built for air-gap from the ground up

The production target for LitigatorOS is a hardened Ubuntu Server 24.04 LTS appliance. Self-hosted on your hardware. Nothing phones home. No vendor access to client data by design.

Active now

Data storage and residency

Your documents, exhibits, transcripts, and case materials remain within your environment. LitigatorOS does not ingest, archive, or reuse your filings.

  • Your documents do not live on our servers
  • No long-term storage unless you explicitly connect cloud drives you control
  • No replication, pooling, or indexing of your filings outside your workspace
  • Local MinIO object storage keeps evidence files on your infrastructure
Active now

Model and processing boundaries

Verification and AI features run inside a narrow execution layer. Only the text or citation being checked is processed. Nothing is stored after the result is returned.

  • No use of your data for training any model
  • No cross-matter analysis or shared model memory
  • No persistence of input beyond the immediate task
  • AI compliance scans run locally on your data, not against external APIs
Active now

Access controls

No one at LitigatorOS can access your data by default. Internal access requires your explicit authorization.

  • No engineer or contractor access without a direct support request from you
  • Temporary access keys expire automatically
  • Role-based workspace permissions with least-privilege defaults
  • All access events logged via auditd on the appliance
Roadmap

Compliance and certifications

LitigatorOS is designed for firms with strict regulatory and confidentiality requirements. The compliance roadmap includes:

  • SOC 2 Type II readiness and external security review
  • Encryption in transit for all connections via TLS
  • Encryption at rest for all stored data via PostgreSQL and MinIO encryption layers
  • Secure boot support on compatible hardware
  • Firm-specific retention and destruction policies as the product matures
  • FedRAMP alignment documentation for federal practitioner deployments
Security contact

Questions or concerns

If you have specific security or confidentiality requirements, questions about deployment architecture, or want to discuss an NDA before a deeper conversation, reach out directly.

Email waitingroom@litigatoros.com with "Security inquiry" in the subject line. We will respond directly, not through a ticketing system.