Trust Center

What Claract reads. What it never decides.

Claract identifies likely issues and prepares review guidance. It does not provide legal advice, certify compliance, send notices, issue summons, or replace legal counsel.

Boundary

The product boundary

What Claract reads

  • Draft notice text
  • Resident lease PDFs
  • Active fee schedule CSV exports
  • Property jurisdiction
  • Reviewer decisions and packet actions

What Claract never decides

  • Whether a notice is legally compliant
  • Whether a notice should be sent
  • How to interpret cure-period law in a specific dispute
  • Whether to issue a legal summons
  • Whether to approve final resident delivery

Attestations

Current security attestation

SOC 2 Type II achieved 18 February 2025; scope covers Customer Data & Compliance Evidence (Stage 3). ISO 27001 pending; submission Q3 2026. Claract does not claim HIPAA or PCI compliance. The controls described on this page are the practices Claract operates today — TLS 1.3 in transit, AES-256 at rest, and Role-based access control (RBAC).

Operating principles

How human review fits the product

  1. 01

    Human sign-off is required

    Claract can extract lease dates, fee amounts, and jurisdiction identifiers. It surfaces findings and prepares a Compliance Packet. A human reviewer must review and sign off before any workflow continues — no notice leaves without approval.

  2. 02

    No legal advice

    Nothing Claract produces constitutes legal advice. Claract identifies likely issues and prepares review guidance. Legal interpretation of cure periods, compliance certification, and issuance of legal summons remain human-required decisions outside Claract's scope.

  3. 03

    Claract does not send notices

    The platform does not deliver notices to residents, initiate legal action, or approve final resident delivery. Every send action is an explicit, human-initiated step that occurs outside the Claract review workflow.