What you're looking at
A Mekavo service record is a chain of timestamped, cryptographically-sealed entries. Each entry captures who did the work, when, on what mileage, with what parts — plus photo evidence when available. The forensic layer below is what makes it different from any other vehicle history product on the market.
The chain — every entry sealed to the one before it
Each service entry is hashed with SHA-256 the moment it's submitted. That hash is then chained to the hash of the previous entry. The result: editing any past entry breaks the chain on every entry that came after. When you load a record on Mekavo, we recompute every seal in real time and compare it against what was stored at sealing. A green badge means the chain holds — nobody has touched the record since the work was sealed.
Chain intact — every entry verified
This is what a buyer sees when the chain holds.
The photos — fingerprinted at the camera, not the platform
Every photo uploaded with a service entry is hashed (SHA-256) and perceptually-hashed (pHash) before it ever reaches our storage. We also extract the EXIF date the camera recorded when the photo was taken. If a mechanic uploads a 6-month-old photo of a different car, the EXIF date won't match the service date — and we can flag it. If the same photo is reused on two different cars, the perceptual hash collides — and we flag that too.
The witnesses — peer co-signature for high-stakes work
For major work — engine rebuilds, timing belts, transmission swaps — a mechanic can ask a friend or co-worker to co-sign the service record. The witness signs through a single-use 24-hour link, and their consent timestamp is bound into the seal. A chain that includes peer witnesses is a stronger chain.
The mechanic — phone-verified via WhatsApp
When a workshop uploads a service entry, they can verify their identity by sending a one-time code from their own WhatsApp number. That phone-verified flag binds into the seal too. It means a third party didn't just type a mechanic's name into the record — that mechanic actively confirmed they were there, from their own phone, at the time of the work.
What the colours mean
What we capture — and what we never publish
To make the seal forensically meaningful, we capture IP, GPS coordinates, user-agent, and consent timestamp at the moment of submission. None of these are ever shown publicly on a service record. The buyer sees a chain badge, town-level location, EXIF date, and truncated hash fingerprints. The full forensic payload sits server-side, available only to the driver themselves and (with explicit consent) to a dispute resolver. Privacy first, evidence second — both at the same time.
What this means in a dispute
If a buyer ever challenges a service record — "this brake job never happened" — the chain provides an audit trail nobody can fabricate. The mechanic's phone-verified identity, the EXIF-stamped photo, the witness consent, the IP and timestamp of submission, all sealed together with a hash that anyone can independently recompute. A court, an insurer, or a future buyer can verify the record without trusting Mekavo as a platform — they only need to trust the cryptography.
Now check a real vehicle.