Skip to content

Trust & Privacy

Your client data
stays your client data.

Review how Kayse uses data, manages access, and divides responsibilities with your firm.

Kayse trust and privacy overview
Kayse trust and privacy overview

Your data is never training data.

Kayse uses AI strictly for inference inside your workflows.

It does not use customer-specific data, including message bodies, chat and email content, call transcripts and recordings, case and matter data, attorney-client communications, or related metadata, to train, retrain, or fine-tune any AI model.

The models Kayse uses are pre-trained by vendors and used for inference only.

Protection measures and account access.

Review the measures that apply to your service and subscription level.

Protection measures

Depending on the Service and subscription level, measures may include encryption in transit, encryption at rest, access controls, account-level access management, logging, monitoring, vendor-management practices, and documented incident-response procedures. No provider can guarantee absolute security, and Kayse does not claim to.

Account structure

Accounts may be organized into organizations and sub-organizations with role-based access controls designed to limit access to authorized users of that account.

Sub-processors

Sub-processors that help operate the Services are bound to written confidentiality and security obligations appropriate to what they do.

Read the sub-processor policy

Compliance is a shared model.

Your firm owns its compliance program.

Kayse is built with configurable guardrails: allowed calling hours, recording consent in the states that require it, AI disclosure on calls, opt-in capture for SMS text and Voice AI, and a dedicated compliance log. We keep them updated as the landscape evolves. Your firm owns its compliance program: the consent you collect, the data you load, and your opt-out practices determine outcomes. Kayse is not marketed as an absolute compliance guarantee.

Give your diligence team the current documents.

Request the data-flow, sub-processor, retention, and incident-response documentation relevant to your review.

Request security documentation →

Kayse makes no guarantee of any regulatory outcome, and no provider can guarantee absolute security. See the Privacy Policy and Terms of Use for the controlling language.