Evidence pack — Trust Center | VaseSign

VaseSign can produce and expose a combination of artefacts that organisations use for operational verification, internal audit, and procurement diligence. What you receive for a given envelope depends on workspace configuration, integrations, document lifecycle state, and feature enablement. Nothing on this page promises that every artefact exists for every transaction.

Typical evidence components

Component	Description
Completion certificate	Human-readable summary of envelope completion: parties, roles, key timestamps, and outcome when the workflow has closed successfully.
Audit trail extract	Structured list of security-relevant events (send, view, reminder, signature, download) with timestamps and actor references where logging is enabled.
Signature validation report	Output from certificate or DSS validation tooling where integrated — confirms PDF signature packets, chains, or validation status subject to provider configuration.
Evidence record	Machine-oriented record tying ceremony metadata, document revisions, and signing steps together for downstream verification systems.
Document hash	Cryptographic digest (for example SHA-256) of the document bytes at a defined point in the lifecycle, used to detect tampering after signing.
Timestamp data	RFC 3161 or equivalent timestamp tokens where a timestamp authority is configured — proves existence of a hash at a point in time.
Signer identity method	Description of how signers were authenticated (password, OTP, SSO assertion, ID verification outcome) as captured by the product — not a legal identity guarantee.
IP / device / browser metadata	Network and client signals collected where lawful, proportionate, and consistent with your privacy notice — useful for operational fraud review and audit exports.
Consent and intent capture	Records of disclosure acceptance, ceremony acknowledgements, or intent statements presented during signing — wording depends on template configuration.
Verification URL	Public or authenticated link recipients can use to validate exports or verification codes issued for supported artefact types — availability depends on issuance settings.

Access and verification

Authenticated users access signing evidence from the document workspace when enabled. Public verification flows exist for supported artefact types — for example validation helpers or verification codes — subject to issuance settings and retention. Operational URLs for your deployment are documented in implementation guides shared during onboarding or under NDA for enterprise customers.

Certificate validation and advanced signing integrations run through paths configured for your organisation; trust service behaviour is governed by your agreements with those providers.

Typical evidence components

Component	Description
Completion certificate	Human-readable summary of envelope completion: parties, roles, key timestamps, and outcome when the workflow has closed successfully.
Audit trail extract	Structured list of security-relevant events (send, view, reminder, signature, download) with timestamps and actor references where logging is enabled.
Signature validation report	Output from certificate or DSS validation tooling where integrated — confirms PDF signature packets, chains, or validation status subject to provider configuration.
Evidence record	Machine-oriented record tying ceremony metadata, document revisions, and signing steps together for downstream verification systems.
Document hash	Cryptographic digest (for example SHA-256) of the document bytes at a defined point in the lifecycle, used to detect tampering after signing.
Timestamp data	RFC 3161 or equivalent timestamp tokens where a timestamp authority is configured — proves existence of a hash at a point in time.
Signer identity method	Description of how signers were authenticated (password, OTP, SSO assertion, ID verification outcome) as captured by the product — not a legal identity guarantee.
IP / device / browser metadata	Network and client signals collected where lawful, proportionate, and consistent with your privacy notice — useful for operational fraud review and audit exports.
Consent and intent capture	Records of disclosure acceptance, ceremony acknowledgements, or intent statements presented during signing — wording depends on template configuration.
Verification URL	Public or authenticated link recipients can use to validate exports or verification codes issued for supported artefact types — availability depends on issuance settings.

Access and verification

Certificate validation and advanced signing integrations run through paths configured for your organisation; trust service behaviour is governed by your agreements with those providers.