Trust

What you can rely on, and what we do not claim yet.

Tessavra is in development. This page keeps three things apart: what the code and local tests show, what is still being built, and what we do not claim.

  • Customer data is separated per organisation by row-level security, tested on a local stack.
  • Several controls, including single sign-on and retention, are still in development.
  • No certification and no independent penetration test.

Verified in the code and local tests.

Read these with the qualifier

Everything in the list above was checked in code and on a local test stack. No hosted environment has verified any of it yet.

In development.

Responsible AI, in development

A person stays in charge.

A finding can carry a review state that a person sets: not reviewed, in progress or reviewed. Where a finding cites audio, the citation carries a confidence marker such as Exact or Unverified. Live guidance in Cortex comes from rules your team writes or passages from your own documents, and no model writes it. Citation accuracy has not yet been evaluated.

  • Review states a person sets
  • Citation confidence markers
  • Guidance your team writes

What we do not claim

No SOC 2, ISO 27001, HIPAA, PCI or GDPR certification. No independent penetration test, uptime commitment or data-residency commitment. No multi-factor authentication, no SCIM directory sync and no SAML sign-in. No self-service data export or erasure, and no default retention period. No public API. No subprocessor list is published.

Documents on request.

Security questionnaires

Send yours and we will answer it for your review.

Review documentation

Ask for the controls described here in a form your team can file.

A person to talk to

Bring your legal, security and compliance teams to a demo.

Email hello@tessavra.com

Talk through the controls you need.

Request a demo and bring the questions from your security review.

Request a demo