Skip to content

Trust

How Tsaro protects a case

These are the controls built into the platform. Where something is a design target rather than a measured result, we say so.

Isolation model

Every record belongs to one institution. Database policies refuse reads and writes outside the caller's institution and assigned cases, independently of the screen.

Authority model

Permissions come from protected membership roles. The drafter of a decision cannot approve it, and sensitive steps require fresh multi-factor sign-in.

Audit model

Actions are written to append-only, hash-chained records. Corrections are linked to the original; nothing is overwritten.

Data protection

Evidence is stored privately and verified by its fingerprint. Restricted sources are excluded from search and AI assistance, and legal holds prevent deletion.

Consent that is enforced

Tsaro's terms are versioned and fingerprinted. Inside the application, changes are refused until the current terms are accepted — by the server and by the database, not only by a pop-up.

See the versioned legal documents

Vulnerability disclosure

If you believe you have found a security weakness, report it privately and give us reasonable time to fix it before disclosure. Please do not access other institutions' data or disrupt the service.

What we do not claim

Tsaro holds no third-party certification today, and no deployment has yet been independently measured. Hardware-backed signatures, data-residency evidence and immutable archival depend on each deployment.