Audit & legal

When the contract goes to court.

Every envelope keeps an append-only audit trail, and a completed envelope gets a certificate of completion with a SHA-256 fingerprint of each signed PDF. Here is what they contain and how to check a file against its certificate.

On this page

What the audit trail records

Each event is stored with its time in UTC, who acted (the recipient’s name and email, or the person in your workspace), the IP address, the browser’s user agent and details of the event. Events are added, never edited or removed. They include:

  • Draft created and document sent
  • Document viewed, each time a recipient opens their link or a document
  • Phone code verified, when a signer enters their SMS code
  • Field filled and document signed, for every field and every signer
  • Document declined, envelope voided, recalled to draft or expired
  • Reminder sent and recipient details corrected
  • Document completed and copy distributed

To read it, click an envelope under Sent. Its Audit trail page lists every event under When (UTC), Actor, Event and IP. Audit in the sidebar opens the Audit log, all activity across your workspace, with Export CSV and Export PDF.

The certificate of completion

When the last signer finishes, VG·Sign makes one certificate for the whole envelope. It is always attached, as certificate.pdf, to the completion email that goes to every signer, every copy recipient and you. The signed PDFs are attached too, unless together they pass 15 MB; then they come as download links valid for 14 days. The certificate lists:

  • The envelope title and ID, the completion time in UTC and your business name under Issued by
  • Each signed document with its ID and the SHA-256 of the final PDF
  • Each signer’s name, email, party, place in the signing order and the time they signed
  • Copy recipients, marked as having received a copy without signing
  • The audit trail, with the device, browser and identification method (Email, Email + SMS OTP, or Account session when you sign in the editor) for views, signatures, declines and SMS checks

You can download it again from the envelope’s audit trail page with Certificate.

Checking the SHA-256 fingerprint

A SHA-256 fingerprint is a 64-character value calculated from a file’s exact bytes. Change one byte and the value changes. The certificate prints the fingerprint of each signed PDF as it was at completion, and the PDFs in the completion email, attached or linked, are those same files.

  1. Save the signed PDF from the completion email, or from its download link. The Signed PDF button on the audit trail page downloads the first signed document of an envelope.
  2. Calculate its SHA-256. On Windows, run certutil -hashfile contract.pdf SHA256. On macOS or Linux, run shasum -a 256 contract.pdf.
  3. Compare the result with SHA-256 of final PDF under that document on the certificate.

If the two match, the file is byte for byte the one that completed. If they differ, the file has changed since then, even if it looks the same. Saving it again from a PDF program is enough to change it.

Where to read more

This article describes what VG·Sign records. Whether that record is enough for a particular dispute is a question for your lawyer.

  • Audit certificates: the audit trail, document integrity and a section on court admissibility.
  • Consumer disclosure: what signers agree to before they sign.
  • Privacy policy: how personal information is handled and how long signed agreements are kept.
  • Security: how data is protected, and our certification status.

Back to help center

  • How signers prove who they are.

    What VG·Sign records about who signed, the SMS code you can add for each signer, and the consumer disclosure every signer accepts. For what the law asks of a particular document, read the pages linked at the end.

    Read
  • Send your first envelope.

    Upload a document, add the people who sign it, place their fields and send. This walkthrough follows the screens in that order.

    Read