Frequently asked questions

FAQ — Seal and anchor a document (generic proof)

Proof of anteriority and integrity of a document: SHA-256 hash, eIDAS timestamping, Hedera anchoring, at €0.20/seal, no subscription.

Short answer

By computing its SHA-256 hash, timestamping it (eIDAS RFC 3161) and anchoring the hash on Hedera. You get verifiable proof of existence and integrity, without revealing the document's content.

How do I seal a document to prove its anteriority?
By computing its SHA-256 hash, timestamping it (eIDAS RFC 3161) and anchoring the hash on Hedera. You get verifiable proof of existence and integrity, without revealing the document's content.
How much does sealing a document cost, and is there a subscription?
€0.20 per seal, eIDAS timestamping included, no subscription or commitment. Seal one-off in 60 seconds, or in bulk via API.
Does my document go to your servers?
No. Only the hash of the document is transmitted and anchored; the content stays with you. 0DATA neither reads nor stores your document.
How can a third party (judge, client, partner) verify my document's hash?
By recomputing the document's hash and comparing it to the hash anchored on Hedera. Verification is public, account-free, and does not depend on 0DATA.
Does sealing count as eIDAS timestamping or a qualified electronic seal?
eIDAS qualified timestamping (RFC 3161) is integrated, conferring a presumption of date accuracy and integrity. Sealing remains a technical evidence element, distinct from a qualified electronic seal under eIDAS.
Can I seal in bulk via API to automate my document flows?
Yes. The API enables bulk sealing and automation of your flows, at €0.20/seal, to integrate integrity proof into your document processes.
Subscribe See comparison