Clear answers for legal, compliance and trust questions.
A careful FAQ is part of the product posture. It should clarify what LegalProof does well, where the boundaries are, and why the architecture remains useful.
LegalProof FAQ
These questions can be used directly on the MVP site.
What is LegalProof?
LegalProof is a legal-facing proof layer built on top of VeriSeal Core. It packages sensitive events into a sealed record with a public verification surface and downloadable artifacts.
Who is LegalProof for?
Law firms, in-house legal teams, compliance functions, regulated businesses and selected professionals or individuals dealing with sensitive digital records.
What does LegalProof prove?
It is designed to preserve a stronger technical record of content, document state, deposit, access or notification context, depending on the exact workflow used.
Does it replace a qualified signature or a qualified delivery service?
No. Those are separate trust-service categories with their own legal and provider requirements. LegalProof should not be marketed as a substitute by default.
Can a verifier inspect a proof without an account?
That is the target posture for the public verification surface. The page should be readable outside the internal workflow, with the proof artifacts exposed according to deployment policy.
What artifacts may be available?
Typical artifacts include a signed PDF, canonical JSON, detached signature, public signing key and timestamp or anchor material where available.
Is LegalProof legal advice?
No. It is a product layer, not legal counsel. Admissibility and procedural effect depend on the relevant law and the specific facts.
Can LegalProof be connected to qualified trust services later?
Yes. The commercial wording should leave room for optional qualified timestamps, qualified seals or other trust-service integrations where appropriate.
Recommended policy: when in doubt, position LegalProof as an evidentiary and verification layer, not as a universal legal shortcut.