For anyone who receives a photo or video taken with GeoCam: GPS Map Camera by TUVAMBES Technologies, a division of TUVAMBES Enterprises (package com.tuvambes.geocam) — courts, lawyers, insurers, investigators, their experts, and anyone else.

Every photo and video GeoCam saves carries a digital signature made inside the phone's secure hardware. Check whether a file is an unchanged GeoCam original — in the GeoCam app if you have it, or right here if you don't. This page also explains exactly how the check works, and what a result does and does not show.

WhoHow to checkWhere your file goes
You have the GeoCam appIn the app: Settings › Security & authenticity › Verify media authenticity, or open the file with GeoCam (section 6).It stays on your phone. Nothing is uploaded.
You don't have the appUpload it in the online checker below (section 1).Sent over an encrypted connection to TUVAMBES's server, checked, and deleted immediately after the check (section 2).
Experts, offlineThe reference verifier, geocam_verify.py (section 7).It stays on your computer.

1.Check a file online

For anyone without the GeoCam app. Choose the photo, video or evidence package exactly as you received it — sent as a file or document, not re-sent as a photo through a chat app.

Open the online checker

2.How the online check works

What happens to your file, step by step:

  1. You choose a file and confirm the notice. The checker accepts JPEG photos (and screenshots or copies of them in PNG or WebP), MP4 videos and GeoCam evidence packages (.zip), up to the size shown above. Nothing is sent until you press Check file.
  2. For a photo, your browser first reads GeoCam's hidden mark and the GeoStamp QR (the copy check, section 9.8), on your device, and sends what they say — a few bytes — with the file.
  3. Your browser uploads it over an encrypted (HTTPS) connection to TUVAMBES's web server at tuvambes.in, which is hosted by Hostinger. There is no account, no sign-in and no cookie.
  4. The server checks it with the method in section 9 — the same checks the GeoCam app makes. It also uses Google's public list of revoked phone certificates, which the server downloads at most once a day; nothing about you or your file is sent to Google. An evidence package is unpacked into temporary files to be checked.
  5. The file is deleted as soon as the check finishes — before the result is sent back to you — together with anything unpacked from it. If something goes wrong, it is deleted all the same, and the server software also removes every upload when the request ends.
  6. Only the result comes back to your browser. TUVAMBES does not keep the file, a copy, the result or any record of what the file showed. No person looks at it, it is not analysed for faces, and it is not used for anything else.
  7. Keep the result yourself if you need it: print it or save it as a PDF from your browser. We can't send it to you later, because we don't keep it.
  8. What is kept: our hosting provider's standard server logs — your IP address, the time, the page address and your browser type, never the file — kept for a limited time for security; and, to stop abuse, a counter linked to a one-way coded form of your IP address, deleted within an hour.

Files larger than the limit, or many files at once: use the GeoCam app or the reference verifier (section 7), which check files without uploading them. For evidence, a check that anyone can repeat — in the app or with the reference verifier — carries more weight than a printout of this page.

3.Is this checker genuine?

4.What each result means

The app and this checker first check the file's signature. When a photo has no signature (a messaging app, a social app or a screenshot removed it), they also run the copy check: GeoCam's hidden mark in the picture and the signed GeoStamp QR. The result combines both. Only the signature can make a file Verified; the copy check can only show that a file is a copy of a GeoCam photo. A missing signature or mark is never called an edit.

ResultWhen it appearsWhat it meansWhat to do
VerifiedThe original GeoCam file, unchanged. Also when the phone only hid the location in the file's standard details (Android does this when another app opens or receives a file), with a note; the signed location stays in the record.The file is the original GeoCam capture, signed by the official app on a genuine phone.Nothing more is needed.
Verified – Mark-up
Verified – Measurements
Verified – Mark-up & measurements
The original file, with mark-up (drawings, shapes or text), measurements or both added in GeoCam before saving.As Verified. The additions are listed in the signed record; they are not part of the scene, and measurements are estimates. When the original was kept, it is a separate signed file, linked by its provenance ID.Nothing more is needed.
ModifiedThe file carries a genuine GeoCam signature, but its picture or video, its signed record, or the location in its details was changed after signing.A change was made after GeoCam signed it (not who made it or why).Ask for the original file.
GeoCam copyA photo with no signature, but with GeoCam's hidden mark and/or a GeoStamp QR with a correct GeoCam signature, and nothing disagrees. Typical: a GeoCam photo sent through WhatsApp as a photo.It is a GeoCam photo, but a copy, so the full proof is missing. The time and place GeoCam recovered are shown.Ask the sender for the original file (in WhatsApp: attach it as a Document).
GeoCam copy – yours (app only)As GeoCam copy, and the capture it points to is in the checking phone's own GeoCam gallery.It is a copy of a photo taken on that phone.Check the original in the GeoCam gallery.
GeoCam copy – changedA photo with no signature in which the hidden mark and the GeoStamp QR disagree, or which has GeoCam's mark but a QR that is not GeoCam's (a wrong or no signature).It started as a GeoCam photo, but its GeoStamp was changed. The time or place shown on the photo cannot be trusted.Do not rely on the time and place shown; ask for the original file.
Not a GeoCam captureA photo with no signature, no hidden mark and no GeoStamp QR.No sign that it was taken with GeoCam: it may come from another camera or app, or be a screenshot or a very small copy. GeoCam cannot say when or where it was taken. This is not a finding that it was edited.If it should be a GeoCam photo, ask for the original file.
Not a GeoCam capture (imitated QR)No signature and no hidden mark, and a GeoStamp QR carrying a GeoCam signature that does not match.The GeoStamp on this photo was not made by GeoCam.Do not rely on the time and place shown; ask for the original file.
Can't confirmA photo whose only GeoCam-like part is a GeoStamp QR without a signature (GeoCam before 1.1.0, or another app); a video without a signature (messaging apps remove it, and videos carry no mark yet); an earlier GeoCam capture whose location the phone hid; or a photo whose copy check could not be read.There is not enough left in the file to tell.Ask for the original file.
UnverifiedSigned, but not by the official app on a genuine phone; the signing key or certificate was withdrawn; or the signing phone reported its security as off.The signature cannot be relied on. Not a finding that the file was edited.Ask for the original file.
Can't checkThe file or its signature is damaged, it is not a JPEG photo or MP4 video, or it was signed by a newer GeoCam version.The file cannot be checked.Ask for the original file, or use the latest GeoCam.

4.1 How a photo without a signature is decided

Hidden markGeoStamp QRMark and QR agree?Result
FoundGeoCam signature correctYes, or nothing to compareGeoCam copy
FoundGeoCam signature correctNo (places more than 150 m apart, or times more than a minute apart)GeoCam copy – changed
FoundGeoCam signature wrong–GeoCam copy – changed
FoundNo GeoCam signature–GeoCam copy – changed (QR replaced)
FoundNone found–GeoCam copy
Not foundGeoCam signature correct–GeoCam copy (the picture itself can't be checked)
Not foundGeoCam signature wrong–Not a GeoCam capture (imitated QR)
Not foundNo GeoCam signature–Can't confirm
Not foundNone found–Not a GeoCam capture

A file with a signature always gets the signature's result (Verified, Modified, Unverified or Can't check); the copy check is then shown only as background. The time and place under a copy result come from the hidden mark when it was read (it is inside the picture, the harder record to change), otherwise from the signed GeoStamp QR. How to send a file so it can be verified: in WhatsApp, attach it as a Document (not as a photo or video), or share it by Google Drive, email or Nearby Share; screenshots, editing apps and social media remove the signature.

5.What GeoCam signs

When GeoCam saves a capture, it writes a signed record into the file and signs it, together with a fingerprint (SHA-256) of the picture or video, using a key that was created inside the phone's secure hardware and never leaves it. The record holds:

PartContents
TimeCapture time (UTC) and time-zone offset from the phone's clock. When the phone had them, its satellite (GNSS) time and network time at the same instant, and whether automatic date & time was on. The time of signing.
PlaceLatitude and longitude (WGS 84), accuracy, altitude and the GPS fix time; the satellites used and in view and their systems (for example GPS, Galileo, NavIC); whether the phone reported a mock-location (fake GPS) app.
Phone & appThe phone's maker, model and Android version; the app's package, version and build.
CapturePhoto or video; random capture and provenance IDs; for an edited copy, the provenance ID of its kept original; a list of what GeoCam did (markup, measure, dual-lens, orientation-pair, camera-original); any measurements, with their ± estimates, method and points.
SignerThe public key, and the phone's Android key-attestation certificate chain, which shows that the key was created in secure hardware for the app com.tuvambes.geocam, and reports the phone's security state — verified boot, bootloader lock, Android version and security patch level.

The GeoStamp printed on the photo is part of the picture; the signed record is the authoritative copy of what GeoCam recorded. Satellite time, satellites and the phone model can be switched off in the app (Settings › Security & authenticity › Record satellite time & GPS signal); the result then says the time is from the phone's clock only.

6.Check a file in the app

On every plan, offline, with nothing uploaded:

The result shows the details of the signed record and the signer. Export report (PDF) saves a verification report; Export evidence package saves the files themselves together with the report and the custody log (section 8).

Check the file exactly as it was saved Ask for the original file, sent as a file or document — by email attachment, USB or a cloud drive — not as a photo or video in a chat or social app, which re-compresses it and removes the signature. A copy whose location the phone hid still verifies, and so does a capture GeoCam stored in Google Drive, downloaded as the original file.

7.Check a file offline (experts)

Anyone without the app can use the online checker (section 1). To check files without uploading them — or to repeat a check independently, as an expert — use our reference verifier, geocam_verify.py — a single, readable Python script that follows the method in section 9 and gives the same result as the app and the online checker (we test all three on the same set of files). It runs on Windows, macOS and Linux, with Python 3.9 or later:

pip install cryptography
python geocam_verify.py IMG_20261005_101530.jpg
python geocam_verify.py --package GeoCam_evidence_20261005_103000.zip
python geocam_verify.py --json VID_20261005_102000.mp4

It prints each file's SHA-256, the result and its explanation, the signed record and the signer checks. --json gives the same as machine-readable JSON. Exit code 0 means every file is Verified, 1 that a file is Modified, 2 that a file is Unverified or a package or custody check failed. Everything runs on your computer; the optional --google-revocation also downloads Google's public attestation status list, and a revoked certificate in the signer's chain then makes the file Unverified, as on the online checker.

For the copy check of a photo or a copy of one (section 9.8), use geocam_copycheck.py. It reads the hidden mark and checks the GeoStamp QR's signature the same way as the app and the online checker:

pip install pillow numpy cryptography pyzbar
python geocam_copycheck.py IMG-20261031-WA0004.jpg
python geocam_copycheck.py screenshot.png --qr "geo:13.082680,80.270718?gc=..."

Without pyzbar, read the QR with any QR scanner and pass its text with --qr.

8.Evidence packages & custody logs

An evidence package is a ZIP file made by the app on request. Its files are stored as they are, not recompressed:

To check that a package is complete and unchanged:

sha256sum -c SHA256SUMS.txt            # Linux
shasum -a 256 -c SHA256SUMS.txt        # macOS
certutil -hashfile <file> SHA256       # Windows, file by file

The custody log records, for one capture, each time it was captured and signed, saved to the phone gallery, shared, put in a PDF report, exported in a verification report or evidence package, uploaded to or downloaded back from the user's own Google Drive (Pro), or checked — with the time (phone clock, UTC) and the file's name, size and SHA-256 at that moment. Each entry includes the fingerprint of the one before and is signed with the same hardware key that signed the capture, so an entry can't be changed, removed, reordered or moved to another capture without the check failing. It records only what happened inside GeoCam on that phone — not what happened to copies after they left the app. It can be switched off in Settings.

Tip — fix the time a package existed As soon as you export an evidence package, record its SHA-256 somewhere independent of the phone — for example in an email to your lawyer, or with a trusted time-stamping service or a notary. That shows the package, and every file in it, existed by that time.

9.The method, step by step

For experts. Byte offsets are zero-based; a range [start, end) includes start and excludes end.

9.1 Where the signature is

The media is the file with that segment or box removed.

9.2 The manifest

{ "schemaVersion": 2,
  "signedPayloadB64": "<base64 of the signed payload bytes>",
  "signAlg": "ES256",
  "signatureB64": "<base64 of an ECDSA P-256 / SHA-256 signature, ASN.1 DER>",
  "certChainB64": ["<leaf certificate, DER, base64>", "...", "<root>"] }

The signature covers exactly the payload bytes as embedded — nothing is re-serialised before checking. The payload is UTF-8 JSON with these fields:

FieldMeaning
schemaVersion2
assertionThe signed record (section 5), e.g. capturedAtUtc, tzOffsetMinutes, timeSource (gnss, network or device), gnssTimeUtc, networkTimeUtc, autoTime, signedAtUtc, latitude, longitude, gpsAccuracy, altitude, fixTimeUtc, satellitesUsed, satellitesInView, constellations, mockLocationDetected, deviceMake, deviceModel, osRelease, appId, appVersion, buildId, captureId, provenanceId, parentProvenanceId, transform, measurement.
mediaHashAlgSHA-256
mediaHashHexSHA-256 of the media with every byte of zeroedRanges read as 0x00 (9.3).
zeroedRangesThe location-metadata byte ranges of the media, sorted and non-overlapping: [{"start", "end", "sha256"}], each with the SHA-256 of its bytes at signing.
signAlgES256 (ECDSA P-256 with SHA-256).
publicKeyB64The signing key's SubjectPublicKeyInfo (DER), base64.

9.3 Why location bytes are zeroed

On Android 10 and later, when an app without the media-location permission opens or receives a photo or video, Android overwrites its location metadata with zeros, in place — the file keeps its size but its fingerprint changes. GeoCam therefore signs the media with those bytes read as zero, and signs each range's own fingerprint separately. The ranges are: in a JPEG, the value bytes of every tag in the EXIF GPS IFD; in an MP4, the ©xyz, loci, gps  and gps0 boxes, from their type field to their end. On checking, each range is unchanged (its fingerprint matches), hidden (all zeros) or changed (anything else). The picture and everything else must match exactly.

9.4 The checks, in order

The result is the first rule that applies:

  1. Not a JPEG or MP4 → Unverified (AUTH-009).
  2. schemaVersion higher than 2 → Unverified (AUTH-015).
  3. No signature segment or box → Unverified (AUTH-001).
  4. The manifest or payload can't be read → Unverified (AUTH-010).
  5. The signer. Each certificate in the chain must be signed by the next (ECDSA or RSA, with SHA-256 or SHA-384) up to one of Google's hardware attestation roots (9.5); the leaf's public key must be publicKeyB64; the leaf (the capture key's own certificate) must be valid at capturedAtUtc — Google's roots are trusted by their key, not by the dates on the copy a phone sends, and the phone's factory intermediates are not date-checked (phones still send Google's 2016 root copy, which expired on 24 May 2026); withdrawn keys and certificates are caught by the revocation checks below; and the leaf's key-attestation extension (OID 1.3.6.1.4.1.11129.2.1.17) must show a key kept in secure hardware (TEE or StrongBox) for the app com.tuvambes.geocam. Otherwise → Unverified (AUTH-006; AUTH-014 when there is no chain).
  6. The key or the leaf certificate is on TUVAMBES's withdrawn list → Unverified (AUTH-007).
  7. The online checker, and the reference verifier with --google-revocation: a certificate in the chain is on Google's attestation status list (revoked or suspended, for example because a phone's keys leaked) → Unverified (AUTH-007). The app works offline and uses the withdrawn list in its signed trust list.
  8. The attestation's root of trust reports a verified-boot state other than Verified, or an unlocked bootloader → Unverified (AUTH-018).
  9. The signature over the payload bytes does not verify with publicKeyB64 → Modified (AUTH-003).
  10. The media hash (9.3) differs from mediaHashHex → Modified (AUTH-004).
  11. A location range is changed → Modified (AUTH-016).
  12. Otherwise → Verified, or Verified – Mark-up / Measurements when transform lists markup or measure; with a note when a location range is hidden.

Notes also report a mock-location flag, and how far the phone's clock was from satellite (else network) time at capture; a difference over 60 seconds is flagged. A report also shows each certificate's SHA-256 and the SHA-256 of the app signing certificate bound to the key — TUVAMBES will confirm on request whether a fingerprint belongs to the official app.

9.5 Trust anchors

RootPublic key (SPKI) SHA-256
Google Hardware Attestation Root (RSA-4096)feb2ea7551ee316ed4bb443c8293b884dbfdea40b603ee3e4f4a897e4580fbae
Google Key Attestation CA1 (ECDSA P-384)3ee44512a1af2beb39c889490c60ea3f82e43f5d5a5532f5ab9419f676cd07ec

Google publishes these roots at developer.android.com. The app carries them, and the withdrawn-key list, in a trust list signed by TUVAMBES; the reference verifier includes the same roots.

9.6 The custody log

Each entry's hashHex is the SHA-256 of the canonical JSON of {recordId, seq, type, atUtc, fileSha256, fileSize, fileName, detail, prevHashHex} — keys sorted, no spaces, UTF-8. prevHashHex is the previous entry's hashHex (empty for the first), seq counts from 0, and signatureB64 is an ECDSA P-256 / SHA-256 signature of the same bytes by publicKeyB64 — the key that signed the capture.

9.7 Earlier format

Pre-release builds of GeoCam wrote manifest version 1, with a plain media hash; every release build writes version 2. The app still checks version 1 files; the reference verifier reports them as Unverified (AUTH-002) and asks you to check them in the app.

9.8 The copy check (photos)

The hidden mark is read first at the size the photo was saved, measuring each cell over exactly the pixels the writer used. Copies that were resized, cropped or screenshotted are then searched for the frame. When the whole frame is read, up to five of the 24 least certain bits may be corrected, provided the CRC-32 then passes and the time is not in the future.

A photo sent through a chat app, or a screenshot of it, loses GeoCam's signature. So that such a copy can still be traced to its capture, photos taken with GeoCam 1.1.0 or later carry two more things. Neither replaces the signature: the copy check is supporting information, not proof. Proof is the signed original file.

The check reports the mark's time and place; whether the QR's signature is correct; and whether the two agree (places within 150 m, and the QR's second within the mark's minute). In the app, it also names the capture in the phone's own GeoCam gallery that they point to. Compare them with the GeoStamp visible on the photo: a different time or place means the GeoStamp was edited, for example by an AI tool.

Limits: the QR key is inside the app, so someone who takes the app apart could make a QR that passes; and someone who knows the method can copy a mark into another picture. A missing mark does not mean a photo was edited (photos from before GeoCam 1.1.0 have none). Videos don't carry a mark yet.

10.Diagnostic codes

CodeMeaningResult
AUTH-001No GeoCam signature in the fileUnverified
AUTH-002Earlier signature format (reference verifier only)Unverified
AUTH-003The signed record no longer matches its signatureModified
AUTH-004The picture or video no longer matches its signatureModified
AUTH-006Not signed by the official app on a genuine phoneUnverified
AUTH-007The signing key or a certificate was withdrawn by TUVAMBES or revoked by GoogleUnverified
AUTH-008The file is damagedUnverified
AUTH-009Not a JPEG photo or MP4 videoUnverified
AUTH-010The signature block can't be readUnverified
AUTH-014No certificate chain to check the signerUnverified
AUTH-015Signed by a newer version of GeoCamUnverified
AUTH-016The location in the file's details was changed after signingModified
AUTH-017An earlier-format capture whose location the phone hid (app only)Unverified
AUTH-018The signing phone reported its security as offUnverified

Codes AUTH-005 and AUTH-011 to AUTH-013 are reserved.

11.What a result does not show

12.Using GeoCam files as evidence

Not legal advice Whether a file is admissible, and the weight it carries, is for the court or authority to decide under its own rules. TUVAMBES does not guarantee that any file, result or report will be accepted. Take advice from a lawyer where you are.

A verification result supports the authenticity of the file — that it is the file GeoCam saved, unchanged. What the file shows is usually confirmed by a witness, often the person who took it. To give a capture the most weight:

  1. Keep the files exactly as GeoCam saved them, and keep the original beside any edited copy (on by default).
  2. Export an evidence package soon after the event, and record its SHA-256 independently (section 8).
  3. Hand over the evidence package — the files and the report — rather than screenshots or forwarded copies.
  4. Keep a note of who handled the files and when, after they left the app.
  5. Be ready for the person who took the photo or video to confirm it, and, where the law requires, for a certificate or an expert.

Some examples of the rules that may apply:

13.Contact

Questions about this method, or a request to confirm the official app's signing-certificate fingerprint: contact@tuvambes.in. A file uploaded to the online checker is deleted as soon as it has been checked (section 2); otherwise files never reach TUVAMBES unless you send them to us. See also the Terms and the Privacy Policy.

↑ Back to top