Skip to content
Dastawez
Menu

E-signature audit trail and tamper-evident PDFs

Every Dastawez document comes with an append-only audit trail of each step and a digitally sealed, tamper-evident PDF. Together they show who signed, what they signed, and that nothing has changed since.

Anyone holding the sealed PDF can verify it from the QR code on its completion certificate, without uploading the file anywhere.

The evidence behind every document

If a signature is ever denied, the person relying on it may have to prove how it was made. These are the questions that usually come up, and what Dastawez keeps to answer each one.

Who signed?
The email address each link went to, the one-time code if you asked for one, and the time, IP address, and device of every step.
Did they intend to sign?
An explicit consent step that names the signing method, recorded with the version of its wording, and then each field the person completed.
What did they sign?
The SHA-256 fingerprint of the original PDF and of the signed version, printed on the completion certificate.
Has it changed since?
The digital seal and trusted timestamp Dastawez puts on the finished PDF. Any later change is detectable.
Is the record reliable?
An append-only, hash-chained audit trail, and a public verification page for every sealed document.

What the audit trail records

The audit trail is the request's own history, written at the moment each thing happens. It records:

  • when the request was sent, and to whom;
  • each time a recipient opened their link;
  • each one-time code sent, entered correctly, or entered wrongly;
  • the consent each person gave, with the version of the wording they agreed to;
  • each signature or approval, with every value the person filled in, and the SHA-256 fingerprint of the exact version of the document they were shown;
  • declines with their reasons, reminders, cancellation, or expiry;
  • the seal, the completion, and every download of the files.

Every entry carries its time, the IP address it came from, and the device and browser that made it, along with who acted: a person in your team, a recipient, an API key, or Dastawez itself.

Why it can be relied on

The trail is append-only. Entries are added, never edited or removed, and the database itself refuses any attempt to change or delete one. Each entry also includes the hash of the entry before it, forming a chain, so a missing or altered entry would break the chain and show.

Nothing in the trail is filled in afterwards or guessed. If a detail, such as an IP address, was not available, the trail says it was not recorded rather than inventing one.

How the seal works

As each person signs, their values are stamped onto a new version of the document. The original upload is never changed.

When everyone has finished, Dastawez adds the completion certificate page and then digitally seals the whole PDF with its own certificate and a trusted timestamp from a timestamp authority. The seal fixes the exact content of the file at that moment. It also embeds the data needed to check the seal later, and an archive timestamp.

After sealing, any change to the file is detectable: PDF readers that check the seal report it, and the verification page no longer recognises the file. A request is marked completed only after its seal has been applied and checked.

The completion certificate

The completion certificate is the last page of every sealed PDF. It is built from the audit trail, and it shows:

  • the document's name, its number of pages, and when everyone finished;
  • each participant, with their masked email address and their role;
  • when each person viewed, signed, or approved, with the IP address and device;
  • the version of the consent wording each signer agreed to;
  • the SHA-256 fingerprint of the original PDF, and of the signed version before the certificate was added;
  • a QR code and the address of the document's public verification page.

The sealed file's own fingerprint cannot be printed inside the file it describes. It is kept in the audit trail and shown on the verification page instead.

Verify a signed PDF

Every sealed document has its own public verification page. To reach it, scan the QR code on the completion certificate or type the address printed beside it.

The page shows what was sealed: the organization, the document, its pages, who signed or approved and when, and the SHA-256 fingerprints of the sealed file and the original. Then you choose the PDF you were given. Your browser calculates its fingerprint and compares it with the sealed file's, and the page tells you plainly whether it is exactly the sealed file or not.

The file you check stays on your device. It is compared inside your browser and never uploaded.

Security

  • HTTPS everywhere.
  • Documents are stored encrypted, in private storage. Every link to a file expires after 5 minutes.
  • Webhook secrets are stored encrypted, and API keys are stored only as a hash.
  • One-time email codes, where you require them, before a recipient can see the document.
  • Each organization's documents, templates, keys, and webhooks are kept separate from every other organization's.

What Dastawez does not claim

Dastawez gives you a plain electronic signature with strong evidence, recognised under the Electronic Transactions Ordinance 2002. It is not the Ordinance's "advanced" grade, and each signer does not receive a certificate of their own. Dastawez is not for property sale deeds, powers of attorney, wills, trusts, or cheques.

Send your first document free

Upload a PDF, add the people who need to sign, and send it. Your first completed document costs nothing.