Signature

A contract is printed, signed and photographed on a phone, so nobody knows which copy is the last one, when each party signed, or whether anything changed afterwards. What is needed is the document sent as a link per signer, and a record of who opened it, who pressed “Sign”, when, and over exactly which bytes.

Who it is for

• Anyone sending contracts out to be signed
• Property offices and property management
• Human resources

• A trail, and nothing more

  JooDax records who opened the link, who pressed “Sign”, when, from which IP address and which browser, and the fingerprint of the exact bytes they were shown. We hold no accreditation from anybody, we verify nobody’s identity, and a typed or drawn name is a name, not proof of identity. What this signature means, and whether anyone accepts it, is not something this app decides.

• One link per signer, used once

  32 random bytes per signer, of which only the hash is stored, and the link is shown once. A link can be withdrawn and stops from that instant, reissued for somebody who lost the message, and the request itself carries an expiry. JooDax does not send the links out: you do.

• In turn, or all at once

  Either each signer waits their turn and their link will not open before it, or everybody’s opens at once. The last signature completes the request, one refusal closes the whole of it with its written reason — and completed, refused, expired and cancelled never reopen.

• A signed copy that does not change

  JooDax writes nothing inside the file. The signed copy is the very bytes that were shown to every signer, kept as its own object, and the original in the Documents app is left exactly as it was and goes on gaining new versions without touching the request.

• A completion record, in plain text

  Plain UTF-8 text with times in UTC: who signed, when, and over which fingerprint, carrying both what the SHA-256 proves — that the file was not altered after it was signed — and what it does not, which is who pressed the button. It contains IP addresses, so it is shown only to a holder of the signing-trail permission and is never handed to a signer.

On one set of data: what happens here reaches these apps without anyone retyping it.

• DocumentsStore files and attach them to records