Verify a sealed record.
A KeyProof hire record prints fingerprints: of the exact agreement text the hirer signed, of each condition photo, of the hire itself, and of the whole record once the hire is closed. Anyone holding the pack can check them here, with no account and no knowledge of hashing beyond following the steps.
The seals on a hire record, and what each one proves
The terms hash is a fingerprint of the agreement wording. It proves that a copy of the terms you have been handed is word for word what was signed. It does not identify the hire: a firm uses one agreement template, so every hire that firm runs carries the same terms hash, as expected.
The record seal is a fingerprint of the hire. When the hirer signed, one line of text was assembled from the hire's own particulars, the reference, the vehicle, the hire dates, the hirer's name, the deposit acknowledged, the minute of signing and the terms hash, then fingerprinted and stored unchanged. Alter any one of those particulars and the fingerprint changes completely, so a record seal that still matches is a hire whose particulars have not moved since signing.
The close seal is a fingerprint of the whole record at the moment the hire was closed: its particulars, the fuel and mileage readings, the deposit and its outcome, the fingerprint of every condition photo and walkaround video, and the time, kind and author of every timeline entry up to that moment. It is written out as a block of text, one entry per line, beginning keyproof-close-v3 (or keyproof-close-v2 on a record sealed before the joint sign-off at return was added, and keyproof-close-v1 on one sealed before walkaround videos were), and printed with its fingerprint at the end of the record. Anything added to the record after the close, such as a fine or a claim note, is outside it, and the record's timeline marks where the seal falls.
How to check a record seal
- Find the block headed Record seal on the pack. Beneath it, in typewriter type, is a line beginning keyproof-record-v2.
- Copy or retype that line into the record seal box in the checker. It is written in capitals, digits and single spaces on purpose, so that it survives being retyped off paper. A hyphen in a field means the hire carried no such value. If you would rather not retype the whole line, open Assemble it from the pack and fill in the eight fields; the page builds the line for you in exactly the form the seal was taken over.
- Put the 64-character hash printed underneath that line into the second box. The page says whether the two agree, and can ask KeyProof whether the fingerprint matches a hire on record.
A photograph is checked the same way: choose the image file and compare the result against the fingerprint printed under that photograph on the pack. The terms are checked the same way too: paste the agreement text exactly as it appears, line breaks included. So is a close seal: copy the whole block, line breaks included, into the checker's record seal box, and put the fingerprint printed under it into the second box.
What a match does and does not prove
A match proves the copy you hold is identical to what was sealed at the recorded time. It does not decide liability, prove who took a photograph, or make any statement about a hire beyond the integrity of the document itself. Checking a hash here reveals nothing about the record: the answer is only whether the fingerprint matches a seal KeyProof holds. A hire signed before 13 August 2026 has no record seal, and none has been added since, because a fingerprint computed today would attest to today; those records say so on their face and still carry the terms hash. For the same reason a hire closed before the close seal was introduced has no close seal, and none has been added since.
A hire whose record has since been erased, under KeyProof's own data retention schedule or at the firm's own hand, stops matching too, even one that matched for years beforehand: the seals answer against records KeyProof currently holds, and an erased record is not one of them. So a no-match here does not by itself mean the document was altered or never sealed; it can also mean the hire it belongs to is no longer on file.
Everything is hashed in your browser
Pasted text, pasted record seal lines and chosen files are hashed locally on your device and are never sent to KeyProof. Only the 64-character fingerprint travels, and only if you ask us to check it against our records.