GPS Evidence in India: Using Location Data in Court

Introduction

Location is one of the most persuasive — and most contested — kinds of digital proof. When a dispute turns on where a person or a vehicle was at a particular moment, parties increasingly reach for GPS evidence in India: a phone's location history, a vehicle-tracker or telematics log, an app's timestamped entries, or a geotag buried inside a photo. Used well, such data can corroborate a timeline or place a vehicle on a route. Used carelessly, it can mislead, because location can be approximate, derived from indirect signals, or even faked. This article is a practical walk-through of where location data comes from, how reliable it really is, and how to obtain, preserve and prove it so it stands up to scrutiny. It is general information, not legal advice; always read the law as it stands and take counsel where the stakes warrant it.

Sources of Location Data

Location evidence rarely arrives as a single neat file. The most common sources are: a phone's location history exported from the device or the associated account, often as a structured file of timestamped coordinates; vehicle GPS and telematics or fleet-tracker logs that record a vehicle's position, speed and ignition events at intervals; application logs, where ride, delivery, attendance or field-service apps write a position alongside each action; and EXIF geotags — the latitude, longitude and timestamp a camera or phone embeds inside a photo or video file. Each format is different, and each carries its own metadata. Before anything else, record precisely which source a given file came from and how it was exported, because that provenance shapes everything that follows.

Reliability and Accuracy Caveats

Location is an estimate, not a certainty. A satellite fix can be approximate — accurate to a few metres in the open, but off by tens or hundreds of metres indoors, among tall buildings, or under weak signal. Many devices fall back on cell-tower or Wi-Fi positioning, which is coarser still and can place a device in the wrong neighbourhood. Positions can be deliberately spoofed or mocked by software, EXIF geotags can be edited or stripped, and a timestamp may reflect a device clock that is wrong or a time zone that differs from the local one. The practical takeaway: treat any single point as an estimate, prefer continuous tracks over isolated pings, and look for independent corroboration before relying on a location as fact.

Obtaining and Preserving the Original Export

The integrity of location evidence is largely decided at the moment of collection. Wherever possible, obtain the original export in its native format straight from the device or the account — not a screenshot, not a re-saved or converted copy, both of which discard metadata and invite a "this was altered" objection. Note the date, time and method of the export, and the identity of the person who performed it. Then store a read-only master copy that you never edit, and do all analysis on duplicates. The goal is simple: the file you produce later should be demonstrably the same file you collected, with a documented account of how it got from the source to the courtroom.

Why It Needs a Certificate and a Chain of Custody

Location data is an electronic record, so it is generally tendered under the rules for electronic evidence, including the certificate required by Section 63 of the BSA 2023 (formerly Section 65B of the Indian Evidence Act). That certificate captures the device, the acquisition method and the deponent's details alongside the integrity values, and it is the formal, court-prescribed wrapper around the export. Surrounding it is the chain of custody for digital evidence — beyond hashing: the contemporaneous record of who held the file, when, and what was done to it. Neither the certificate nor the custody log guarantees admissibility — that remains the court's call — but together they answer the questions a careful opponent will ask.

Hashing the Export at Collection

The single most useful technical step is to hash the original export the moment you collect it. A cryptographic hash is a fixed-length fingerprint computed over the file's bytes; change one byte and the hash changes completely, so a recorded hash is strong proof the file has not drifted since collection. With e-Dex (the Digital Evidence Integrity Suite) you compute several algorithms — MD5, SHA-1, SHA-256, SHA-512 and BLAKE3 — for the export and generate a readable integrity certificate, entirely offline on your own Windows machine, so the location file never leaves your computer. Months later, anyone can recompute the hash and watch it match the recorded value, turning "trust me, it's unchanged" into a fact a reviewer can verify for themselves.

Frequently Asked Questions

Is GPS location data admissible as evidence in India?
Location data is a form of electronic record, so it is generally tendered subject to the rules for electronic evidence — including the certificate required under Section 63 of the BSA 2023 (formerly Section 65B of the Indian Evidence Act). Admissibility is never automatic: the court weighs how the data was generated, exported, preserved and proved, and whether its accuracy and reliability are established. A clean integrity trail helps, but the final call rests with the court on the facts of the matter. This is general information, not legal advice.

What are the common sources of location evidence?
Common sources include a phone's location history exported from the device or account, vehicle GPS and telematics or fleet-tracker logs, timestamped location entries written by apps, and EXIF geotags embedded in photos and videos by a camera or phone. Each source has a different format and a different reliability profile, so it is important to record exactly where the data came from and how it was exported.

Can GPS location data be inaccurate or spoofed?
Yes. A satellite fix can be approximate, especially indoors, in urban canyons or under poor signal, where the position may be off by metres to hundreds of metres. Location can also be derived from cell towers or Wi-Fi rather than satellites, which is coarser. Software can spoof or mock a position, EXIF geotags can be edited, and timestamps may reflect a device clock or a time zone rather than true local time. Treat a single point as an estimate and look for corroboration.

How should I preserve a location data export?
Obtain the original export in its native format from the device or account rather than a screenshot or a re-saved copy, note the date, time and method of export, and store a read-only master copy that you do not edit. Compute a cryptographic hash of the original file at the moment of collection so any later change is detectable, and keep a contemporaneous chain-of-custody record of who handled the file and when. Work only on copies for analysis.

Why does location evidence need a hash and a certificate?
A hash is a digital fingerprint of the file; if even one byte changes, the hash changes, so it proves the export is unaltered since collection. The Section 63 BSA / Section 65B certificate is the court-prescribed attestation for the electronic record, capturing device, acquisition and deponent details alongside integrity values. Together with a documented chain of custody, the hash and certificate let you show the location data is exactly what was collected. e-Dex produces the integrity proof offline; it does not guarantee admissibility.

Conclusion

Location data can be compelling, but it is only as strong as the care taken in collecting and preserving it. Treat positions as estimates, capture the original export in its native format, document how it was obtained, and lock down its integrity the moment it lands. The quickest way to do that last part is to hash the export at collection and issue a verifiable integrity certificate with e-Dex — the free, offline Digital Evidence Integrity Suite. Download it free and make your location evidence something anyone can re-verify. Remember: this article is general information, not legal advice.