A certificate, checked
What anybody sees at signsealer.com/verify with a code from a completed agreement: whether the certificate still matches the record behind it, and everything that record says. This is the real page.
Evidence
A trust page that only lists what a product can do is a marketing page. The useful half is the constraints.
What anybody sees at signsealer.com/verify with a code from a completed agreement: whether the certificate still matches the record behind it, and everything that record says. This is the real page.
Created, sent, delivered, viewed, consented, signed, completed — each with the time, the address and the browser, and the hash of the text as it stood at that moment.
Written before the signature is accepted. The engine refuses a signature from a signer who has not consented; it is not a field on the signature row.
Stored on the document, not a reference to a template. Retention means reproducing what was agreed, and the template can change — that is the whole point of versioning it.
Each audit row's hash covers its own content and the hash before it, per customer. Removing or altering one breaks every row after it.
We build the evidence. Whether a particular agreement is enforceable where you are — and whether your waiver language holds in your state — is a question for your own counsel.
An email link proves possession of an inbox. Where you need more than that, there is a passcode and an ID check — and the certificate says which was used rather than implying the strongest.