What you receive
The two kinds of proof Audrie produces, why both exist, and what each one is good for.
Audrie produces two different kinds of proof. They look similar and they are often confused, so it is worth being clear about which is which, because they answer different questions and they are useful at different moments.
| Answers | Held by | |
|---|---|---|
| Authentication proof | "Is this document genuine, and who stands behind it?" | Whoever holds the document |
| Verification certificate | "Did I check this document, and what did I find?" | Whoever did the checking |
Authentication proof travels inside your document
When you authenticate a PDF, the proof is placed inside the file itself, alongside the certificate page. From then on it travels wherever the document travels. Email it, print it to PDF, put it in a data room, hand it over on a USB stick years later: the proof goes with it.
This is deliberate, and it is the more important of the two. It means:
- The document defends itself. Someone who receives it does not have to know what Audrie is, or take your word that the document is genuine. The evidence is right there in the file.
- It works without us. The proof inside the document carries the ledger coordinates for its entry, so anyone holding the file can check it against the public ledger directly. It does not depend on Audrie being reachable, or being in business.
- It cannot be transplanted. The proof is tied to that one exact file. It cannot be lifted off and reattached to a different document, which is precisely the trick that makes a scanned signature worthless.
What it contains is the document's fingerprint, the signature, the identity behind it, when it happened, and where to find the matching public ledger entry.
Authenticate the same document twice and you get two independent records. Audrie will not, however, authenticate a document that already carries Audrie proof inside it, because that would leave the earlier proof stranded and ambiguous.
A verification certificate is your receipt
The second kind is produced when you check somebody else's document. It records that you performed a check, on a specific date, and exactly what came back.
Checking a document is free and needs no account. A verification certificate is different: it is evidence about you, so it requires an account and it is issued only to you.
That is what makes it useful. If you are the person who has to demonstrate you did your due diligence before relying on a document, "I checked it and it was valid" is an assertion. A verification certificate is evidence, with a date on it, that Audrie stands behind and that is itself committed to the public ledger.
It records what was found at that moment: every record that matched the document, whether each one was still valid or had been revoked, how the signer was standing at the time, and the ledger entry for the check itself.
Your verification certificate identifies you. Your account email is stored in the certificate's file details so the check is attributable to you, which is exactly what makes it usable as evidence. It is not printed on the page, but anyone who inspects the file's details can read it. Treat a verification certificate as identifying you, and share it accordingly.
Why both exist
Because two different people need protection, and they need different things.
The person relying on a document needs the document to prove itself, without depending on anyone's cooperation or continued existence. That is the authentication proof, and it lives in the file.
The person checking a document needs to show, later, that they checked and what they found. That is the verification certificate, and it belongs to them, not to the document.
A record that could only be checked while Audrie is available would be a weak record. A check that left no trace would be a weak check. Both kinds of proof exist so that neither of those is true here.
Next
- Verifying a document covers checking a document you were sent.
- What Audrie never sees covers what is stored and what is not.