EasySign

Built so a signed document can prove itself

A signed agreement is only as good as what you can show about it later: who signed, that it was them, and that nobody has changed it since. This is how EasySign answers those questions. Anything marked “Being built” is not live yet; ask us where it is up to.

The document

What protects the file itself, wherever it ends up.

Digital seal (PAdES)
Every completed document is sealed (PAdES) and locked against changes, with a timestamp from DigiCert, a separate time source. Change one character and the seal breaks. The seal certificate is EasySign’s own, so Adobe Acrobat shows whether the file has changed but lists the signer’s identity as unknown; check any copy against our records at sign.easysign.nz/verify.
Outside timestamp
The seal carries an RFC 3161 timestamp from DigiCert (or Sectigo), not just the time on our server. Only a fingerprint is sent to them, never the document.
IDs on every pageBeing built
Each page will carry the signer ID and the envelope ID, so pages cannot be swapped in from another document without it showing.
Original pages unchanged
Your pages are kept as they were. Answers and signatures are added on top, then a signature page and a certificate of completion.

The signer

Checks that the person signing is the person you sent it to.

One-time email code
Before signing, the signer enters a code sent to their email address.
Optional access code
For a request that needs more, add an access code and give it to the signer another way, such as by phone.
Links that expire
Signing links stop working after a set time.
Saved signatures with consent
A sender’s saved signature is only applied with their recorded consent.

The record

What you can show later, and where it is kept.

Tamper-evident audit trail
Each event is chained to the one before it by a hash, so removing or editing an event breaks the chain.
Certificate of completion
Names, emails, IP addresses and times for every signer, and the full event history, at the end of the document.
Signing records in Sydney
Signing records are kept in Sydney, Australia. Documents are stored on Cloudflare R2, requested in its Oceania region (best effort, per Cloudflare).
Filed against the contact
The completed copy is filed against the contact it was sent to, so you can find it again.

Sources

  1. Cloudflare R2 data location (location hints are best effort, not a guarantee)
  2. DigiCert: RFC 3161 time stamp authority server
  3. Sectigo: time-stamping server
  4. RFC 3161: Time-Stamp Protocol

Verify a document

Anyone holding an EasySign document can check it on a public page: whether it is the exact file EasySign sealed, who signed it and when, and whether the signing record is intact. The file stays on your device; only its fingerprint is checked.

Live

Check a document at sign.easysign.nz/verify.

Security questions

If you need detail for your own security review, such as how data is handled or where something is up to, email hello@webgun.nz.

See it with one of your own documents.

Send us a PDF you use now. We will set it up in EasySign and walk you through sending and signing it, on a phone and a laptop.