SHA-256 seal on every PDF
Each sealed PDF’s fingerprint is registered. Any change after sealing produces a different fingerprint, and the public check says so.
Built so a funder can check your document, not just read it.
Every sealed PDF carries a fingerprint anyone can verify, every signature has an audit trail, and nobody signs in with a password that can leak.
Free public verificationNo passwordsNever used to train AI
Six things that happen on every document.
Signed on your device
Signatures are drawn and placed in your browser. DocuCraft registers the fingerprint of the signed file, not the file itself.
Full audit trail
Who signed, when (in WAT) and how they confirmed their email, on a certificate page and on the public seal record.
Sign-in without passwords
A one-time code by email, with an optional authenticator app and passkeys. Codes are hashed and expire in 10 minutes.
Your documents stay yours
Client documents are not used to train AI models. Experts see only the documents for jobs they accept.
Money held until you approve
Expert fees are held by DocuCraft until you approve the work. Payments run through Paystack; DocuCraft never sees card numbers.
Good to know.
Where is my data stored?
In a managed Postgres database in the EU (Frankfurt). Files you merge, split or sign in the browser never reach our servers.
Who can see my documents?
Only you, and an expert you hire for that job. DocuCraft staff open a document only to resolve a dispute or a report, and that is logged.
Can someone fake a DocuCraft seal?
They can copy the stamp, but not the fingerprint. The public check compares the file itself against the register.
How do I report a problem?
From Help & reports in your workspace, or from the Help centre. Reports about data misuse are reviewed first.