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.
| Who | How to check | Where your file goes |
|---|---|---|
| You have the GeoCam app | In 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 app | Upload 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, offline | The 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.
2.How the online check works
What happens to your file, step by step:
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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?
- Use it only at https://tuvambes.in/geocam/verification. GeoCam's reports and evidence packages link to this address.
- The checker uses the same trust list as the app, signed by TUVAMBES, and refuses to give any result if that list has been changed.
- Each release of the checker's files is listed, with their SHA-256 fingerprints, in
verifier-manifest.json, signed with the TUVAMBES root key (verifier-manifest.sig, checkable with the public key intuvambes_root.pem). The checker refuses to give results if its own files don't match. To check the list yourself:openssl x509 -in tuvambes_root.pem -pubkey -noout > tuvambes_root_pub.pem openssl dgst -sha256 -verify tuvambes_root_pub.pem -signature verifier-manifest.sig verifier-manifest.json sha256sum geocam_verify.py geocam_copycheck.py # compare with verifier-manifest.json - You don't have to trust this website alone: the same file gives the same result in the GeoCam app and with the offline reference verifier.
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.
| Result | When it appears | What it means | What to do |
|---|---|---|---|
| Verified | The 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. |
| Modified | The 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 copy | A 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 – changed | A 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 capture | A 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 confirm | A 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. |
| Unverified | Signed, 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 check | The 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 mark | GeoStamp QR | Mark and QR agree? | Result |
|---|---|---|---|
| Found | GeoCam signature correct | Yes, or nothing to compare | GeoCam copy |
| Found | GeoCam signature correct | No (places more than 150 m apart, or times more than a minute apart) | GeoCam copy – changed |
| Found | GeoCam signature wrong | – | GeoCam copy – changed |
| Found | No GeoCam signature | – | GeoCam copy – changed (QR replaced) |
| Found | None found | – | GeoCam copy |
| Not found | GeoCam signature correct | – | GeoCam copy (the picture itself can't be checked) |
| Not found | GeoCam signature wrong | – | Not a GeoCam capture (imitated QR) |
| Not found | No GeoCam signature | – | Can't confirm |
| Not found | None 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:
| Part | Contents |
|---|---|
| Time | Capture 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. |
| Place | Latitude 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 & app | The phone's maker, model and Android version; the app's package, version and build. |
| Capture | Photo 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. |
| Signer | The 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:
- Settings › Security & authenticity › Verify media authenticity, then choose the photo or video; or
- open the file with GeoCam from another app (Open with or Share); or
- tap the shield on a capture in GeoCam's own gallery.
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).
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:
- the capture's files exactly as GeoCam stored them — the capture, its kept original (when it was edited) and the camera's own photo (when kept);
verification_report.pdfandverification_report.json— the check of each file, with its SHA-256;custody_log.json— the capture's signed custody log;README.txtandSHA256SUMS.txt— the SHA-256 of every file in the package.
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.
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
- JPEG: an APP11 segment (marker
FF EB) whose data begins with the 14 bytesTUVAMBES-AUTH\0, followed by the manifest (UTF-8 JSON). It is placed after the EXIF / JFIF segments. - MP4: a top-level
uuidbox whose 16-byte user type is the ASCIITUVAMBESAUTH0001, followed by the manifest. It is appended at the end of the file.
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:
| Field | Meaning |
|---|---|
schemaVersion | 2 |
assertion | The 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. |
mediaHashAlg | SHA-256 |
mediaHashHex | SHA-256 of the media with every byte of zeroedRanges read as 0x00 (9.3). |
zeroedRanges | The location-metadata byte ranges of the media, sorted and non-overlapping: [{"start", "end", "sha256"}], each with the SHA-256 of its bytes at signing. |
signAlg | ES256 (ECDSA P-256 with SHA-256). |
publicKeyB64 | The 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:
- Not a JPEG or MP4 → Unverified (AUTH-009).
schemaVersionhigher than 2 → Unverified (AUTH-015).- No signature segment or box → Unverified (AUTH-001).
- The manifest or payload can't be read → Unverified (AUTH-010).
- 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 atcapturedAtUtc— 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 (OID1.3.6.1.4.1.11129.2.1.17) must show a key kept in secure hardware (TEE or StrongBox) for the appcom.tuvambes.geocam. Otherwise → Unverified (AUTH-006; AUTH-014 when there is no chain). - The key or the leaf certificate is on TUVAMBES's withdrawn list → Unverified (AUTH-007).
- 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. - The attestation's root of trust reports a verified-boot state other than Verified, or an unlocked bootloader → Unverified (AUTH-018).
- The signature over the payload bytes does not verify with
publicKeyB64→ Modified (AUTH-003). - The media hash (9.3) differs from
mediaHashHex→ Modified (AUTH-004). - A location range is changed → Modified (AUTH-016).
- Otherwise → Verified, or Verified – Mark-up / Measurements when
transformlistsmarkupormeasure; 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
| Root | Public 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.
- A hidden mark. 8 bytes are woven invisibly into the photo's brightness: the capture's minute (24 bits, minutes since 1 January 2026 UTC) and place (20 bits each of latitude and longitude, to about 20 m north–south and 40 m east–west). When the GeoStamp shows no place, the mark keeps none (latitude and longitude all ones), so the mark never tells more than the stamp. The GeoStamp itself, including its Google map, is left exactly as it is. Method: the picture is divided into a 96 × 96 grid relative to its size. Each cell's mean brightness (Y = 0.299 R + 0.587 G + 0.114 B, over the inner 4/6 × 4/6 of the cell) is placed on one of two interleaved ladders 4 levels apart, with a per-cell key offset: one ladder means 0, the other 1. The 96 bits (the code and its CRC-32) are each spread over about 96 cells by a keyed shuffle, and read by a weighted vote; cells near black or white are left out. The change is a smooth field of at most ±2 levels (about 47 dB PSNR), which the eye does not see. It survives resizing down to about 1,000 pixels, recompression, brightness changes, small crops and screenshots. Very small copies and heavy edits remove it. A read counts only when its CRC-32 matches, so an unmarked photo is not read as marked. The key and the shuffle are in the published reader.
- A signed GeoStamp QR. The QR still opens the place in any QR scanner:
geo:LAT,LNG, followed by?gc=and, in base64url, the version (1 byte), the key version (1), the latitude and longitude (signed 32-bit, millionths of a degree), the capture time (unsigned 32-bit, seconds since 1 January 2026 UTC), and an ECDSA P-256 / SHA-256 signature (r ‖ s, 64 bytes) overGEOCAM-QR1followed by those 14 bytes. It is made by the official app with GeoCam's QR key. The readable place must be the signed place; a QR whose readable place or signed bytes were changed fails. Public key, version 1 — x:78289e9b1e308ea2057c5cfb45d8fa391122a99167b73c27c0045d4a63d1efb7, y:42f3d632c9ff64abdd306b678d7e1c908dfea0c86ef53c10477a1139e627615c.
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
| Code | Meaning | Result |
|---|---|---|
| AUTH-001 | No GeoCam signature in the file | Unverified |
| AUTH-002 | Earlier signature format (reference verifier only) | Unverified |
| AUTH-003 | The signed record no longer matches its signature | Modified |
| AUTH-004 | The picture or video no longer matches its signature | Modified |
| AUTH-006 | Not signed by the official app on a genuine phone | Unverified |
| AUTH-007 | The signing key or a certificate was withdrawn by TUVAMBES or revoked by Google | Unverified |
| AUTH-008 | The file is damaged | Unverified |
| AUTH-009 | Not a JPEG photo or MP4 video | Unverified |
| AUTH-010 | The signature block can't be read | Unverified |
| AUTH-014 | No certificate chain to check the signer | Unverified |
| AUTH-015 | Signed by a newer version of GeoCam | Unverified |
| AUTH-016 | The location in the file's details was changed after signing | Modified |
| AUTH-017 | An earlier-format capture whose location the phone hid (app only) | Unverified |
| AUTH-018 | The signing phone reported its security as off | Unverified |
Codes AUTH-005 and AUTH-011 to AUTH-013 are reserved.
11.What a result does not show
- A result shows whether a file matches the signature GeoCam made when it saved it, and what the signed record states. It does not show that the scene was not staged, or that what is depicted is true — a photo of a screen or of a printed picture can be signed too.
- The capture time comes from the phone's clock. Satellite or network time, when shown, is an independent reference the phone held at capture; “confirmed by satellite time” means the phone's clock agreed with it to within 60 seconds.
- The location comes from the phone's location services, with the accuracy the phone reported. A mock-location flag is recorded when the phone reports one, but not every way of faking a location can be detected.
- The GeoStamp, and any mark-up or measurements, were added by the app. Measurements are estimates with the stated uncertainty and should be confirmed with calibrated instruments where exact values matter.
- The signature identifies the phone (the app installation) that signed the file — not the person who pressed the shutter.
- The check relies on the phone's secure hardware and Google's attestation. Phones that report an unlocked bootloader or unverified software are not trusted.
- The copy check (section 9.8) helps trace a copy to its capture; it is not proof, and it can't show what else in a copy was changed.
12.Using GeoCam files as evidence
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:
- Keep the files exactly as GeoCam saved them, and keep the original beside any edited copy (on by default).
- Export an evidence package soon after the event, and record its SHA-256 independently (section 8).
- Hand over the evidence package — the files and the report — rather than screenshots or forwarded copies.
- Keep a note of who handled the files and when, after they left the app.
- 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:
- India. Under Section 63 of the Bharatiya Sakshya Adhiniyam, 2023, an electronic record is submitted with a certificate in the form set out in its Schedule — Part A by the party and Part B by an expert — which includes the record's hash value. A verification report gives the SHA-256 of each file.
- United States. Federal Rule of Evidence 901(b)(9) allows authentication by evidence about a process or system that produces an accurate result; Rules 902(13) and 902(14) allow self-authentication by the certification of a qualified person, including for data copied from a device and identified by its hash. The published method and the reference verifier support such evidence and certifications.
- European Union. Under the eIDAS Regulation (EU) No 910/2014, an electronic signature, seal or time stamp cannot be denied legal effect or admissibility as evidence solely because it is electronic or not qualified (Articles 25(1), 35(1) and 41(1)). GeoCam's signatures and time records are not qualified electronic signatures, seals or time stamps.
- China. The Supreme People's Court's Provisions on Several Issues Concerning the Trial of Cases by Internet Courts (2018), Article 11, recognise electronic signatures, trusted time stamps and hash-value verification among the technical means of showing that electronic data has not been tampered with.
- Elsewhere. Many electronic-evidence laws follow the UNCITRAL Model Law on Electronic Commerce (1996), whose Article 9 weighs how reliably a record was generated, stored and kept intact — what the signature, the custody log and the published method describe.
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