E-Sign Guide

Understanding E-Sign Audit Logs

Every action taken on a StackBloom E-Sign document is recorded in a tamper-evident audit trail. Learn what is logged, how to access it, and how to use it for compliance.

1

What Is Logged

The audit log captures every meaningful event in the lifecycle of a document — from creation to completion. Each event is timestamped and includes the actor's identity and IP address.

EventDetails Recorded
Document createdTimestamp, creator name, document title
Document sentTimestamp, sender name, recipient email addresses
Document viewedTimestamp, signer name, IP address, browser/OS info
Field filledTimestamp, signer name, field type, IP address
Document signedTimestamp, signer name, IP address, geolocation (approximate)
Reminder sentTimestamp, signer email, reminder number
Document completedTimestamp — all signers have signed
Document voidedTimestamp, reason, voiding user name
Audit log downloadedTimestamp, downloader name
2

Timestamps & IP Addresses

All timestamps in the audit log are recorded in UTC and stored with millisecond precision. IP addresses are captured for every signer action to provide evidence of the signer's location and identity.

Sample Audit Entry

2026-02-23T14:32:17.841Z — Document sent
Sender: Jane Smith (jane@company.com)
Recipients: client@example.com
2026-02-23T15:01:44.209Z — Document viewed
Signer: John Client (client@example.com)
IP: 203.0.113.42
Browser: Chrome 121 / macOS
2026-02-23T15:04:11.573Z — Document signed
Signer: John Client (client@example.com)
IP: 203.0.113.42

IP addresses are stored as-logged. If a signer uses a VPN, proxy, or corporate network, the logged IP may reflect the exit node rather than the signer's physical location.

3

How to Download the Audit Trail

You can download the audit log for any document as a PDF. The PDF is formatted for use in legal proceedings and includes a cryptographic hash of the document to prove it has not been tampered with.

  1. Go to the E-Sign dashboard
  2. Find the completed (or voided) document and click on it
  3. In the document detail view, click the "Audit Log" tab
  4. Review the log entries in the browser
  5. Click "Download Audit Log PDF" to save the formatted audit report

What the PDF Contains

  • Document title and unique ID
  • All signer names and email addresses
  • Chronological event log with timestamps and IP addresses
  • SHA-256 hash of the signed document file
  • StackBloom certificate of completion (digitally signed)
4

Legal Admissibility

StackBloom E-Sign audit logs are designed to meet the evidentiary standards of electronic signature laws in the United States (ESIGN Act, UETA) and the European Union (eIDAS Regulation).

ESIGN Act (USA)

Establishes that electronic signatures are legally equivalent to handwritten signatures. StackBloom's audit trail provides the intent, authentication, and record-keeping required under ESIGN.

eIDAS (EU)

StackBloom E-Sign produces Simple Electronic Signatures (SES) as defined under eIDAS. For Qualified Electronic Signatures (QES) required in some EU jurisdictions, consult a legal professional.

Legal Disclaimer

StackBloom's audit logs are designed to support legal validity, but we are not a law firm. For contracts involving significant financial or legal risk, consult a qualified attorney about the appropriate level of signature formality required in your jurisdiction.

5

Retention Period

Audit logs and signed documents are retained according to your E-Sign plan tier.

PlanAudit Log RetentionDocument Storage
Basic1 year1 year
Advanced5 years5 years
Enterprise10 years10 years

We strongly recommend downloading and independently archiving audit logs and signed documents for any legally significant contracts — particularly if your retention requirements exceed your plan's storage period.

Audit Log Tips

✓

Download Immediately After Completion

As soon as a document is fully signed, download both the signed PDF and the audit log PDF and store them in your own document management system.

✓

Verify the Document Hash

The audit log PDF includes a SHA-256 hash of the signed document. You can verify this hash against the downloaded document file to prove the document has not been modified after signing.

✓

Include in Contract Packages

When delivering a signed contract to a client or counterparty, include the audit log PDF alongside the signed document to demonstrate the integrity and chain of custody of the signature.

Next Steps