Evidence bundle, not scattered files
Package the relevant event into a structured record instead of relying on fragmented documents, screenshots and memory.
Cryptographic evidence for legal workflows
Create a stronger record for what was deposited, delivered, accessed or disputed.
LegalProof turns sensitive digital events into sealed proof bundles backed by VeriSeal Core: canonical JSON, certified PDF, hash evidence, Merkle root, and a public verification surface that can be opened outside the internal workflow.
Proof of content
Proof of deposit
Proof of access
Proof of notification
Public verify page
Canonical PDF + JSON
Why LegalProof exists
LegalProof is for moments where a legal or sensitive workflow should not end as a screenshot, a loose attachment or an email thread. It is designed to turn a concrete event into a coherent proof bundle that can be preserved, shared and reviewed later.
Public verification outside the workflow
A proof is not trapped inside the application. A third party can open a readable verification page and inspect the associated artifacts.
Built for legal and compliance pressure
Use it when content, timing, access, delivery or document state may be challenged later and the record needs to remain intelligible.
Typical LegalProof use cases
The legal-facing positioning is event-centric. The product is about proving what happened around a sensitive communication or document state, not only freezing a file.
Proof of content
Capture a precise version of a notice, attachment, submission or statement and seal the resulting record.
Proof of deposit or handover
Show that a file or bundle was deposited, handed over or released at a specific moment under a controlled workflow.
Proof of access
Record a controlled access event when the workflow includes a view or open step, with technical evidence attached to the bundle.
Proof of notification
Preserve the evidence surrounding a delivery or notice workflow and expose a public proof page for later review.
Dispute-ready matter record
Keep a stronger timeline for contentious files, escalations, complaints, payment disputes or contractual friction.
Internal legal and compliance workflows
Support in-house legal, compliance or governance teams that need a disciplined proof layer without rebuilding their full stack.
How LegalProof works
The flow stays narrow on purpose: ingest the event, seal the bundle, expose a readable trust surface, and keep independent verification possible later.
1
Capture or ingest the event
Collect the content, file, message state, delivery event, access event or matter metadata that actually needs to be preserved.
2
Seal the bundle
VeriSeal Core canonicalises the record, generates a cryptographic bundle, derives the hash and Merkle root, and prepares the proof artifacts.
3
Share or retain the result
Keep the bundle private, circulate the PDF internally, or expose a public verification page when an external counterparty must review it.
4
Verify independently
A verifier can inspect the readable proof surface and retrieve the underlying PDF, JSON and verification artifacts without depending on your internal tool access.
Need legal-facing proof, not another inbox folder?
Start with a focused pilot around one notification flow, one dispute-heavy matter type, or one controlled document-access scenario.
What a verifier should be able to inspect
LegalProof inherits the public-verify posture already visible in CargoProof: a readable page, downloadable artifacts, and a trust layer that sits outside the internal workflow.
Proof summary
Proof type, status, issued-at time, matter context and the key facts required to understand the bundle at a glance.
Verification artifacts
Signed PDF, canonical JSON, detached signature, public signing key and timestamp or anchor material when exposed by the deployment.
Hash and Merkle root
A stable cryptographic fingerprint that ties the bundle to the underlying ledger logic and allows later reference.
Independent review surface
A link that can be shared with counsel, counterparties, auditors or compliance teams without granting them application access.
FAQ preview
The commercial positioning should stay precise and careful from day one.
Does LegalProof replace legal advice or formal procedural service?
No. LegalProof is a cryptographic proof layer. It can strengthen evidence handling and review, but it does not replace legal advice, court procedure, bailiff service or jurisdiction-specific formalities.
Does LegalProof prove that a person actually read a document?
Only when the workflow contains a real access event that is itself captured and sealed. Otherwise the proof may show delivery, availability or a preserved state, but not actual comprehension or acceptance.
Is LegalProof eIDAS qualified by default?
No. The default product positioning should remain careful. Qualified trust effects depend on the exact service used, the provider status and whether a listed qualified trust service is involved.
Can a third party inspect the proof without an account?
That is the intended direction. The public verification page is designed to be readable outside the internal workflow, with downloadable artifacts for independent review.
LegalProof should be marketed as a stronger evidentiary layer, not as a guaranteed court outcome. Identity, legal admissibility, service validity and regulatory effect still depend on jurisdiction, workflow design, and whether qualified trust services are actually used.