One hire, one record. It says what it does not have.
Every hire on KeyProof ends in a single dated record. It opens by listing each check as on record, not on record, or not yet due, with the gaps counted at the top. A thin record cannot pass as a full one, which is what makes a full one worth handing to an insurer.
Illustrative record. Not a real renter.
Every pack opens by stating its own gaps.
The reader of a hire record is usually a claims handler, a solicitor or an accountant, on paper, months later, with no context. Absence is the hardest thing for that reader to see: a record with no licence check looks, at a glance, exactly like one with a licence check, because a missing section is simply not there. So the record refuses to let that happen. It opens with a register that names every check and stamps each one.
- ON RECORD. The thing exists and the document shows it, in the detail further down the page.
- NOT ON RECORD. The thing should exist by this point in the hire and does not. It is a stated gap, named in plain words, not an empty space a reader might skim past.
- NOT YET DUE. The thing could not exist yet because the hire has not reached it. Return photos of a car still out on hire are not a gap, and the register does not pretend they are.
One line above the register counts them: how many items are not on record, so a reader who reads nothing else knows how much of the hire has evidence behind it. Every stamp is derived from the booking's own data, not from a box an operator can tick, so no route through the product produces a record that reads better than the hire actually went.
Six checks, each with its own stamp on the register.
These are the items the register names. Each one lands on the same record, in the same place every time, so a reader learns the layout once and knows it on every hire.
Whether the renter completed the check-in link before the keys moved. Everything the renter supplied hangs off this one fact, so it leads the register.
Photo ID matched to a live selfie. Stripe runs the check and holds the document and the selfie as the regulated provider; KeyProof records the pass-or-fail result, not the images. A check carried forward from an earlier hire says so, and never reads as a fresh one.
The renter supplies a DVLA share code and the last eight of their licence number, and you run the free check on gov.uk. KeyProof never contacts the DVLA about a driver: it records that the check was done and when.
Your own hire agreement, e-signed and bound to the booking. The exact terms are hashed at the moment of signing, so any later change to them is detectable. A signature with no sealed terms behind it is stamped as its own gap.
Timestamped photographs of the car when it went out and again when it came back, each set numbered so a reader can cite one. A notice arriving five weeks later meets one dated record, not a camera roll.
The deposit you took, held on your own account, logged against the booking. Alongside it, a server-timestamped timeline of what happened and when, so the sequence is not your word against theirs.
Built to be read by a stranger, months later.
A record is only evidence if someone who was not there can trust it. So the KeyProof record is built for the reader who has no context and cannot ask you a question.
- It states its own gaps. A record that hid what it was missing would make every complete record worth less, because none of them could be trusted to be saying everything. So it says so, in the same fixed place, every time.
- It is derived, not asserted. Every stamp on the register comes from the booking's own columns. There is no field an operator can fill in to make a hire read as more complete than it was.
- The timestamps are server-recorded. The times on the record are set by the system when each thing happened, not typed in afterwards.
- It reads in black and white. The stamps are words, not colours, because a pack is read photocopied at least as often as it is read on a screen.
What the seal says, and what it does not.
When every item on a hire is on record, the pack carries a "Verified by KeyProof" seal. That seal is printed off the register and off nothing an operator can set, so a hire cannot be made to earn it. It says the evidence behind the hire is complete. It does not say who is right about the hire: you decide what counts as new damage and whether to pursue a charge, every time, and KeyProof records what happened without ever scoring it.
KeyProof is not an insurer, an authority or a court, and the record makes no claim that any of them has pre-approved it. What it is designed to be is a straight, dated, complete account of one hire that holds up when it is read. How the underlying data is handled sits on our security page.
One record per hire.
It never overstates itself.
Walk a check-in in the demo and watch the register fill in, or see how the record is made across a whole hire.
Locked for life, any fleet size.
30 days free on every plan. No setup fee, no contract, cancel any time.