Every hire.
Clearly documented.
The driver, the agreement, the condition and the timeline in one dated record. Every check is named. Every gap is visible. Ready to refer back to long after the keys come home.
One link,
throughout the hire.
The hirer’s check-in becomes the pass you read at handover, the thread the hire runs on and the record you keep. Each stage adds context to the same hire.
- Before collection
Send the link. The hirer completes their details and checks on their own phone.
- At handover
Read their pass, record the condition and confirm what happened before the keys move.
- During the hire
Keep extensions, notes and any issues attached to the same booking.
- After return
Close the hire with its return condition and keep one record of the whole journey.
Know exactly
what is on record.
A reader should never have to guess what is missing. The register opens every pack with a gap count and one of three plain-language states beside each check.
The evidence exists. The detail further down shows it.
It should exist by this point in the hire, but does not. The gap is named, never left blank.
The hire has not reached this stage. A car still out on hire is not missing its return photos.
The detail
behind the record.
Six checks in a consistent layout. The stamps come from the booking’s own data, so an operator cannot tick a box to make a record look more complete.
- Hirer check-in
- Whether the hirer completed the link before the keys moved, and when. Their supplied details belong to that check-in.
- Identity check
- Photo ID matched to a selfie by Stripe. Stripe holds the images; KeyProof records the result. A check carried forward from an earlier hire is labelled as such.
- Driving licence
- The hirer supplies a DVLA share code and the last eight characters of their licence number. You run the free check on gov.uk. KeyProof records that it was done and when; it never contacts the DVLA about a driver.
- Signed agreement
- Your own agreement, e-signed and bound to the booking. The wording at signing and the hire particulars are fingerprinted with SHA-256, so a later change is detectable.
- Condition at both ends
- Timestamped photographs at handover and return, each individually fingerprinted and numbered so a reader can cite one. You decide what counts as new damage.
- Deposit and timeline
- The deposit you took, held on your own account and logged against the booking, beside a server-timestamped sequence of what happened and when.
Clear today.
Useful months later.
A claims handler, solicitor or accountant may read the pack long after the hire. The record is built to make sense without the original conversation.
Check a record’s fingerprints- Readable on paper
- States are written in words, not communicated by colour alone. The pack still works when it is printed, copied or forwarded.
- Share only the relevant hire
- A read-only link needs no account and expires after 30 days. The DVLA share code and hirer contact details are withheld. Creating a link is logged, and one action revokes every live link.
- A defined retention period
- Records are kept for 24 months after the hire ends, then deleted in full. The clock stops while a dispute is flagged or a claim or fine is open.
A seal with a clear meaning.
When every item is on record, the pack carries the “Verified by KeyProof” seal. It says the evidence behind the hire is complete. It does not say who is right, or whether a charge is justified.
The agreement, photos and hire particulars are tamper-evident, not tamper-proof. Anyone holding the pack can compare its fingerprints in their own browser, with no account or need to contact KeyProof.
KeyProof is not an insurer, an authority or a court. The record claims no pre-approval from any of them. Read how we handle the data on our security page.
Build a stronger record on your next hire.
See the checks, the handover and the finished record in the demo.
KeyProof is selecting UK car hire operators for its private beta, ahead of public launch in January 2027.