Understand what Trusta's public product examples demonstrate, what they do not establish, and which checks are required before client data, contracts and operational commitments.
Demonstration calculations, sample evidence packets and illustrative scenarios are synthetic or modeled where identified. They do not prove installation, live industrial actuation, measured facility savings or independent field performance.
CONFORM explores evidence provenance and uncertainty and supports readiness reviews. It is not an accredited test laboratory, certificate issuer or regulatory verification body.
Decision support, constraints and checkpoint integrity can improve traceability; a signed record or audit trail does not itself prove that the underlying facts are true.
For a paid scoped service, report evidence, assumptions, missing inputs and limitations. Professional engineering opinions, calibration or third-party certification require separate qualified reviewers and written scope.
Do not email confidential customer records or site telemetry for preliminary quotations. Trusta will confirm identity, permitted purpose, data rights and a suitable secure intake method before accepting protected files.
Any data-processing terms, authorized subprocessors, retention and deletion commitments, service scope, acceptance criteria and payment/refund arrangements must be agreed for the actual engagement.
Readiness should be evidenced through appropriate access boundaries, source reviews, test records, backup/restore verification and incident-handling controls. Public app availability is not proof of complete recovery readiness.
Trusta does not claim SOC 2 certification, ISO certification, accredited testing, enterprise compliance approval or an external security audit without documentation applicable to the specific service.
This page describes boundaries and review principles, not certification or a security attestation. Last editorial update: November 2026.