Built for the sensitivity of your matters.

Data handling

Pandexis ingests your documents into a per-tenant logical boundary and never mixes them with other clients' data for model training, evaluation, or product telemetry. Raw documents remain in customer-controlled storage; derivative extractions and embeddings are held only as long as your retention policy requires.

Encryption

All data is encrypted at rest (AES-256, cloud-provider-managed keys) and in transit (TLS 1.3). Keys are rotated on a documented cadence and revoked on tenant offboarding.

Access controls

Role-based access with single sign-on. Every operator action against tenant data is logged to an immutable audit stream.

Tenant isolation

Data is isolated at the database layer using row-level security policies bound to a tenant identifier set per-request. The platform does not rely on application-level filtering for isolation; the database enforces it.

Audit logging

Every LLM call, every consensus decision, every pipeline state transition emits a structured audit entry. You can export this log for any matter at any time.

Privilege protection

Privilege markers are applied continuously during review, not as a separate pass. Privileged passages are excluded from cross-document synthesis by default.

Certifications & compliance

Pandexis does not hold a third-party security certification or attestation today. We are not SOC 2, ISO 27001, or HIPAA certified, and we will not tell you otherwise. The controls described on this page are the ones we actually run.

We are building toward a SOC 2 Type II audit, and we will say so here — with the report date — only once it has been issued. In the meantime we complete security questionnaires and will walk your security team through our controls directly.

Data residency at v1 is US jurisdiction; EU / UK residency is on the roadmap and available by request for qualifying engagements.