Verification you can inspect. Safeguards you can name.

ChronoLaw is built for confidential legal matters and claim files. Encryption, hosting, data-use limits, HIPAA workflows, and privilege-related controls are described below as technical facts, not as a guarantee of privilege or compliance. ChronoLaw's analysis may use probabilistic AI. The link from a finding back to its source supports immediate verification.
Contact usSecurity whitepaper

Your documents are not training data.

ChronoLaw does not use customer documents or its outputs to train its models, and its model providers do not train on customer data.

Protected in transit, at rest, and in use.

  • Encryption in transit
  • Encryption at rest
  • US-based infrastructure
  • Authentication and MFA
  • Passkey / WebAuthn support
  • Access controls
  • Audit records
  • Data-deletion workflows

Deeper technical detail for IT and procurement is available in the security whitepaper.

Built for records containing protected health information.

Litigation and claims files often include PHI. ChronoLaw supports HIPAA-compliant workflows. A BAA is available to all users, including trial users. Do not submit PHI until a BAA is in effect.

For BAA execution and HIPAA-related vendor documentation, contact us.

Privilege-aware by design.

ChronoLaw includes a contractual and operational framework, including Supervising Attorney designation and related terms, intended to support attorney-client privilege under a Kovel-style agency structure. That framework is designed to help ChronoLaw sit inside counsel's privileged workflow rather than outside it.

It is a structure intended to support privilege, not an unconditional guarantee that privilege will apply in every matter, jurisdiction, or fact pattern. Counsel remains responsible for privilege analysis on each engagement. See the Terms for the operative Kovel-related provisions.

Read privilege terms →

Reasoning may be probabilistic. Source verification does not have to be.

ChronoLaw may use AI to identify contradictions, corroboration, or other findings. The link from a finding back to its stored source does not require the model to recreate or remember that source. That is not a claim of 100% accuracy, and it does not remove the duty to review work before relying on it.

Source linking supports professional review. It does not eliminate the professional's duty to verify work before relying on it.

Current compliance status we state publicly

  • HIPAA-compliant workflows
  • BAA available to all users, including trial users

We do not publish certification claims on this page beyond the statuses above.

Need security or procurement materials?

A BAA is available to all users, including trial users. Contact us for questionnaires and deeper technical documentation appropriate to your review.

Contact us.