Website contact data
When a visitor submits the contact form, Docseal may receive name, organization, role, work email, sector, message content, consent flag, technical user-agent information and an IP hash used for operational logging.
Privacy notice per Docseal.
This notice explains how Docseal approaches privacy for website contact requests and scoped pilot discussions. Contractual data-processing terms are defined per pilot.
Last updated: 10 May 2026Pilot data minimization
Docseal pilots can be scoped to minimize personal data exposure. In hash-only mode, document content does not need to be stored or read by Docseal for verification to work.
Possible pilot metadata
Depending on pilot scope, Docseal may process issuer metadata, document type, Seal ID, registry status, file hash, receipt metadata and verification event metadata.
DPA and regulated deployment
For regulated or production deployments, a Data Processing Agreement and privacy review should be completed before launch. Roles, retention, data categories and processing scope are defined contractually.
Retention and export
Pilot retention, receipt export, evidence export and reversibility requirements should be defined in the pilot scope or production agreement.
Contact route
Privacy or pilot data-processing questions should be submitted through the Docseal contact form.
Need a privacy-scoped pilot?
Docseal can be evaluated with hash-only or restricted-visible workflows depending on document sensitivity.