Generate a signed-style certificate documenting that your file was processed locally, complete with a SHA-256 fingerprint an auditor can independently verify. Useful for client files, compliance records, and internal audit trails.
Two things. First, it records the SHA-256 fingerprint of your document — a value that changes completely if even one byte of the file is altered, so anyone can confirm the file they hold is the one the certificate covers. Second, it documents that the processing happened in your browser, which is a property of how VaultPDF is built rather than a promise you have to take on trust.
It is a technical record, not a legal instrument. It carries no digital signature from a certificate authority and is not notarised. It is designed to support an audit trail or internal compliance file, alongside your own records — not to replace legal advice or a formal attestation. VaultPDF is not a law firm.
Yes, and that is the point. Any SHA-256 tool — a command line, an online checker, or another application — computing the hash of the same file will produce the identical value shown on the certificate. No VaultPDF involvement is needed to verify it.
No. It contains the filename, size, timestamp, the operation you selected, and the fingerprint. The content of the document itself is never read into the certificate, and nothing is transmitted anywhere.