Skip to content

Free buyer resource

Electronic signature privacy checklist

Twelve concrete questions for any eSignature vendor. Ask for answers you can test, not just a promise that your documents are encrypted.

Prepared November 8, 2026. Vendor-neutral evaluation questions. No sign-up required to read or print.

How to use this checklist

Share the same questions with each provider. Record the evidence, plan, and review date for each answer. A question is not an allegation that a provider fails a control. Some teams need extensive certifications or integrations; others mainly need practical signing with a smaller data-access boundary.

Tip: use your browser's Print command to keep a copy and fill it out with your procurement team.

Data boundaries

Which parts of an agreement can the provider decrypt?

Why it matters: The uploaded source PDF, filled fields, attachments, and metadata may have different protections.

Evidence to request: Request a data-flow diagram that names each data type and its encryption boundary.

Vendor and plan: ____________________ Reviewed on: __________

Who holds the keys needed to decrypt protected content?

Why it matters: Encryption at rest does not reveal whether the provider can independently open data.

Evidence to request: Ask for key custody, recovery and server-side access documentation.

Vendor and plan: ____________________ Reviewed on: __________

Where are new signer values encrypted and decrypted?

Why it matters: Browser-side protection and server-side decryption create different operational risks.

Evidence to request: Request a documented description of browser, server and storage operations.

Vendor and plan: ____________________ Reviewed on: __________

Accounts and recovery

What happens when a signer loses a device or password?

Why it matters: Recovery should be usable without quietly granting the provider unrestricted access.

Evidence to request: Walk through a supported recovery process with test users.

Vendor and plan: ____________________ Reviewed on: __________

Can new team members read historical completed agreements?

Why it matters: Organization access, sender access and participant access can differ.

Evidence to request: Inspect permissions with a newly added auditor in a test workspace.

Vendor and plan: ____________________ Reviewed on: __________

Recipients

Must external signers create an account?

Why it matters: The guest journey affects completion and support costs.

Evidence to request: Run a signing invitation in a private browser window on mobile.

Vendor and plan: ____________________ Reviewed on: __________

How are invitations and signer identities verified?

Why it matters: An email link, passcode and identity verification are not interchangeable.

Evidence to request: List each method available on the purchased plan and assess your risk needs.

Vendor and plan: ____________________ Reviewed on: __________

Documents

Can the service or its subprocessors access uploaded source PDFs?

Why it matters: A protected signature field does not automatically encrypt the original PDF.

Evidence to request: Ask where PDF rendering, assembly and delivery take place.

Vendor and plan: ____________________ Reviewed on: __________

Can users export readable signed agreements and audit evidence?

Why it matters: Teams may need a durable usable record independent of their vendor account.

Evidence to request: Test export and readability of a completed agreement and its audit record.

Vendor and plan: ____________________ Reviewed on: __________

Operations

How long are documents, metadata and backups retained?

Why it matters: Retention periods and backup deletion may differ.

Evidence to request: Read the retention policy and validate available deletion controls.

Vendor and plan: ____________________ Reviewed on: __________

What independent security evidence is available?

Why it matters: A marketing badge is not a substitute for a scoped report or operational controls.

Evidence to request: Ask for current audit reports, scope, exclusions and independent assessment dates.

Vendor and plan: ____________________ Reviewed on: __________

Cost

What exactly counts toward a send or envelope limit?

Why it matters: Included seats, requests, API use, templates and bulk sends can have separate rules.

Evidence to request: Model a typical month, check plan terms, then test an actual workflow.

Vendor and plan: ____________________ Reviewed on: __________

How Inklok answers the key question

Inklok encrypts protected values entered during signing in the participant's browser. Inklok does not possess an independent key to decrypt those protected completed values. Inklok still processes uploaded source PDFs and operational metadata to run the agreement workflow. That distinction is central to an informed comparison.

Read the security overview for the documented boundary. For a visual explanation, see who can read which parts of an agreement.

Electronic Signature Privacy Checklist for Buyers | Inklok