How are repair photos sealed — and what do they prove?

A photo only counts as documentation if nobody can swap it out afterwards.

  • The server seals every photo and video: storage location, checksum, time
  • After that, the original can’t be overwritten
  • This makes the documentation hard to tamper with — it is not proof of authenticity

Six steps

What happens when a file is sealed.

  1. The server assigns the storage location Not the app.
  2. Checked on the bytes Not on the file extension.
  3. SHA‑256 checksum Over the stored bytes, on the server.
  4. Time from the server A phone’s clock can be changed.
  5. Unchangeable afterwards A correction is a new entry.
  6. Everything in the log Add only, never change.

What this secures — and what it doesn’t.

What it secures

  • The original can’t be overwritten.
  • Time and checksum come from the server, not from the device.
  • If the workshop removes a photo or video you could see, a note with the date remains.
  • Every step is in the log — including hiding, with a reason.

What it doesn’t secure

  • That what the picture shows is genuine: a prepared image is sealed flawlessly.
  • When it was taken: the time is the time of sealing.
  • Where an uploaded file comes from — which is why it is marked “Uploaded”.

That’s why we say hard to tamper with — never “tamper-proof”.

Access

Access has tight limits too.

  • 1repair job per invitation
  • 24 hthen the guest session ends by itself
  • 5code attempts per day
  • Any timethe workshop can revoke access

Internal notes are stored separately — every workshop sees only its own repair jobs.

Frequently asked question

Are the photos “tamper-proof”?
No, and we don’t claim they are: once sealed, no device and no account can overwrite the original, but the workshop can hide or delete a photo. That is not proof of authenticity.