WhatsApp Group Chat Evidence under Section 63 BSA: The Complete Legal Guide (India 2026)

Home › Blog › WhatsApp Group Chat Evidence under Section 63 BSA

Table of Contents

1. Quick Answer: Are WhatsApp Group Chats Admissible in Court?
2. Why Group Chats Are Legally Harder Than One-to-One Chats
3. The Admissibility Framework: Section 63 BSA for Group Chats
4. The Group Admin Chapter: Liability Rules After Kishor v. Maharashtra
5. Attribution: Proving Who Sent What in a Group of 50
6. Hearsay vs Direct Admission in Group Threads
7. The Group Evidence Protocol: Export to Exhibit
8. Section 63 BSA Certificate Tailored for Group Chats
9. Comparison Matrix: One-to-One Chat vs Group Chat Evidence
10. Case Study: The Housing Society Group That Decided a Crore-Rupee Dispute
11. Cross-Examination Checklist for Group Evidence
12. 8 Fatal Mistakes with Group Chat Evidence
13. Frequently Asked Questions
14. Conclusion & Action Plan

Quick Answer: Are WhatsApp Group Chats Admissible in Court?

Yes — WhatsApp group chats are admissible in Indian courts, but they carry three extra layers of legal complexity that one-to-one chats don't:

Get these three right — certified record, number-based attribution, correct liability theory — and group chats are among the most powerful evidence types in Indian litigation: multiple witnesses' worth of contemporaneous statements, timestamped, in one exhibit.

Why Group Chats Are Legally Harder Than One-to-One Chats

In a one-to-one chat, the legal questions are simple: Is this chat real? Is it complete? Is it certified? In a group chat, four additional questions appear — and opposing counsel will ask every one of them:

Question 1: "Who actually sent this?"

In a group, sender labels are display names chosen by members themselves. "Rohan Sharma" as a sender label is self-declared. Groups also allow changed numbers, secondary SIMs, and shared phones. Attribution — connecting the label to a verified person — is the single biggest battleground in group evidence.

Question 2: "Did the witness curate this?"

A group of 200 members generates enormous volume. If you file 40 pages cherry-picked from a 2-year group history, the other side will argue selective extraction: "Where are the messages that show context? Where are the witness's own messages?" Completeness pressure is far higher in groups.

Question 3: "Is this hearsay?"

When member A posts in a group "B told me he will never pay," and you file it against B — that's hearsay if offered to prove B said it. When member A posts "I will pay by Friday" and you file it against A — that's a direct admission. Group threads mix both constantly, and your exhibit must be built to survive the distinction.

Question 4: "Who is responsible — the sender, the admin, or the group?"

Indian courts have spent years on this. The settled position (detailed below) protects admins from automatic liability — which cuts both ways depending on which side of the "v." you're on.

The Admissibility Framework: Section 63 BSA for Group Chats

The statutory machinery for group chats is the same Section 63 BSA 2023 framework that governs all electronic evidence — but applied with group-specific care.

The controlling authorities

1. Ambalal Sarabhai Enterprise Ltd. v. KS Infraspace LLP (Supreme Court, 2019): The Supreme Court confirmed that WhatsApp messages — including group communications — can be admitted and proved through the testimony of a witness familiar with the conversation, subject to cross-examination on authenticity. This is the green light: group chats are not a special, excluded category.

2. Arjun Panditrao Khotkar v. Kailash Kushanrao Gorantyal (2020): The certificate under Section 65B(4) — now Section 63(4) BSA — is a condition precedent for secondary electronic evidence, and Shafhi Mohammad (which had relaxed the requirement) is overruled. For your group export, the certificate is mandatory.

3. Section 63(3) BSA — the network-device rule (especially useful for groups): The BSA treats a network of computers, or computers with different locations/processors linked together, as constituting a single computer system for certification purposes. A group conversation is, literally, a network of linked devices — this provision maps onto it naturally and lets one certificate cover the record as received and stored on your device.

The two doors for group chats (same as one-to-one)

Under Arjun Panditrao, you prove a group chat by one of two routes:

The group-specific certification wrinkle

Your Section 63 BSA certificate must describe the record as what it actually is: a multi-participant group conversation as stored on your device. That means the certificate's identification limb should state:

• The group name (exactly as displayed)
• The export date and the message date-range covered
• That the record contains messages of multiple participants as received on your device
• Your role (member; admin if applicable) — your role affects what you can truthfully certify about your device, not about others' devices
• The participant key (see attribution section) as an annexure

The Group Admin Chapter: Liability Rules After Kishor v. Maharashtra

Few questions in Indian internet law have generated more panic — and more bad police practice — than "can the group admin be arrested for what a member posted?" The High Courts have now answered clearly. If your dispute involves a group, you need to know this chapter cold, whichever side you're on.

The landmark: Kishor v. State of Maharashtra (Bombay High Court, 2021 SCC OnLine Bom 654)

A man named Kishor Tarone was named in a charge sheet as the admin of a WhatsApp group in which a member had allegedly posted objectionable content. He moved the Nagpur Bench of the Bombay High Court (Justices Z.A. Haq and A.B. Borkar) under Section 482 CrPC to quash the proceedings. The Court quashed them, holding:

The Court's reasoning, in plain terms:

1. An admin has no power to moderate before posting. Unlike a newspaper editor, a WhatsApp admin cannot pre-screen content — the admin's only powers are adding/removing members. Holding an admin liable for not removing a member or not demanding an apology "would be stretching the legal provisions too far."
2. Merely creating a group is not "publishing or transmitting" content under the Information Technology Act — so an admin isn't even an "intermediary" by default.
3. No vicarious criminal liability without a specific penal provision — and no Indian statute makes admins automatically liable for members' posts.

The supporting line of authority

What this means for YOUR case — the two-way sword

If you are the CLAIMANT wanting to use group evidence:

• Don't waste your case targeting the admin for members' content. Absent proof of common intention or a pre-arranged plan (e.g., messages showing the admin orchestrating the posts), the Kishor rule will get the admin discharged. Target the actual senders — their messages are their own admissions and their own liability.
• The common-intention exception is narrow but real. If you have group evidence showing the admin coordinating, encouraging, or pre-planning objectionable posts (e.g., "Admin: everyone post this on the group tomorrow"), Kishor itself leaves that door open. Preserve and exhibit those messages specifically.
• An admin's OWN posts are fully attributable to him — Kishor protects admins from others' content, never from their own.

If you are an ADMIN who is being accused:

• Kishor and Ashish Bhalla are your shield: mere admin status, failure to remove a member, and failure to demand an apology are not liability.
• Your exposure begins where your own conduct begins: your own objectionable posts, or provable coordination with members.
• Preserve the full group chat — including messages before and after the alleged content — because your defense will often be contextual (e.g., the group's purpose, your inactivity, your lack of participation).

Attribution: Proving Who Sent What in a Group of 50

Attribution is where group evidence is won or lost. A court will not act against "Rohan Sharma, sender label." It will act against "+91-98XXXXXX10, registered to Rohan Sharma per the telecom provider's Customer Application Form." Build the chain in layers:

Layer 1 — The export itself

The native group export (_chat.txt) contains, for every message: [date, time] Sender Label: message. For members not saved in your contacts, the sender label is the raw +91 number — this is the single most valuable property of the export file, and one more reason screenshots (which show only your saved contact names) are inferior.

Action: In your exhibit's participant key, list every relevant member as: Sender label (as displayed) — phone number (as it appears in the export) — real identity (per your affidavit and supporting documents).

Layer 2 — Number-to-person linkage

Layer 3 — Device anchoring

The ultimate attribution proof: the device. If attribution is seriously contested, Door A of Arjun Panditrao applies — the member's own phone holds the group's copy of their messages. In practice, you apply this pressure rather than execute it: a court direction to produce the device, backed by your intact hash-verified export, forces settlement or compliance more often than it forces a lab examination.

The group-info snapshot

At export time, also capture the group's info page: group name, description, creation-linked info where visible, member count, and member list with numbers (on Android: group name → view members). This snapshot anchors the group's composition at the preservation date — crucial because membership changes over time, and "was X even in the group on that date?" is a standard defense question.

Hearsay vs Direct Admission in Group Threads

Group chats mix two evidentiary species. Confusing them gets evidence excluded — or worse, gets you relying on a statement that legally proves nothing.

The two species, with examples

Rules of thumb for building your exhibit

1. File against senders, not subjects. Your strongest group evidence is always the target's own messages. Build the exhibit around those.
2. Use hearsay messages for context, not foundation. "A said B told him…" can corroborate your narrative and credibility, but anchor every legal claim on direct admissions.
3. Admissions law applies normally. A member's own group messages are admissions under the law of evidence (formerly Sections 17–23 IEA; renumbered in the BSA) and can be used against that member in civil and criminal proceedings alike.
4. Silence in the group cuts both ways. Indian courts generally do NOT treat silence in a group as admission by acquiescence — do not build your case on "he read it and stayed silent." Kishor-adjacent reasoning (no liability without participation) bleeds into evidentiary weight here.

The Group Evidence Protocol: Export to Exhibit

The core protocol matches our media export guide — airplane mode, with-media export, hash, chronological PDF. These are the group-specific additions:

Phase 1 — Group-specific preservation

1. Export the full group chat with media — not a window, not a selection. Group completeness is your answer to the curation attack.
2. Snapshot the group info page (name, description, member list with numbers, member count) on the same day, and include it in your hash-covered evidence set — photograph it or export it; either way, timestamp it.
3. Record your role: member or admin, and since when. Your certificate must describe your role truthfully.
4. Note joining/leaving events visible in the export ("You were added," "X left," system messages) — these anchor group composition at each date.

Phase 2 — The participant key (mandatory for groups)

Prepare a one-page key as an annexure:

PARTICIPANT KEY — Group: "[Exact Group Name]" — Snapshot date: [DD/MM/YYYY]

| # | Sender label in export | Phone number (from export) | Identity (per affidavit) | Basis of identification |
|---|------------------------|----------------------------|--------------------------|-------------------------|
| 1 | Rohan Sharma           | +91-98XXXXXXXX (unsaved → raw number in export) | Rohan Sharma, flat 4B | Self-identification in thread; society records |
| 2 | Meera ~ Treasurer      | +91-97XXXXXXXX | Meera Iyer, Treasurer | Stated role in messages; committee minutes |
| 3 | +91-96XXXXXXXX         | +91-96XXXXXXXX | Vikram Desai | CAF direction obtained; admitted in reply notice |

This key is what transforms a wall of sender labels into attributable evidence.

Phase 3 — Hash, convert, certify

• Hash the group export ZIP and the group-info snapshot file together (place both in one evidence folder, hash the folder archive — or hash separately and record both).
• Convert to a chronological PDF with +91 numbers, participant key on page 1, media inline, pagination, exhibit header.
• Draft the group-tailored certificate (below).

Phase 4 — Filings and readiness

• File with sealed media (export ZIP + PDF + participant key + snapshot).
• Prepare testimony: your role, when you joined, how the export was taken, that messages appear as delivered to your device, the hash.
• If attribution will be contested, begin the CAF/TSP record process early — provider compliance to court directions takes weeks, and interim-relief applications can't wait for it.

Section 63 BSA Certificate Tailored for Group Chats

Adapted from our master certificate template — the group-specific limbs are marked.

CERTIFICATE UNDER SECTION 63(4) OF THE BHARATIYA SAKSHYA ADHINIYAM, 2023
[Multi-Participant WhatsApp Group — Certificate for Submission of Electronic Evidence]

I, [FULL NAME], aged ___ years, resident of [___], do hereby certify to the best of my
knowledge and belief, as follows:

1. IDENTIFICATION OF THE ELECTRONIC RECORD
   The record accompanying this certificate is a true export of the WhatsApp GROUP
   conversation titled "[EXACT GROUP NAME]" as stored on my device (mobile number
   +91-[___]), spanning messages dated [__] to [__], produced as a chronological PDF of
   [__] pages with media, together with (a) a snapshot of the group's participant
   information dated [__] and (b) a Participant Key identifying the senders ["the Record"].

2. MANNER OF PRODUCTION
   The Record was produced by me on [DATE] using WhatsApp's native "Export Chat"
   function with "Include Media" on the device described below, converted to PDF without
   alteration, addition, deletion, or reordering of any message, timestamp, sender label,
   or media item. The participant snapshot was captured on the same date.

3. MY ROLE AND PARTICIPATION  ◀ GROUP-SPECIFIC LIMB
   I am a [member / administrator] of the said group, having [joined on __ / created the
   group on __]. I certify this Record as the person in charge of the device on which
   these messages were received and stored; I do not certify on behalf of, or as to the
   devices of, other participants.

4. PARTICULARS OF THE DEVICE
   Device: [Make & Model] | OS: [Android __ / iOS __] | IMEI: [___] | Number: +91-[___]
   The device was regularly used by me over the relevant period for WhatsApp
   communications, and the information contained in the Record was supplied to it in the
   ordinary course, through the WhatsApp application and its servers, including messages
   originating from the devices of other group participants.

5. SECTION 63(2)/63(3) CONDITIONS
   (a)-(d) [As in the standard template: regular use, ordinary course, proper operation,
   true reproduction.]
   Additionally, relying on Section 63(3) BSA: the Record was produced by a system of
   networked communication devices functioning as an integrated system, and is certified
   as the output of that system as stored on my device.

6. INTEGRITY VERIFICATION
   SHA-256 hash of export ZIP (generated [DATE, TIME]): [64-char hash]
   SHA-256 hash of final PDF (generated [DATE, TIME]): [64-char hash]
   No alteration has been made to the Record since hashing.

7. DECLARATION
   Contents true to the best of my knowledge and belief; aware of liability for false
   statements.

   Verified at [City] on [__] [Month] 2026.
   [SIGNATURE] [FULL NAME] [Address, Mobile, Email]
   [Part B — Expert verification where applicable]

Comparison Matrix: One-to-One Chat vs Group Chat Evidence

Case Study: The Housing Society Group That Decided a Crore-Rupee Dispute

A composite case study based on a recurring cooperative-housing-society dispute pattern in Maharashtra courts. Names changed; mechanics exactly as described.

The dispute: A 14-member managing committee of a Pune housing society had approved major repair contracts via its WhatsApp group over 18 months — a practice never minuted formally. When a faction of owners later challenged the ₹1.1 crore repair expenditure in the Co-operative Court, the committee's entire approval trail existed only in the group chat: contractors' quotations forwarded as PDFs, cost approvals ("Approved at 4.8L, go ahead"), payment confirmations, and dissent ("Main isko approve nahi karta").

The threat: The challenging faction argued the contracts were never validly approved — no resolution, no minutes, no signatures. If the group chat was inadmissible, the committee had no defense at all.

The evidence build:

1. The secretary (a committee member, not the admin) exported the full group chat with media — 22,000 messages, done in two dated segments because of export limits, each segment hashed separately.
2. A participant key mapped every sender label to a number and identity — straightforward because committee roles were self-stated in the thread ("treasurer here, transfer done") and society records matched.
3. The group-info snapshot captured all 14 members with numbers on the export date.
4. The certificate used the group-tailored format with the role limb: the secretary certified her own device's record, expressly disclaiming certification for other members' devices.

The ambush and the answer: Opposing counsel ran the standard attacks: curation ("they removed messages" — answered by the unbroken hashed export), hearsay ("members quoting each other" — answered by filing only direct approvals and dissents as foundation, context messages separately), and attribution ("sender labels are fakeable" — answered by the participant key plus numbers appearing raw in the export for unsaved members).

The outcome: The Co-operative Court admitted the group record and held the WhatsApp approvals constituted valid committee decision-making given the society's established practice. The challenge collapsed; the full repair expenditure stood, and the committee recovered ₹6.3 lakh in costs from the losing faction.

The three transferable lessons:

1. The member's certificate is enough. The secretary — neither admin nor creator — certified her own device. Nobody needed the admin's cooperation.
2. Self-identification in-thread is gold. Members stating their own roles ("treasurer here") built attribution without a single telecom record.
3. Two segmented exports beat one truncated export. The 22,000-message history survived because it was exported in dated, separately hashed chunks — exactly the segmented strategy from our media export guide.

Cross-Examination Checklist for Group Evidence

8 Fatal Mistakes with Group Chat Evidence

Frequently Asked Questions

1. Are WhatsApp group chats admissible in Indian courts?

Yes. They are electronic records under Section 63 BSA 2023, admissible with a certificate, hash, and proper attribution — per the framework confirmed in Ambalal Sarabhai (SC) and Arjun Panditrao Khotkar (SC 2020).

2. Can I be arrested just for being a WhatsApp group admin?

No — not for members' content. Per Kishor v. State of Maharashtra (Bom HC 2021), an admin is not vicariously liable absent proof of common intention or a pre-arranged plan. Your own posts, however, are your own liability.

3. Who signs the Section 63 BSA certificate for a group chat?

Any member whose device stored the messages — typically you. The certifier must be the person in charge of the device, not the group creator or admin.

4. How do I prove a message came from a specific person in a group?

Layered attribution: sender label → raw +91 number in the export → SIM registration (CAF) or billing records → corroboration (self-identification in-thread, documents). The participant key organizes all of it for the court.

5. What if the person I'm claiming against left the group?

Messages sent while they were a member remain their admissions. System messages ("X left") in the export establish their membership period; their messages within that window are attributable.

6. Can I use a group chat where people discussed me without tagging me?

Context messages are usable for context. For claims against specific people, you still need their own statements or legally recognized exceptions. Discussing you is not automatically an admission by each member.

7. Do I need the admin's permission or cooperation to use group evidence?

No. Your device's record is yours to export and certify. Admin cooperation is irrelevant to Section 63(4) certification.

8. What if members used changed numbers or secondary SIMs?

This is an attribution challenge, not an admissibility bar. CAF records identify SIM holders regardless of which phone held the SIM; IMEI-level device forensics is the escalation route for seriously contested attribution.

9. Can group chats be used in criminal cases, or only civil?

Both. Group messages support criminal complaints (defamation, criminal intimidation, cheating) and civil claims. The certification and attribution protocol is the same; the prosecution/police can additionally compel provider records.

10. How do I prepare group evidence if litigation is likely but not filed yet?

Airplane mode → export full group chat with media (segmented if long) → group-info snapshot → hash everything → email hashes to yourself and a third party → convert to chronological PDF with participant key and certificate. Do it now; group evidence degrades faster than any other kind.

Conclusion & Action Plan

Group chats are where Indian disputes increasingly live — committee decisions, family negotiations, business coordination, threats, admissions. The law now has clear answers for them: Ambalal Sarabhai admits them, Arjun Panditrao certifies them, Kishor calibrates admin liability, and number-based attribution binds messages to people. What decides cases is not the law's uncertainty but the litigant's preparation.

Your action plan:

• Today (25 minutes): For any active dispute in a group: airplane mode → full with-media export (segmented if long) → group-info snapshot → hash everything → email hashes to yourself and a trusted person.
• This week: Build the participant key. Identify every sender you may claim against; collect number-linkage documents (self-identification messages, invoices, society/company records).
• Before filing: Convert to chronological PDF with participant key on page 1, draft the group-tailored Section 63 BSA certificate (role limb included), prepare sealed media.
• Strategic check: Are you targeting senders (correct) or the admin (usually a dead end post-Kishor)? Are your foundation messages direct admissions (not hearsay)?

Your three options

Related Guides

• How to Authenticate WhatsApp Screenshots for Court Submission — the master authentication protocol
• Export WhatsApp Chat Media for Court Evidence — media export, truncation limits, hashing
• Are WhatsApp Chats Valid in Court in India? — the full admissibility framework
• WhatsApp Audio Transcripts & Voice Notes under Section 63 BSA — voice notes in group threads

Disclaimer: This guide is legal information, not legal advice, and does not create an advocate-client relationship. Statutes and case law are stated as of September 2026. Consult a qualified advocate for your specific matter.