Claridy runs on top of your stack, not beside it. Your books stay in your own systems, we read read-only where we can, and every action is traceable.
Every action of every workflow records what was read, what was decided, at what confidence score, and what was written back. That log is searchable and exportable, and it is meant to be shown to an auditor.
That is not an extra feature but a consequence of how it is built: deterministic workflows can always explain why they did something. A model cannot.
There is no language model in the execution path. AI writes the workflow and helps with interpretation at the edges, but execution is deterministic code. A workflow that worked yesterday works the same today. There is no model update that quietly changes your booking behaviour.
Claridy was assessed externally by TAC Security in February 2026 against CASA Tier 2, the assessment built on the OWASP Application Security Verification Standard. All 108 requirements were reviewed: access control, cryptography, session management, data protection and injection prevention.
A SOC 2 programme is under way. It goes here once the report exists.
Data processing agreement · Sub-processor overview · Security overview · CASA Tier 2 audit report on request