Evidence
What is the Evidence Package, and what is the difference between Certified PDF and Evidence PDF?
The Evidence Package is your legal proof bundle. It combines document integrity, signature metadata, and audit history so you can prove what was signed, by whom, when, and under which verification method.
The Evidence Package is your legal proof bundle. It combines document integrity, signature metadata, and audit history so you can prove what was signed, by whom, when, and under which verification method.
EVIDENCE OUTPUTS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Agreement PDF (Certified)
+
Evidence Certificate PDF
+
Evidence Package JSON
+
ZIP (all files + README)What each file is for
Certified PDF (agreement-certified.pdf / format=agreement-pdf)
Includes: The rendered agreement content from an immutable revision snapshot, plus revision/hash verification metadata.
Best for: Showing the exact contractual text that was frozen for signing, with verifiable integrity metadata.
Availability: Available only in eligible statuses (ready-to-sign and later signing-complete states).
Evidence PDF (evidence-certificate.pdf / format=pdf)
Includes: Signature identities, signed-at timestamps, verification method, masked IP data, document hash, audit events, and cancellation evidence (if applicable).
Best for: Disputes, legal review, and operational audit where signer actions and verification details matter.
Evidence JSON (evidence-package.json / format=json)
Includes: Machine-readable full evidence dataset, including revision info, signatures, and audit logs.
Best for: Compliance tooling, internal analytics, integrations, and long-term structured archival.
ZIP bundle (format=zip)
Includes: Evidence PDF, Certified PDF when eligible, JSON evidence payload, and README summary.
Best for: One-click legal archive where everything is packaged together.
Why this matters legally
- Tamper evidence: SHA-256 hash links evidence to exact content; altered content changes hash.
- Identity context: records who signed and what verification path was used.
- Timeline proof: audit trail and signature timestamps create a chronological event chain.
- Portability: ZIP + JSON let legal, compliance, and technical teams validate evidence independently.
Related guides