Skip to main content
Government agencies can evaluate Truthlocks for signed records, document verification and approval evidence. Procurement acceptance must use the actual deployment, current test evidence and written responsibilities. This page is not a claim of sovereign accreditation, government certification or an unconditional service-level guarantee.

Evaluate the deployment

The current hosted platform uses Google Cloud. Confirm the agreed data region, subprocessors, access boundaries, retention and exit arrangements before production use. A selectable region or a key-management feature does not establish sovereign hosting or a dedicated government deployment by itself. Workspace and environment controls protect supported operations. Request the applicable isolation test results and known limitations. Independently assess whether the available identity-review and approval workflows meet the agency’s requirements; do not assume mandatory multi-person approval for every operation.

Onboard and validate

  1. Create the organization and complete the requested organization and identity evidence.
  2. Use sandbox keys and synthetic records to test the integration.
  3. Submit the issuer application and required evidence for staff review. Creating an issuer is not proof of a reviewed identity or production approval.
  4. Select an algorithm supported by the chosen signing provider and test signature verification and tamper rejection.
  5. Complete production onboarding and any separately required billing-country review before the relevant production or paid operation.
  6. Review roles, MFA/SSO, audit exports, retention and incident contacts before inviting operational users.
Use the issuer application guide, security governance page and SIEM delivery guide. Validate invitation delivery and access with the intended users; do not infer successful onboarding from tenant creation or a sales status change.

Reliability and response

Automated database backups and point-in-time recovery are configured. Full application recovery, availability commitments, support coverage and incident response times must be assessed and agreed explicitly. A single-zone database does not provide multi-zone database failover. This page does not promise a staffed 24/7 response team, multi-region failover or automatic service credits. Agree the required recovery objectives, escalation contacts, evidence retention and exit procedures in the contract. Record acceptance decisions and unresolved exceptions; a successful sandbox pilot does not waive them.