FAQ
Common questions about Easerix Sign — the audit trail, storage and access, links, limits, and webhooks.
View as MarkdownQuick answers about Easerix Sign: what the audit trail records, where your files live and who can see them, what happens to signing links over time, the file limits, and how to feed signature events into your own systems with webhooks. For sending basics, start with the quickstart instead.
Frequently asked questions
Are documents signed with Easerix Sign legally binding?
That depends on your document, your jurisdiction, and your situation — it's a question for a legal professional, and Easerix Sign doesn't make legal claims on your behalf. What Sign does is record evidence: every document carries an audit trail of who acted, what they did (viewed, filled a field, signed, declined), when, and from which IP address; signers tick an explicit consent checkbox before finishing; and the completed PDF includes a certificate of completion built from that trail.
What exactly does the audit trail record?
Each event records the actor, the action, a timestamp, the IP address it came from, and the browser used. Events cover the document's whole life — created, file attached, sent, reminded, viewed, field filled, signed, declined, voided, completed — and each event carries a SHA-256 hash chaining it to the one before it, so the history is tamper-evident. The trail is on every document page, and the certificate of completion in the final PDF carries it too.
Where are my documents stored, and who can see them?
Uploaded PDFs are stored in Easerix Sign's cloud file storage, and each document belongs to your workspace. A document is private to you until you choose Share with workspace, which makes it visible to your teammates. Recipients only ever see the documents sent to them, through their personal signing links.
Can people without an Easerix account sign?
Yes — that's the normal flow. Signers get an email with a personal link and complete everything in the browser. See You've been asked to sign.
How are signing links protected?
Each link contains a long token unique to one recipient on one document, so it works only for them. You can add a per-recipient access code (share it outside the email) as a second factor, and repeated failed attempts against signing links are rate-limited. Links stop working the moment a document is voided or expires.
What are the file limits?
PDF only, up to 25 MB per document.
Can I download a signed document later?
Yes. Download on the document page always fetches the current PDF; once the document is completed, that's the final version with every signature stamped in plus the certificate of completion. Signers also receive the final document by email.
Can I connect Sign to my own systems?
Yes — webhooks, under Settings → Webhooks in Sign. Add an endpoint URL and Sign POSTs document events (sent, viewed, signed, declined, completed, voided, expired) to it. Deliveries are HMAC-signed with an X-Easerix-Signature: sha256=<hex> header over the raw body; the signing secret is shown once when you create the webhook.
Last updated on