Skip to main content
Truthlocks issues signed attestations and publishes transparency evidence. A valid signature establishes integrity and signing-key attribution; it does not by itself establish that a claim is true, an identity was independently verified, or a regulatory requirement was satisfied.

Cryptography and keys

Use the algorithms actually supported by the selected key provider and API. Truthlocks supports multiple signing algorithms; Ed25519 is not the only option. Managed platform signing uses Google Cloud KMS. Confirm the protection level and key-management responsibilities for the specific deployment rather than assuming every key is held in an HSM with a particular certification. Public proof identifiers and public verification keys are intentionally shareable. Private keys, API credentials and internal cloud key paths must not appear in public proof displays. Issuer-managed keys and platform-managed keys have different operational responsibilities.

Tenant and environment boundaries

Verified identities, API scopes and PostgreSQL row-level security protect workspace access. Signing resources and supported data paths distinguish sandbox from production. These controls require testing across each relevant API, job and storage path; they do not justify an absolute claim that cross-tenant access is impossible. Ask for the current isolation evidence and unresolved findings.

Audit and transparency evidence

The transparency log publishes signed checkpoints and inclusion evidence for logged records. Application audit events and request logs are separate evidence sources. SIEM delivery covers new audit events with verified environment attribution, not every historical platform action. Retention depends on the actual configured storage policy and agreement; this page does not promise seven years of complete audit history.

Privacy and recovery

Private document storage, audit retention, legal holds and erasure requests require distinct controls. An immutable signed record is not the same as a deletable uploaded document. Confirm the supported deletion/export workflow and the applicable retention policy before uploading regulated information. The current hosted database has automated backups and point-in-time recovery. A database recovery exercise is separate from application failover. Do not assume multi-region failover, a particular recovery time, or a guaranteed availability percentage from this page. Service levels and recovery commitments require a written agreement supported by the deployed architecture and exercises.

Shared responsibilities

Truthlocks operates the hosted platform and its managed keys. Customers control their users, API credentials, submitted claims and intended use. Responsibility for personal-data requests, customer-held keys, retention and incident communication must be defined in the applicable agreement. Read security governance and compliance scope. No completed SOC 2 examination, ISO/IEC 27001 certification, independent audit opinion or blanket regulatory compliance is asserted here.