What Klariqo does
1
Signs compliance records
Klariqo signs a record for each recorded call. The record is signed with a JWS signature using RS256, and the signature carries Klariqo’s signing certificate.
2
Makes changes detectable
A signed record is tamper-evident. If the signed vCon is changed after signing, verification fails.
3
Fingerprints the recording
A SHA-512 content hash fingerprints the recording inside the record. This helps tie the record to the recording content.
4
Secures dialer connections
Recording connections use HTTPS by default. Plain HTTP is refused unless your account owner accepts the risk for that address. Voice AI connections use SIP digest authentication, and audio to Klariqo travels over an encrypted WebSocket.
5
Stores recordings encrypted
Recordings are kept in encrypted storage.
6
Applies a trusted timestamp
Klariqo obtains an RFC 3161 trusted timestamp from DigiCert over the record’s fingerprint, proving the record existed at a point in time. DigiCert does not receive the transcript, audio, phone numbers, or QA content.
Who sees your call data
Your call audio reaches Klariqo and its transcription vendors. Klariqo is not HIPAA or PCI compliant. See who handles your call data.What you own
You are responsible for the systems and decisions you control.Shared responsibility in practice
Klariqo evidence layer
Signed records, content hashes, QA results, trusted timestamps, and verification.
Your operating layer
Scripts, consent, dialer administration, access control, retention, and legal review.