Feature 03 / 06 · Audit trail

Every state change is hashed, sequenced, and timestamped. The trail is tamper-evident from upload to seal — and exportable as evidence.

Evidence certificate
Envelope env_01h9k…
chain-head: b601…72d4
events: 6
sealed: 2025-04-12 14:04Z
✓ Verified against public log
How it works

Four moves, one tidy trail.

Capture every event.

Thirty-four distinct event types, from envelope-created to signer-device-rotated. Every one stored with UTC timestamp, actor, method, and network metadata.

Event stream
14:01:47envelope.createdmarcus@northwind.co
14:02:03envelope.sentsystem
14:02:09signer.viewedelena@atwater.law
14:03:44consent.recordedelena@atwater.law
14:03:51signature.capturedelena@atwater.law
14:04:02envelope.sealedsystem

Hash into the chain.

Each event’s SHA-256 is folded into the previous one. The chain head is published daily to an append-only evidence log — you can verify integrity without trusting us.

Hash chain
019f8c…b27d↓ sha256(prev + evt)
02a412…01ff↓ sha256(prev + evt)
0378e3…c9a1↓ sha256(prev + evt)
04b601…72d4

Bind to the document.

When the envelope seals, the chain head is embedded into the signed PDF’s XMP metadata and into a companion Evidence Certificate.

Certificate excerpt
{
  "envelopeId": "env_01h9k…",
  "chainHead": "b601…72d4",
  "publishedAt": "2025-04-12T14:04:10Z",
  "events": 6,
  "sealAlg": "ECDSA-P256"
}

Export on demand.

Download the Evidence Certificate as a PDF, the raw event log as JSON, or integrate via API. All three are identical in substance and independently verifiable.

Export formats
  • Evidence Certificatepdf
  • Event logjson
  • GET /v1/envelopes/:id/evidenceapi
Proof

Numbers the team actually checks.

34
Event types

From creation to sealed delivery

SHA-256
Hash family

FIPS 140-2 approved

0
Plaintext leaks

Event metadata tenant-scoped

24h
Chain head publish

Append-only third-party log

Compliance

Tamper-evident by construction.

Every audit trail is cryptographically chained: if any event were altered, every subsequent hash would diverge and the embedded chain head in the PDF would no longer verify against our public log.

The Evidence Certificate satisfies FRE 901 (authenticity), FRE 902 (self-authenticating electronic records), and is commonly accepted under equivalent rules in EU, UK, and APAC jurisdictions.

Questions

Before you write it in.

  • Yes. legesis Evidence Certificates are designed to satisfy FRE 901/902 in the US and equivalent rules in the EU, UK, and APAC jurisdictions we operate in. We've assisted in over three hundred disputes — zero have been thrown out on authenticity grounds.
Start today

Five free envelopes, no credit card. You can upgrade, downgrade, or walk away — we designed it that way.

No card required · 5 free envelopes · Cancel anytime.