Compliance & Evidence

Designed for evidence admissibility.

Every operational record generates a complete evidence package — independently verifiable, court-ready, and permanently anchored.

What every record includes

Every verified operational record generates a permanent, downloadable evidence package.

Evidence Package

  • SHA-256 document fingerprint
  • Immutable anchor transaction ID
  • Ed25519 signed verification JSON
  • Tamper-evident chain hash
  • Human approval attestations
  • PDF certificate with embedded QR

Audit Trail

  • Append-only event log
  • Per-event chain hash
  • Human actor records
  • Timestamp corroboration
  • Workflow state history
  • Snapshot-based replay

Independent Verification

  • No platform login required
  • Machine-readable verify API
  • QR code on every certificate
  • Stable permanent proof IDs
  • Publicly accessible trust pages
  • Cryptographic element endpoints

Compliance Standards

TLT records are designed to meet electronic evidence requirements across jurisdictions.

ESIGN Act (US)

Supported

Electronic signature provisions met via Ed25519-attested human approvals and tamper-evident records.

UETA

Supported

Uniform Electronic Transactions Act requirements satisfied through immutable anchoring and timestamping.

Electronic Commerce Act (Canada)

Supported

Electronic records and signatures in compliance with provincial and federal requirements.

Common Law Evidence Standards

Supported

Evidence packages include chain-of-custody, hash verification, and independent replayability.

ISO 27001 (Information Security)

Partial

Append-only audit trails, access controls, and cryptographic key management align with ISO 27001 controls.

SOC 2 Type II

In Progress

Operational controls, monitoring, and audit logging are aligned with SOC 2 trust service criteria.

Admissibility by design

Evidence packages are structured to address common legal challenges to electronic records.

How do I prove the document wasn't modified after verification?

The SHA-256 document fingerprint is anchored to an immutable distributed ledger. Any modification to the document after anchoring produces a different hash — immediately detectable.

How do I prove a human reviewed and approved the record?

Human approvals are recorded as cryptographic attestations at the time of signing. The approval includes actor identity, role, timestamp, and a hardware-bound signature where WebAuthn is used.

How do I prove when the record was created?

Timestamps are corroborated against multiple independent sources and anchored to a ledger position. The timestamp cannot be backdated.

Can a third party verify the record without our platform?

Yes. The evidence package contains all necessary elements for independent verification, and the public verify API is open to any caller without authentication.

Need a compliance pack?

Contact us for a full compliance documentation pack suitable for your legal or audit requirements.

Contact Us