Veridis Attestation

How it works

1. You submit the document. It passes through our application server and is forwarded to a trusted execution environment (TEE), which computes the fingerprint (SHA-256) inside the enclave and discards the file once processing ends. The document is not written to any database nor retained after the attestation.
2. The hardware issues the proof. The chip itself signs a proof that this document passed through it, in an environment that not even the machine's administrator can open.
3. You receive the document with the seal plus a self-contained certificate: a file that carries the whole proof.
4. Verification is independent of the issuer. With the self-contained certificate and the verifier provided by Veridis, a third party checks on their own machine, without querying this site, that the document has not changed and that the proof was issued by genuine hardware. The proof stays verifiable even if this site goes offline.

What this seal proves (and what it does not)

• PROVES that the document has not been altered since the attestation.
• PROVES that this fingerprint was computed on genuine hardware, bound to this document.
• PROVES checkable by a third party, independently of the issuer, without querying this site.
• DOES NOT prove that we did not retain the document: non-retention is our policy, not a fact demonstrable by cryptography. We keep only the fingerprint, for the link's verification counter.
• DOES NOT replace verification by an accredited body (OVV): it says whether the data is correct; we say that no one tampered with it. The two layers add up.
• DOES NOT constitute public faith (notary) and does not assert that the content is true.

For developers and white-label integration

• POST /api/attest → attestation + PDF + self-contained certificate
• GET /api/resolve?token=… → link seal state
• GET /api/tee-info → hardware status