FAQ
Straight answers about e‑signatures, waivers and the evidence.
The questions people ask before they sign up, answered without a sales call. If yours is not here, write to us and we will answer it and add it.
FAQ
The questions people ask before they sign up, answered without a sales call. If yours is not here, write to us and we will answer it and add it.
SignSealer is e-signature software for waivers, rental agreements and contracts, built as an evidence store first. Consent to sign electronically is recorded as its own step, a fingerprint of the exact text is written into every event, the finished PDF is sealed, and every completed agreement gets a certificate anybody holding the document can check.
No. A link by text or email opens one page on any phone. There is no account to make, no app to install, and the page loads no script from anybody else. The tablet app is for the business's own counter, not for the signer.
In the United States, under the ESIGN Act and UETA, an electronic signature is enforceable when you can show five things: intent, consent to do business electronically, association with the record, attribution to the person, and retention of an accurate copy. SignSealer records evidence for all five and seals it. This is not legal advice, and whether a particular agreement is enforceable where you are is a question for your own counsel.
Yes. The free plan needs no card, and the live demo lets you sign a short waiver as a guest and then countersign it as the business, so you see both sides and the certificate at the end.
The time, the network address, the browser, and a SHA-256 fingerprint of the exact text they were shown, on every event: sent, viewed, consented, signed, completed. Consent is recorded before the signature as a separate event, so the record can show it came first rather than assert it. The trail is append-only and hash-chained, and nobody at SignSealer can edit it.
Every completed agreement gets a certificate with a code. Anybody holding the document can check it at signsealer.com/verify with no account and no call to us. It is re-derived from the record when checked, so a change shows, and the public check names the signers only to somebody who can show the document's fingerprint, never their email addresses.
No. Events cannot be edited or deleted, which is a database constraint rather than a policy. The sealed PDF shows a changed byte. A published template cannot be edited either: revising it makes a new version, so nothing signed last week changes retroactively. If the record behind a certificate has diverged, the check reports it and changes nothing.
Not with an identity document, no. Attribution rests on the link being sent to a named person's own phone number or email address, the typed name being checked against who the link was sent to, and the address, browser and time recorded at each step. Those are the same facts a court weighs, and they are stronger together than any one of them alone.
No. AATL is a trust list inside Adobe Reader, not a legal standard, and neither ESIGN nor UETA asks for one. What an agreement needs is the evidence: who signed, that they consented first, what text they saw, and that none of it has changed since.
Four ways, and the same record either way: your booking system or CRM starts it with one API call and hears back on a webhook; a personal link goes by email; the same link goes by text; or a tablet at the counter runs one form in kiosk mode, with a QR code for people who would rather sign on their own phone.
A text is only sent with a consent the record keeps, from a number registered for transactional messages. Every message says Reply STOP to stop. A STOP is honoured at once: it revokes the consent and suppresses the number for that business, and the record shows it. HELP is answered with who is sending and how to reach a person.
The tablet app keeps signing and catches up when the connection is back. It is honest about time: the record keeps the moment we received the signature, which is the part we can attest to, and beside it what the device says happened, marked as a claim, with the clock difference computed by us rather than sent by the device.
Yes. A document can have several signers, in order or all at once, and a countersignature from the business. A guardian signing for a minor is recorded as the guardian's own act, with the participant named, rather than folded into one signature.
Yes. Your logo and sender name go on every message and page, and a verified domain of your own can send the mail and host the signing links. Until you add your own domain, messages say they were sent through SignSealer, so the signer can place the address.
In one unit: a completed agreement, however many people signed it. A five-party contract is one, a waiver is one, and nothing is charged for a draft, a void or a document nobody signed. There is no per-user fee, and the expensive inputs such as text messages are metered at cost beside the plan.
Pause the account. Your templates, your team and every piece of evidence stay exactly as they are; the monthly fee stops, and any document you send in the off-season is billed at the pay-as-you-go rate. Coming back means resuming, not starting again.
For as long as your account exists, unless you redact a document yourself. Redaction replaces the text and the signers' personal details; the text's fingerprint, the certificate and the trail of events stay, so a redacted document can still be shown to have existed and been signed, and by how many people. The live demo's documents are redacted after a day.
In the footer of every page, and written to be read: the terms of service, the privacy policy, the cookie notice, the text-message policy, and a form for asking what we hold about you.
Free for the first 25 agreements a month. No card to start.