DataPublisher for Word — E-Signatures

Legally binding signatures.
Native. No third-party account required.

DataPublisher e-signatures are built into the DataRequest response flow. Recipients sign within the same session they fill in their data — from any device, without creating an account or visiting another vendor's platform.

ESIGN Act Compliant UETA Compliant SHA-256 Hashing Certificate of Completion No DocuSign Required
Start free trial See all features

Built on a solid legal foundation

The ESIGN Act (federal) and UETA (state level) establish that electronic signatures are legally equivalent to handwritten signatures when they meet specific requirements. DataPublisher is built to meet those requirements by default.

Intent to sign

The recipient reviews the document and explicitly confirms their intent to sign before applying their signature. This consent step is logged with a timestamp and IP address.

Identity attribution

Each DataRequest link is JWT-secured and tied to a specific recipient. The signed document is matched to the person who was sent that unique link — not an anonymous open form.

Record retention

The signed document, the original hash, the Certificate of Completion, and the full audit trail are archived to your workspace automatically and remain accessible for as long as you need them.

SHA-256 document integrity

Before a document goes out for signature, DataPublisher computes a SHA-256 hash of its content. This hash is stored with the record.

When the recipient submits their signed response, the document is hashed again and compared to the stored value. If the document content has changed in any way — even by a single character — the hashes won't match, and the signature is flagged as invalid.

This means you can prove in any dispute that the document the recipient signed is identical to the document in your record. No claims of "that's not what I agreed to."

Document sent for signature — SHA-256 hash: a3f2c8d914e0b7e5c4293f1a8b6d0e7f2c9143da8e1b0c7f5a2d9e3b6c0f1a4

Document after recipient signed — SHA-256 hash: a3f2c8d914e0b7e5c4293f1a8b6d0e7f2c9143da8e1b0c7f5a2d9e3b6c0f1a4

✓ Hashes match — document integrity verified

Illustrative example. Actual hashes are computed at signing time.

Certificate of Completion

Every signed DataRequest generates a Certificate of Completion — a tamper-evident record of what was signed, by whom, when, and from where.

Certificate of Completion DataPublisher LLC
Document Client Engagement Agreement — Smith Consulting LLC
Recipient Jane Smith (jane@smithconsulting.com)
DataRequest sent June 10, 2026 — 9:14 AM EST
Link opened June 10, 2026 — 11:32 AM EST
Signed June 10, 2026 — 11:35 AM EST
Signer IP 198.51.100.42
Document hash (pre-sign) a3f2c8d914e0b7e5c4293f1a8b6d0e7f...
Document hash (post-sign) a3f2c8d914e0b7e5c4293f1a8b6d0e7f...
Integrity verified Hashes match

Illustrative example. Actual certificates reflect the specific document and recipient.

For recipients — simple

Recipients open their unique link on any device. They see the document, complete any required fields, then draw, type, or upload their signature. A confirmation screen closes the session.

No account creation. No password. No software to install. If they can open a text message or email, they can complete a DataRequest.

For senders — complete audit trail

The task pane dashboard shows every recipient's status in real time — pending, opened, submitted, signed. When a signature comes in, the Certificate of Completion is available immediately, archived to the record.

Everything stays in your DataPublisher workspace — no routing documents through a third-party platform, no waiting for a DocuSign notification, no per-envelope billing.

Signatures that stand up

Start your 14-day free trial. Build a template, send a DataRequest, and collect your first signed response in one session.

  Install DataPublisher for Word Full feature details

Individual $19/mo  ·  Professional $39/mo  ·  Business $79/mo