Understanding Section 65B of the Indian Evidence Act
A deep dive into the legal requirements for digital evidence admissibility and common pitfalls to avoid.
Every WhatsApp message, email thread, CCTV clip and server log that reaches an Indian courtroom passes through a single gate: Section 65B of the Indian Evidence Act, 1872. Introduced by the Information Technology Act, 2000, the provision decides whether electronic material is treated as admissible evidence or quietly discarded as an unproven printout.
Despite being more than two decades old, Section 65B remains the most misunderstood provision in digital litigation. Our review of matters handled during 2023 found that most rejected electronic records failed not on substance but on certification, a procedural miss that is entirely avoidable.
What Section 65B actually says
Section 65B(1) creates a legal fiction. Information contained in an electronic record that is printed, copied or stored on media produced by a computer is deemed to be a document, and is admissible without further proof of the original, provided the conditions in sub-section (2) are satisfied.
- The computer output was produced during a period when the computer was regularly used to store or process information for an activity regularly carried on by the person having lawful control over it.
- Information of the kind contained in the record was regularly fed into the computer in the ordinary course of that activity.
- Throughout the material period the computer was operating properly, or any malfunction did not affect the accuracy of the record.
- The information in the electronic record reproduces or is derived from information fed into the computer in the ordinary course of that activity.
The certificate under Section 65B(4)
Sub-section (4) is where most matters are won or lost. A certificate, signed by a person occupying a responsible official position in relation to the operation of the relevant device, must identify the electronic record, describe the manner in which it was produced, give particulars of the device involved and confirm that the conditions in sub-section (2) were met.
"Such a certificate must accompany the electronic record like computer printout, compact disc, video compact disc, pen drive, etc., pertaining to which a statement is sought to be given in evidence, when the same is produced in evidence."
Who should sign it?
The signatory does not have to be a technical expert. The statute asks for someone who can speak, to the best of their knowledge and belief, about how the device was operated and how the output was produced. For a company's email server that is typically the IT administrator; for a personal phone it is the owner; for a CCTV system it is the person responsible for the recorder.
Common pitfalls we see in practice
- Producing a bare printout or screenshot with no certificate at all, then attempting to cure the defect at the argument stage.
- A certificate signed by counsel or a notary who never had control of the device.
- No hash value or other integrity marker, leaving the record open to a challenge that it was altered after acquisition.
- A certificate that describes the device vaguely, with no make, model, identifier or operating system.
- Filing the certificate months after the record, inviting a dispute about whether the two refer to the same output.
Looking ahead: the Bharatiya Sakshya Adhiniyam
The Bharatiya Sakshya Adhiniyam, 2023 replaces the Evidence Act from 1 July 2024. The certification requirement survives as Section 63, with a prescribed certificate format in the Schedule that explicitly asks for a hash value and an expert confirmation. Practitioners who already treat hashing and device particulars as mandatory will find the transition seamless.
The practical lesson is unchanged: treat certification as part of acquisition, not as paperwork to be assembled before a hearing. Generating the certificate at the moment the record is captured, with a verifiable hash, removes almost every objection a court is likely to entertain.