Trusted timestamps — proving when, not just what
An independent authority attests the time, so you don't have to take our word for it.
Our seal proves a document hasn't changed. On its own it doesn't prove when it was signed — the time comes from our server's clock, and we're an interested party.
What we do about it
At sealing time SignSpry sends the document's hash (never the document) to an independent Time Stamping Authority under RFC 3161. The authority returns a signed token saying "this hash existed at this instant". We embed the token with the seal.
Because only the hash leaves our servers, the authority learns nothing about your contract — it cannot reconstruct the document from a hash.
Why it matters
Backdating is the most common attack on a document's story. An independent timestamp makes it impossible: to claim a contract was signed in March, you'd need an authority that isn't us to have said so in March.
Checking it
The verification page shows the timestamp alongside the seal, along with which authority issued it, and confirms it covers this exact document.
When it's unavailable
If the authority can't be reached, signing still completes — a signature ceremony is never held up by someone else's outage. The document is sealed and recorded as carrying our timestamp only, and the verification page says so plainly rather than implying an independent attestation that doesn't exist.
Admins can change or disable the authority under Admin → Settings.