Securely architected

Trust is not a checkbox.

Security controls and signing evidence are built into the workflow. Encryption, certificate, timestamp, and long-term validation levels depend on deployment and document configuration.

Signature integrity

A chain of evidence, not an image on a PDF.

Designed around eIDAS and durable PDF signature standards.

PAdES lifecycle

PAdES B-B and B-T depend on certificate and timestamp configuration. B-LTA requires the configured EU DSS upgrade path.

B-B → B-T → B-LTA

X.509 certificate

When configured, an X.509 certificate seals the completed document and binds the final PDF to a verifiable signature chain.

X.509 · SHA-256

Trusted timestamps

External RFC 3161 timestamps can prove when a signature and final seal existed when a timestamp authority is selected.

RFC 3161

Defense in depth

Protection from upload to archive.

Envelope encryption

AES-256-GCM document encryption is available when enabled. Keys and envelopes remain separated.

Malicious PDF scan

Uploaded PDFs are inspected before entering a signing workflow.

Strong authentication

TOTP, WebAuthn and email OTP. Identity checks without weakening the audit chain.

Proof-of-work abuse protection

No third-party CAPTCHA. A privacy-respecting proof-of-work challenge limits automated abuse.

GDPR controls

Export and deletion workflows support data-subject requests and retention policies.

Audit context

IP address, user-agent and geo context accompany signing and access events.

Regional context

One product. Different legal frameworks.

Electronic-signature requirements, excluded documents, and higher-assurance signature rules vary by country.

United States

ESIGN Act · UETA

European Union

eIDAS · eIDAS 2.0

United Kingdom

UK eIDAS context

Brazil

MP 2.200-2 · ICP-Brasil context

Mexico

Commercial Code · NOM-151 context

Colombia

Law 527 context

This overview is educational, not legal advice. Suitability depends on the document, identity level, trust service, and local law.

Public verification

Anyone can check the final record.

The public verify URL validates the sealed PDF and its Certificate of Completion without requiring an inSigner account.

Open public verification

Audit log · document 84F2

5 events
  • document.sent IP · geo · user-agent
  • document.opened Recipient verified
  • signer.authenticated Email OTP
  • document.signed PAdES signature
  • document.completed RFC 3161 timestamp

Ready when you are

Inspect the evidence model.

Start free, then review security and verification on a real completed document.