Blog Details

Introduction

A call recording can be decisive evidence. It can capture an admission, a threat, a demand for money, or a promise made in the parties' own voices, and such recordings turn up regularly in matrimonial disputes, extortion complaints and business disagreements. But an audio file on its own answers very few of the questions a court will ask: where did it come from, has it been edited, and was it obtained lawfully? This guide walks through, step by step, how to certify a call recording for court in India the right way — by preserving the original audio, recording the particulars, hashing the file and producing a proper electronic-evidence certificate with e-Dex (formerly Hash Calculator).

When a Call Recording Can Be Evidence

Whether a call recording helps your case turns on two things: authenticity (is this really the conversation it claims to be, between the people it names?) and integrity (has the file been altered since it was made?). A recording that cannot be tied to a device and an event, or that may have been spliced or trimmed, is easy to attack. Because a recording is an electronic record, Indian courts generally expect it to be supported by a certificate rather than simply played from a phone. The steps below are about making both authenticity and integrity demonstrable — so the recording stands up to scrutiny instead of collapsing under it.

An Important Caveat — Consent and Privacy

Before you do anything technical, pause on a threshold question: was the recording lawfully obtained? Recording a phone call without the other party's consent raises real privacy and legal concerns, and courts have at times taken a strict view of recordings made covertly or in breach of a person's rights. A recording that is technically pristine is still of no use if a court declines to rely on it because of how it was made. This is general information, not advice, and the law in this area continues to evolve. Take advice from a lawyer on whether your particular recording can be used at all before you invest effort in certifying it. The remaining steps assume that question has been considered.

Step 1 — Preserve the Original Recording File

Everything else depends on this step. Locate the original audio file exactly as the recording device or app produced it — the native format, whether that is .m4a, .amr, .wav or something else — and keep an untouched copy in a safe location. Do not convert or re-encode it. Turning the file into an MP3, “cleaning up” the audio, or even letting an app re-save it rewrites the underlying bytes, which changes the hash and invites the question of what else was changed. If you need a working copy to listen to or share, make a duplicate and leave the original alone. The original file, on the original device, is your strongest anchor.

Step 2 — Record the Particulars

A certificate is only as useful as the facts it pins down, so write down the particulars while they are fresh. Record the device or app used to make the recording (make, model, application name), the parties to the call, the date and time the call took place, and who recorded it and how. Note where the file has been stored since and who has had access to it — the chain of custody — because that is what lets you later explain how the recording reached the court untouched. These details turn an anonymous audio file into an exhibit tied to a real device, real people and a real event.

Step 3 — Hash the Audio File

Now fingerprint the exact bytes. In e-Dex, add the original audio file and compute a cryptographic hash — SHA-256, and other algorithms such as SHA-512, MD5 or BLAKE3 if you wish — over it. A hash is a fixed-length digital fingerprint: recompute it later and, if it matches, the file is bit-for-bit identical to the one you certified; change a single byte and the hash changes completely. This is what lets anyone — the court, the opposing party, your own expert — confirm the recording has not been edited since it was certified, without taking your word for it. It is worth stressing that e-Dex does not capture or extract the recording. You collect the audio file from the device; e-Dex then hashes and certifies it.

Step 4 — Generate the Certificate

With the file hashed, generate the certificate itself. e-Dex produces a Section 63 BSA / Section 65B electronic-evidence certificate that records the recording device, the particulars you noted and the integrity hashes, with an explicit MATCH verification against the audio exhibit. The output follows the familiar Part A / Part B Schedule form — Part A describing the electronic record and how it was produced, Part B listing the device and the hash values — so it reads the way a court expects. If you want to see the structure first, this Section 65B certificate format with an example is a useful reference.

Step 5 — Sign and Timestamp

Finally, make the certificate tamper-evident. e-Dex can apply a PAdES digital signature using a Digital Signature Certificate (DSC) on a USB token, binding the signer's identity to the document so any later edit is detectable. It can also attach an RFC-3161 trusted timestamp from a Time-Stamping Authority, providing independent proof that the certificate existed in that exact form at that moment. Both steps run from your own Windows machine; only the timestamp touches the internet, and everything else stays fully offline.

Common Pitfalls

A few mistakes account for most weak audio evidence. Re-encoding the file — converting the recording to MP3 or running it through an editor — changes the bytes and breaks the hash, so the certified copy no longer matches the original. Editing or splicing the audio, even to remove dead air, destroys its integrity and is exactly what an opponent will allege; never touch the original. Missing context — no device, no parties, no date, no account of how it was recorded — leaves the court unable to connect the file to anything. And ignoring the consent and privacy question can sink an otherwise sound recording. The steps above are designed to avoid each of these.

A Note on Legal Advice

e-Dex helps you produce a well-structured, integrity-backed certificate; it is a tool, not legal advice and not a substitute for counsel. With call recordings the consent and privacy question is central: whether the recording was lawfully obtained, whether it can be used at all, who must depose to the certificate, and exactly how it is tendered all depend on the facts of your matter and on the text of the provision and the Schedule as it stands. The law has moved — the Bharatiya Sakshya Adhiniyam 2023 now governs — and positions continue to develop. For a broader walkthrough of the rules, this guide to electronic-evidence certificates in India is a good starting point. Always read the current provision, verify the present position, and take advice where the stakes warrant it — e-Dex does not guarantee that any record will be admitted, because that is for the court to decide.

Frequently Asked Questions

Are call recordings admissible as evidence in India?
A call recording is an electronic record, so under Section 63 of the Bharatiya Sakshya Adhiniyam 2023 (the successor to Section 65B of the Indian Evidence Act) it generally needs a certificate to be admitted. Authenticity, integrity and the way it was obtained all matter. e-Dex helps you produce a structured, integrity-backed certificate, but admissibility is decided by the court on the facts of the matter.

Is it legal to record a phone call without consent in India?
Recording a call without the other party's consent raises privacy and legal questions, and courts have at times taken a strict view of recordings made covertly or in breach of a person's rights. Whether a particular recording can be used at all depends on the facts and the current law. This is general information only; take advice from a lawyer before relying on such a recording.

Does a call recording need a Section 65B certificate?
If you are tendering the recording as secondary electronic evidence, a certificate under Section 65B of the Indian Evidence Act, now Section 63 of the Bharatiya Sakshya Adhiniyam 2023, is generally required. The Supreme Court in Arjun Panditrao Khotkar v. Kailash Kushanrao Gorantyal (2020) held that such a certificate is a mandatory pre-requisite for admitting secondary electronic evidence.

Does converting the audio file affect its evidential value?
Yes. Converting or re-encoding the audio (for example from the recorder's native format to MP3) rewrites the bytes, so the hash of the converted file no longer matches the original. That can invite questions about what was changed. Keep and certify the original file exactly as the device produced it, and only convert a working copy if you must.

How do I prove a call recording was not edited?
Hash the original audio file with a tool such as e-Dex to capture a cryptographic fingerprint, then record that hash in a Section 63 / 65B certificate. Anyone can recompute the hash later and confirm a MATCH, proving the file has not changed since certification. Preserving the original recording device and keeping a clear chain of custody strengthens this further.

Conclusion

A call recording can carry real weight — but only if you can show where it came from, that it was lawfully obtained, and that it has not been touched since. Consider the consent and privacy question first, preserve the original file without converting it, record the particulars, hash the audio and wrap it in a signed, timestamped Section 63 certificate, and you give the court something it can actually verify. You collect the recording, then let e-Dex — the Digital Evidence Integrity Suite hash the exhibit, capture the details and generate a court-ready certificate on your own Windows machine, fully offline and free to try.