Security & trust

Review the boundary. Understand the assurance.

Security review starts with the exact workflow, data flow and operating responsibilities. Confirm what the software implements, what has been tested, and what your reviewer still needs.

Assurance status

An early-stage software supplier, with explicit limits.

No completed certifications asserted

This site does not claim completed SOC 2, ISO 27001 or FedRAMP certification. It does not claim customer-production validation, a universal production SLA or a zero-retention guarantee.

Source review is one evidence class

The request path and relevant test assertions were inspected on October 21, 2026. The tests use in-memory storage and fake providers; they were not rerun for this website update. Deployed provider behavior and customer acceptance remain separate verification steps.

Inspect the evidence and its scope
Data handling

Establish the plan for your evaluation.

Data and model paths

Identify what enters Clariva, where transformation occurs, which model or other subprocessors can receive it, and what leaves the agreed boundary. No claim covers every data class or bypass.

Storage, access and deletion

Agree evidence access, retention, deletion, tenant and identity responsibilities, key custody and incident contacts for the actual environment. Do not assume a default retention commitment from this page.

Deployment and operation

Confirm hosting, location, availability, failure handling and support responsibilities before access or testing. Customer VPC, on-premises and topology parity are not represented as generally available modes.

For the security reviewer

Ask for evidence that answers your actual assertion.

  • Architecture, intended ingress, retries, fallback and excluded paths.
  • Exact software revision, policy and environment configuration.
  • Allowed, transformed, denied and held cases relevant to the requirement.
  • Independent execution observations where needed, plus task-quality results.
  • Known limitations, defects and a precise reviewer decision.

A request record shows recorded information. It does not prove complete coverage or provider nonexecution by itself.

Use the reviewer checklist
Questions and terms

Resolve supplier requirements early.

Can you meet our procurement requirements?

Review the actual assurance, deployment and data terms before a paid proposal. If a mandatory requirement is unavailable, hold the affected scope rather than assume it will be delivered.

Do you need confidential details in the website form?

No. Use a high-level description only. Do not send production customer data, credentials or proprietary prompts through a website inquiry.

How do we raise a security question?

Use the general contact form or email admin@clarivaprivacy.com. Describe the issue at a high level first; agree a suitable channel before sharing confidential material.

Contact Clariva about security or terms