The hash-chained audit trail
Every event linked to the one before it, so the sequence can't be quietly rewritten.
Every audit trail records what happened. Ours records it in a way that makes silent editing detectable.
The chain
Each event stores a hash computed over its own content and the hash of the previous event. Change event 4 and its hash changes; event 5 no longer matches it, and so on to the end. You cannot alter one entry without rewriting every entry after it.
What's recorded
- envelope created, sent, corrected, voided, expired
- each invitation, reminder and email delivery result
- every view, with IP address and browser
- consent, with the exact time it was given
- each signature, decline, reassignment and approval
- access-code attempts, including failures
- payments, with reference numbers
- workflow actions and custody transfers
- retention purges
Checking it
Admins can verify every chain on the account under Admin → Audit integrity. It recomputes each hash from scratch and reports any break.
The full trail is downloadable as CSV per envelope, and is appended to the sealed PDF as the certificate of completion.
Under sections 65A and 65B of the Indian Evidence Act, electronic records need to be accompanied by evidence about how they were produced and kept. A tamper-evident chain is exactly the kind of thing that supports such a certificate.
Was this useful?