What makes a field photo tamper-proof?

Understand tamper-evident photo records: network-time checks, recorded GPS and trusted file hashes, plus the limits of what they can establish.

Published · Updated · GeoCliks Field Notes

what makes a field photo tamper-proof

Tamper-evident is more precise than tamper-proof: a trusted hash and signature record can help detect changes by comparing a file with its recorded original. Network-time checks and GPS recorded at capture add context, but do not make device-supplied location or the photographed scene independently true. EXIF can be edited, yet an ordinary photo may still be relevant evidence when considered with other records.

Why EXIF alone does not authenticate a photo

Every phone camera writes EXIF: DateTimeOriginal, GPSLatitude, GPSLongitude, make, model. All of it is a plain, writable field inside the file. Open-source metadata editors rewrite any of those tags in one command, and the file that comes out is structurally valid — nothing about it announces the edit.

There are three ordinary ways a field photo loses its claim to being true, and none of them require skill:

  1. The device clock. Settings, toggle off automatic time, pick a date. The camera now stamps whatever you told it, and the EXIF timestamp agrees.
  2. The metadata edit. A command-line tool rewrites the GPS tags to a location the phone never visited.
  3. The screenshot or re-send. Screenshots and most chat apps strip EXIF entirely. What arrives at the office is an image with no time and no place, indistinguishable from a photo taken last year on a different job.

The three layers that actually hold

1. Network-verified time, with the skew shown

The fix for a movable clock is to not use it. GeoCliks stamps the time from the network and compares it to the handset, then records the difference. A photo captured on a phone whose clock is two seconds out looks like this, and it stays verified:

device 14:31:07 · network 14:31:09 · skew 2s · verified

The important part is the failure case. When the skew is large — a clock deliberately rolled back — the photo is not silently corrected and not silently accepted. It is marked unverified, and everyone who opens it sees that mark, including the client. A system that hides the discrepancy is worse than one that has no clock check at all, because it produces confident-looking output either way.

2. Location captured at the shutter, in two places

Coordinates are recorded with an accuracy radius and reverse-geocoded to a street address at capture time, then written twice: burned into the image itself as a visible watermark, and stored as structured metadata alongside it.

43.65107° N 79.34015° W · ±4 m · verified address

Writing it twice is what survives real-world handling. Burned pixels survive a screenshot, a text message, a printout, and a PDF a client forwards three times. Structured metadata survives filtering, mapping and export. Either one alone has a hole: pixels can be cropped, metadata can be stripped.

The accuracy radius matters more than people expect. A coordinate with no stated accuracy is an assertion; ±4 m is a measurement. When the radius is wide — dense downtown, underground parkade — the record says so instead of pretending to precision it does not have.

3. A hash and a signature, resolvable by code

When a capture is uploaded, GeoCliks computes a SHA-256 digest of the uploaded image bytes, binds it to the submitted metadata, signs the record with an HMAC signature, and issues a short photo code. The server upload timestamp is separate from the reported capture time. An illustrative record label looks like this:

GC-8QF2-40XR-91KD · integrity: intact

SHA-256 produces a 256-bit digest of the bytes provided to it. Comparing the actual file with a trusted recorded digest can reveal changes; a server-held HMAC helps protect the associated record. A photo code opens the stored record, but opening a code is not itself a byte-by-byte check of an edited copy in your possession. Hashes do not authenticate what was photographed or stop false inputs supplied before sealing.

AttackEXIF onlyWatermark onlyNetwork time + hash + signature
Device clock rolled backNot detectedNot detectedFlagged as skew, marked unverified
GPS tags rewritten after captureNot detectedOverlay remains, but is not independently authenticatedChanged bytes differ from the trusted digest when compared
Image edited or re-savedNot detectedNot detectedDigest differs when the actual file is compared
Screenshot re-sentMetadata strippedStamp survivesStamp survives; code resolves to original
Photo from a different job reusedNot detectedWrong address visibleCode resolves to the original job record
What each layer can reveal, subject to trusted inputs and actual file comparison

What this costs, and the part that is free

Compare the mechanisms and output options in the plan you intend to use. Check timestamp source, stored records, export formats and retention rather than assuming an expensive plan automatically supplies better evidence.

GeoCliks prices the opposite way. Network-verified time, GPS with street address, the unique photo code, the public verification page and offline capture are on every plan including Free ($0, no card, 300 captures a month). Paid plans — Plus $7/mo, Business $25/mo with 5 seats, Crew 10 $45/mo, Crew 25 $105/mo — add volume, seats, Teamspace, roles and the Excel, ZIP and KMZ exports. They do not add a better seal. Downgrading does not itself delete captures, but access depends on the record being retained and the service remaining available. Keep an independent archive.

A 60-second audit of your current setup

  1. Take a photo with your current app. Change the phone's clock by an hour. Take another, then restore the clock. Check the timestamp source and mismatch handling; an app using server time may not need to print a clock warning.
  2. Screenshot one of last month's job photos and open the screenshot. Is the time and address still legible? Keep the original too: a visible stamp provides context but does not authenticate the screenshot.
  3. Pick a photo from a closed job and find a trusted original or digest. Compare the actual file with that reference; simply resolving a code does not test a copy's bytes.
  4. Check which of the above your plan gates behind a higher tier. That is the real price of the tool.

Follow-up questions

Does a timestamp in the corner of the photo make it tamper-proof?
No. A burned-in stamp survives screenshots and printing, which is useful, but on its own it only records what the device believed at capture. If the device clock was wrong or deliberately changed, the stamp is confidently wrong. Time checks and a trusted hash comparison add context, but do not prove the scene or exact location.
Can EXIF GPS data be faked?
Yes, trivially. EXIF GPS tags are writable fields; standard metadata tools rewrite them in a single command and the resulting file is valid. That is why location has to be captured at the shutter and bound into a signed record rather than read back out of the file later.
What does SHA-256 actually prove about a photo?
A SHA-256 comparison can establish that file bytes match a trusted recorded digest. Without a trusted reference, a hash alone establishes neither history nor authenticity. It does not prove capture time, location, scene truth or who created the photo.
Do tamper-proof photos work without cell signal?
They should. GeoCliks captures offline — the photo queues on the device with its verification data and uploads itself when signal returns, on every plan including Free. Basements, trenches, parkades and rural sites are where field photos are actually taken.
Is a tamper-proof photo admissible as evidence?
Admissibility is determined under the applicable legal rules, not by software branding. Time-source records and trusted hash comparisons may help evaluate a file, but do not independently establish location, scene truth or a successful claim. Preserve originals and other relevant records and seek qualified advice when required.

Capture a verified photo · All Field Notes