Security and trust

Security that stays close to the work.

Documents, claim conversations, and customer evidence require more than a secure perimeter. Kiso builds access, verification, traceability, and controlled handling into the workflow itself.

Layered controls

Protect the data. Prove the action.

Our product controls are designed around a simple question: who should be able to see or do this, and what evidence should remain afterward?

01 — ACCESS

Scoped authorization

Organization, role, team, participant, and claim-level controls help restrict data and actions to the people who need them.

02 — IDENTITY

Verification where it matters

Secure links, expiring access, consent steps, optional OTP, and step-up verification support higher-risk moments.

03 — EVIDENCE

Auditable events

Delivery, access, signature, status, assignment, upload, and administrative events create an operational history.

04 — FILES

Controlled file handling

Secure uploads, short-lived original links, malware scanning, document integrity checks, and separated derivatives reduce exposure.

05 — TENANCY

Organization isolation

Tenant-aware access patterns and scoped queries keep organization data boundaries part of every request path.

06 — RETENTION

Operational controls

Features such as legal hold, revocable access, transcript export, and configurable workflow records support governed operations.

A reviewable posture

We will answer the hard questions.

Security claims should be specific and reviewable. We can walk your team through architecture, data handling, access controls, communications providers, and the product workflows in scope for your deployment.

  • Security and architecture review
  • Data-flow and subprocessors discussion
  • Product-specific access and retention walkthrough
  • Enterprise requirements captured in the deployment scope
Start a security review

No certification theater. This page describes current product controls and our security approach. It does not claim a certification or regulated-status designation that has not been expressly documented for your agreement and deployment.

Bring your security requirements to the first conversation.