Trust Center

Transparency for teams evaluating Clairist

Clairist is in beta. This Trust Center is a single entry point for security, privacy, legal drafts, and trust analytics documentation. It is designed to support procurement conversations—not to replace your counsel, vendor risk questionnaires, or regulated assurance programs.

Beta and assurance status

  • SOC 2 Type II is not yet completed for Clairist. We do not represent that an independent SOC 2 audit has been finished or that a report is available.
  • We do not claim automatic compliance with any law or regulation, legal advice, or third-party security certification unless explicitly stated elsewhere with evidence you can validate.
  • A Data Processing Agreement (DPA) is available on request for qualified customers; start from the procurement request form or email procurement@clairist.com. Execution and workflow may depend on your plan and readiness of our legal templates.
  • Prefer a structured intake? Use the procurement and trust request form (beta, manually reviewed).

Current legal document versions

These are the versions Clairist records when an account is created. The full text lives on the linked pages; the version identifier matches what we persist in your account for operational continuity.

Public trust artifacts and verification

When you publish a public Trust Record, Clairist can expose structured artifacts and verification material so reviewers can confirm that bundles are internally consistent (for example, hashes and signatures where enabled). Verification answers cryptographic and format questions about the artifact Clairist serves—it does not, by itself, prove that every narrative disclosure is factually complete or that your use of AI complies with law.

Technical entry points used in the product and APIs include public verification via POST /api/public/trust/verify (for submitted bundles) and team-scoped review bundles where the product exposes them. Authenticated workspace users may also use internal verification APIs documented for operators. Availability and rate limits apply; see error responses in the application when limits are hit.

Subprocessors and infrastructure

Clairist runs on modern cloud infrastructure. See the dedicated Subprocessors page for provider names, purposes, data categories at a summary level, and links—not a substitute for your vendor risk process.

Your organization should review each provider's terms, status page, and data processing documentation. The authoritative list for your agreement may appear in an order form, DPA, or updated subprocessor notice we provide when you become a paying customer.

Procurement, DPA, questionnaires, and enterprise inquiries

For procurement routing, DPA requests, vendor security questionnaires, and structured enterprise evaluations, start with the procurement request form (preferred intake). You may also email procurement@clairist.com. Security questionnaires and security reviews: security@clairist.com. Privacy requests: privacy@clairist.com. Context on processor posture and DPA availability is on the DPA overview.

Assurance and maturity. SOC 2 Type II is not yet completed for Clairist. Security review workflows, artifact bundles, and template DPAs are evolving during beta. We can share documentation on request where appropriate, but we do not represent completed third-party audits, automatic compliance, or legal outcomes.

General product questions: hello@clairist.com or the contact page. Please mark procurement or security in the subject line when email is not the dedicated address above.

Nothing in the Trust Center is legal, compliance, or security advice. Draft policies here should be reviewed by your counsel before you rely on them for regulated decisions.

Back to overview