TL;DR: An ordinary WhatsApp or Telegram group admin is almost never an “intermediary” under the IT Act, so section 79 safe harbour rarely helps them and rarely needs to. Naming a person who has been accused of a crime is not, by itself, an offence in India. The way it is done often is, through defamation, criminal intimidation or a privacy violation, and three categories are an absolute bar regardless of intent: a rape victim’s identity, a child victim’s identity under POCSO, and a juvenile in conflict with law’s identity. If you moderate a group, remove the post, preserve a copy first, and say why in the group. If you were the one named, you have real remedies, and the presumption of innocence protects you in a courtroom, not on a phone screen.
On this page
- The scenario
- Is a group admin an intermediary at all
- Section 79 safe harbour and why it barely reaches you
- What courts have actually said about admin liability
- When knowledge plus inaction becomes complicity
- The offences actually in play
- The three rules that override everything else
- Naming an accused is not the offence, the method usually is
- The dpdp act angle and its journalistic purpose gap
- The takedown ladder
- Preserve evidence before you delete anything
- What to actually write in the group
- Decision table: what was posted, and what it means for you
- Frequently asked questions
The scenario
A member of your WhatsApp group, Telegram channel, subreddit, Discord server or Instagram page names someone who has been accused of a crime. Not just named, doxxed: full name, a photo, a home address, a workplace, a phone number, sometimes a family member’s details too. The post is meant to warn people, or to shame the person, or both.
If you run the group, you now have two live questions. Are you personally exposed for something a member posted. And what are you actually required to do about it.
If you are the person who got doxxed, you have a separate and more urgent problem: your address and your employer are now public, whether or not you are eventually convicted of anything, and the presumption of innocence that protects you in a courtroom does nothing to stop the post from spreading.
This is close to the exact fact pattern that surfaced on r/LegalAdviceIndia in mid August 2026, where a group participant asked what happens legally when a member posts an accused person’s identifying details inside a group. It is a common enough situation that it deserves a straight answer for both sides, moderator and accused, rather than the vague “you could get in trouble” that circulates in most group chats after an incident like this. The single most common venue for this exact fact pattern is a housing society WhatsApp group after an alleged theft or altercation, the same group that usually doubles as the forum for maintenance and audit trail disputes, so a lot of the same admins end up moderating both kinds of conflict.
Everything below is India specific. It uses the Bharatiya Nyaya Sanhita, 2023 (BNS), the Bharatiya Nagarik Suraksha Sanhita, 2023 (BNSS) and the Bharatiya Sakshya Adhiniyam, 2023 (BSA) as the primary criminal and evidence law, with the IPC, CrPC and Evidence Act equivalents given the first time each provision appears. For the fuller context on how the recodification works, see the BNS-IPC section mapping and whether IPC-era precedents still apply under BNS.
Is a group admin an intermediary at all
Start here, because most of the anxiety in these threads comes from a category error. People assume a group admin is something like a mini Facebook, regulated the same way, protected the same way. Usually they are not.
Section 2(1)(w) of the Information Technology Act, 2000 defines an intermediary as a person who, on behalf of another person, receives, stores or transmits an electronic record, or provides a service with respect to that record. That definition was built for platforms: telecom operators, network service providers, web hosts, search engines, marketplaces, social media companies. It describes WhatsApp, Telegram, Meta, Reddit and Discord as the operating companies. It does not naturally describe you, an individual who created a group on someone else’s platform and occasionally deletes a message.
Courts asked to decide this directly have generally declined to treat an ordinary admin as an intermediary, and separately declined to treat an admin as vicariously liable for a member’s post the way an employer is liable for an employee’s conduct, because there is no master-servant or principal-agent relationship between an admin and the people in the group. An admin who did not write, edit or specifically approve the offending message is, in the ordinary case, not standing in the platform’s shoes and is not standing in the poster’s shoes either. Your liability, if any, comes from your own conduct after the post appears, not from the platform-style intermediary framework.
Where this gets more complicated is if you run something that functions more like a publication than a private group: a large public Telegram channel you actively curate and repost into, a subreddit where you write the sidebar rules and personally amplify content, or a page where you are the one posting, not merely allowing others to post. The closer your role moves from “person who created a group” to “person who selects and pushes out content,” the closer you move toward being treated as the author or publisher of what appears, and the intermediary analysis stops being the right frame entirely.
Section 79 safe harbour and why it barely reaches you
Section 79 of the IT Act gives an intermediary immunity from liability for third-party content it merely hosts or transmits, provided it meets the due diligence conditions in the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021. That immunity is real and important, but it is built for the platform operator, not for you as a group creator.
The 2021 Rules require, among other things, that the intermediary publish rules and a privacy policy, inform users what content is prohibited, appoint a Grievance Officer, and act on court orders or government notices to remove unlawful content within specified timelines. WhatsApp, Meta and Reddit carry these obligations. An individual admin does not run a Grievance Officer desk and does not need to, because you are not the intermediary the Rules are regulating.
Practically, this means two things at once. First, you should not comfort yourself with “safe harbour protects me,” because section 79 is not really the shield in this situation, it protects the platform, not you personally. Second, you should not panic that you have somehow lost a protection you never had, because in the ordinary admin scenario your exposure was never governed by section 79 in the first place. Your exposure, if it exists, comes from ordinary criminal and civil law applied to your own acts: what you posted yourself, what you specifically approved, and what you knowingly allowed to continue after you had actual notice.
What courts have actually said about admin liability
The most cited ruling on this point is the Delhi High Court’s decision in Ashish Bhalla v. Suresh Chawdhary, where the court held that a group administrator cannot be held liable for a defamatory statement posted by a group member. The court’s comparison was blunt: holding the admin liable for a member’s post would be like holding the manufacturer of newsprint liable for a defamatory article printed on it. A group is a platform for conversation, and a member can post something objectionable without the admin’s knowledge, review or approval before it goes out. Absent a specific statute creating vicarious liability for admins, none exists by default.
The Kerala High Court has reached a broadly similar position when examining whether a WhatsApp group creator or admin should face criminal liability for offensive content posted by a member, again resisting the idea that admin status alone creates liability for everything that happens in the group.
On the narrower question of when an admin’s own liability actually attaches, one practitioner summary of this case law states it plainly: “Liability can only be attached if a ‘common intention’ or ‘pre-arranged plan’ between the admin and the member is proven” (eVaakil, evaakil.com, reviewed 19 August 2026). That is a meaningfully higher bar than mere knowledge. Common intention, as Indian criminal law has always used the term, requires evidence of a shared plan between the admin and the poster, not just the fact that the admin saw the post and was slow to remove it.
None of this makes an admin bulletproof. It establishes a starting point: creating or running a group is not itself the wrongful act, and a member’s post is not automatically imputed to you. What can change that outcome is what you did once you knew.
When knowledge plus inaction becomes complicity
The line that actually matters is not “who is an intermediary.” It is knowledge plus continued availability of the content.
If a member posts doxxing content and you, as admin, are unaware of it, you are in the position the case law above describes: a passive host of a conversation you did not curate line by line. If you see the post, understand what it is, and leave it up, particularly after someone flags it to you or after it becomes obviously connected to threats, harassment or intimidation of the named person, your position changes. Continuing to allow access to content you know is unlawful, especially where it exposes someone to physical risk, moves you from bystander toward participant. Depending on the facts, that can support an abetment analysis or, in an extreme case involving a fresh instance of criminal intimidation building on the doxx, complicity.
The safest reading of Indian law here is conservative: your liability risk rises sharply the moment you have actual knowledge and choose to do nothing, and falls sharply the moment you act, remove the post, and document that you acted. There is no fixed rulebook stating how many hours of delay converts a passive admin into a liable one. Treat “as soon as you become aware” as the only safe standard, not “when it becomes convenient” or “when someone threatens to report the group.”
The offences actually in play
Set the intermediary question aside for a moment. What has the poster, not the admin, actually exposed themselves to under the new criminal codes.
Defamation. BNS section 356 (the successor to IPC sections 499 and 500, now merged into one provision) punishes harming a person’s reputation through words, signs or visible representations, with up to two years’ imprisonment or a fine or both. It is non-cognizable and bailable, and it carries the same public interest and good faith exceptions IPC 499 always had. Naming someone as an accused, if the accusation is true and reported without embellishment, sits closer to those exceptions. Adding a fabricated detail, exaggerating the charge, or implying guilt the FIR does not support, moves it further from them. See defamation law in India for the full exceptions and how truth interacts with public interest.
Criminal intimidation. BNS section 351 (replacing IPC sections 503, 506 and 507) covers threats of injury made to cause alarm or to compel a person to act against their will. Doxxing that comes with, or invites, threats such as “here is where he lives, someone should teach him a lesson” sits squarely inside this provision, and the person who posted the threat, not just the address, is the one exposed.
Privacy and image based offences. Section 66E of the IT Act punishes capturing, publishing or transmitting the image of a person’s private area without consent, which is narrower than general doxxing but relevant where a photo used was taken in circumstances that violated privacy. Where the doxxer got the photo or contact details off a compromised phone or account rather than a public source, that is a separate and serious problem in its own right, covered in what to do when your digital identity is locked out after a lost device. More broadly, publishing someone’s home address and phone number alongside an accusation, with the practical effect of enabling harassment, tends to be prosecuted through the intimidation and stalking provisions rather than a standalone “privacy” offence, because Indian criminal law does not yet have a dedicated doxxing statute. BNS section 78 (stalking) can apply where the disclosure is paired with monitoring, repeated contact attempts, or following, whether online or offline.
Cyberstalking and harassment via the IT Act. Where the conduct is organised, repeated, or coordinated across a group with the effect of harassing the accused, section 66A of the old IT Act is gone (struck down in Shreya Singhal), but the criminal intimidation and stalking provisions above, applied to electronic communication, cover most of the same ground without the free speech problem that section 66A had.
None of these require an “anti doxxing law” to exist as such. India does not have one. What exists is a set of provisions that, applied to the specific way information is used once it is posted, usually reaches the harmful conduct anyway.
The three rules that override everything else
Three categories of disclosure are not judged on manner, intent or public interest at all. They are flatly prohibited, and they sit above every other consideration in this article.
Rape victims. BNS section 72 (the direct successor to IPC section 228A) makes it an offence to print or publish the name of a person against whom certain sexual offences, including rape, are alleged or have been found to have been committed, or any matter that would make her identity known to the public. This applies to victims, not to accused persons, and it applies regardless of whether the accusation is later proven true. If a group post about an accused also identifies the complainant in a sexual offence case, even in passing, that identification is independently and separately unlawful no matter what else is true about the post.
Child victims under POCSO. Section 23 of the Protection of Children from Sexual Offences Act, 2012 bars any report or comment on a POCSO case that discloses the identity of the child, whether through name, photograph, family details, school, neighbourhood, or any other particular that could lead to identification, and it applies to media and to individuals making such disclosures. Violation carries a minimum of six months’ imprisonment, extendable to one year, with or without fine. The Special Court alone can permit disclosure where it finds that doing so serves the child’s interest.
Juveniles in conflict with law. Section 74 of the Juvenile Justice (Care and Protection of Children) Act, 2015 bars disclosure in any newspaper, magazine, news sheet, audio visual media, or online platform of the name, address, school or any particular that could identify a child in conflict with law, a child in need of care and protection, or a child victim or witness, and bars publishing the child’s picture. Violation carries imprisonment up to six months, a fine up to two lakh rupees, or both.
If your group’s post names or identifies a minor, whether as the accused or as a victim or witness, or identifies a rape complainant in any way, the “is the poster protected because they were only naming the accused” question stops mattering. These three bars apply on top of, and independent of, everything else in this article, and they are among the very few genuinely strict, near absolute rules in Indian speech law.
Naming an accused is not the offence, the method usually is
This is the point that gets lost in most group chat arguments, so it is worth stating plainly. Naming a person who has been accused of a crime is not, by itself, illegal in India. FIRs are public documents in most cases, court proceedings are open, and reporting that a named person has been accused, arrested or charged is something newspapers and news channels do every day without committing an offence, provided the reporting is accurate and does not fall into one of the three absolute bars above.
The presumption of innocence, the principle that a person is innocent until proven guilty, is a rule that governs how a court must treat an accused during trial. It is not a rule that bars the public, or a WhatsApp group, from discussing a pending case or naming who has been accused in it. A journalist naming an arrested person the day after an FIR is filed is not violating the presumption of innocence, because the presumption operates inside the courtroom, on the prosecution’s burden of proof, not as a gag on public conversation.
What turns a lawful “here is who has been accused of X” into something that exposes the poster is usually one of a small number of things layered on top: adding unverified or fabricated detail, presenting an accusation as an established fact of guilt, including private information (home address, workplace, family members’ names) that serves no informational purpose and mainly enables people to show up at the person’s door, or accompanying the post with language that reads as an invitation to threaten or harm. Strip those additions out and what is left, “this named person has been accused of this offence, here is the case number,” is usually lawful. Leave them in and the poster has moved from reporting into defamation or intimidation territory, sometimes both.
The dpdp act angle and its journalistic purpose gap
The Digital Personal Data Protection Act, 2023 adds a separate layer that is easy to miss because it is a data protection statute, not a criminal one, and its remedies run through the Data Protection Board rather than a police station. See the DPDP Rules 2025 and the compliance deadlines running into 2026-27 for the wider rollout picture.
The Act’s threshold exclusion matters here first. Section 3(c)(ii) takes personal data that the data principal has themselves made publicly available outside the Act’s scope entirely. That does not usually help a doxxer, because the accused did not make their home address or phone number public, someone else dug it up or already had it and posted it without consent.
Where the DPDP Act gets genuinely awkward is that, unlike several comparable privacy statutes elsewhere, it does not carry a dedicated exemption for processing personal data for journalistic purposes. The Act exempts research, archiving and statistical processing under section 17(2)(b), and it exempts data a person has themselves made public, but a bare journalistic purpose carve out is conspicuously absent, a gap the Editors Guild of India and others have flagged since the Act was passed. Practically, this means a group admin or a would be citizen journalist cannot point to a clean “I was reporting the news” exemption under the DPDP Act the way a registered media house might argue under other frameworks. It does not, by itself, create a criminal case, the DPDP Act’s enforcement mechanism runs through financial penalties imposed by the Data Protection Board on a complaint, not through a police FIR, but it is a live compliance gap that anyone running a channel with a genuine reporting function should know exists rather than assume is covered.
The takedown ladder
If you are the accused, the group admin, or someone advising either, work through these in order. Do not skip straight to the last rung.
- Report to the platform first. WhatsApp, Telegram, Instagram and Reddit each have an in-app report function for harassment, doxxing or personal information disclosure. This is the fastest route and does not require any legal filing.
- Ask the group admin to remove it directly. If you are not the admin, message them. Most removals happen at this stage, and it costs nothing.
- File a complaint with the platform’s Grievance Officer under the 2021 Rules. Every significant social media intermediary must publish a Grievance Officer’s contact details. The Grievance Officer must acknowledge your complaint within 24 hours and dispose of it within 15 days from receipt (Rule 3(2), Intermediary Guidelines 2021, reviewed 19 August 2026). Keep your complaint reference number.
- Escalate to the Grievance Appellate Committee if the platform’s response is inadequate or absent. The GAC, established under the amended 2021 Rules, hears appeals against a Grievance Officer’s decision, or against the platform’s failure to respond, within 30 days of that decision or of the 30 day non-response window lapsing. It is an entirely online process (gac.gov.in, reviewed 19 August 2026), and it endeavours to resolve appeals within 30 days of filing, though the Delhi High Court has separately directed the GAC to dispose of appeals within that same 30 day window where it has been slow.
- Send a section 79(3)(b) notice. This is the formal statutory mechanism: on receiving actual knowledge, by a court order or by notification from the appropriate government agency, that content is unlawful, an intermediary must remove or disable access to it, failing which it loses safe harbour for that content going forward. A well drafted notice citing section 79(3)(b), sent to the platform, forces this obligation into the open.
- Get a court order where the platform will not act. A civil suit for an injunction, or a criminal complaint that results in a court directing takedown, compels removal in a way an in app report cannot. This is also the route for a John Doe (Ashok Kumar) order, an injunction against unnamed, unidentified persons, used where content is being reposted faster than individual takedowns can keep pace, common in doxxing pile ons that spread across multiple groups and reposts.
- File at cybercrime.gov.in for the criminal law side. The national cybercrime reporting portal (cybercrime.gov.in, reviewed 19 August 2026) accepts complaints for cyberstalking, harassment and privacy violations, and routes them to the relevant state cybercrime cell. This runs in parallel with, not instead of, the platform escalation above. See filing a cybercrime complaint in India for the full walkthrough, and how zero FIR and e-FIR work under BNSS if you want to file at a police station outside your jurisdiction because that is where you can get to first. If the local station refuses to register your complaint, police refusing to register an FIR has a defined remedy, and BNSS section 173 sets out when registration is mandatory, discussed in the BNSS section 173 FIR registration guide.
| Step | Where you send it | Legal basis | Their deadline to act | If they ignore it |
|---|---|---|---|---|
| Platform report | In app report tool (WhatsApp, Telegram, Instagram, Reddit) | Platform community guidelines, not a statute | No fixed deadline | Escalate to the Grievance Officer |
| Grievance Officer complaint | The intermediary’s published Grievance Officer contact | Rule 3(2), Intermediary Guidelines 2021 | Acknowledge within 24 hours, resolve within 15 days | Escalate to the Grievance Appellate Committee |
| Grievance Appellate Committee appeal | gac.gov.in, filed online | Rule 3A, Intermediary Guidelines 2021 as amended | Endeavours to resolve within 30 days of the appeal | Send a section 79(3)(b) notice or move court |
| Section 79(3)(b) notice | Directly to the intermediary, citing actual knowledge of unlawful content | Section 79(3)(b), IT Act 2000 | No fixed statutory deadline, but delay risks the platform’s own safe harbour | Platform loses safe harbour for that content, strengthening a case against it too |
| Court order or John Doe injunction | Civil or criminal court with jurisdiction | CPC injunction powers, BNSS, inherent powers of the court | Set by the court, often urgent ex parte relief | Non-compliance risks contempt of court proceedings |
| cybercrime.gov.in complaint | National Cyber Crime Reporting Portal | BNS sections 351 and 356, IT Act provisions | Routed to the state cybercrime cell, no fixed statutory deadline | Follow up with an FIR at the local station |
You do not have to exhaust every rung before the content comes down. Most doxxing posts get removed at rungs one to three. Keep escalating only if they do not.
Preserve evidence before you delete anything
The instinct on seeing a doxxing post is to delete it immediately. Do that, but not before you have preserved a record, because the deleted message is also your evidence if the accused wants to pursue a defamation suit, a criminal complaint, or a DPDP Board complaint later. Preserving evidence properly before you call a lawyer covers the same capture-before-delete discipline in more general terms and is worth reading before you touch the post at all.
Before removing anything: take a full screenshot of the message including the sender’s visible name or number and the timestamp, note the group name and the approximate member count, save the group’s export chat function output if the platform offers one, and record who else reacted to or forwarded the message if that is visible to you. Under the Bharatiya Sakshya Adhiniyam, 2023, electronic records including screenshots and chat exports are admissible subject to the section 63 certification requirement (the BSA’s version of the old Evidence Act section 65B certificate), covered in detail in BSA section 63 and electronic evidence. A screenshot without a proper certificate is weaker evidence than one taken and certified correctly at the time, so if you expect this to end up in a complaint, do the certification step rather than relying on the screenshot alone.
If you are the accused and you are asking a lawyer to send a legal notice or file a complaint, hand over the preserved material, not just a description of it. How to draft a legal notice and, if you are on the receiving end of one instead, how to reply to a legal notice in India cover the mechanics of that exchange. If you are the admin and what actually lands in your inbox is a police notice rather than a lawyer’s letter, legal notice, police notice, and summons: how they differ explains how to triage which one you have and what it actually requires of you.
What to actually write in the group
Admins consistently under communicate at exactly the moment clear communication matters most. A short, firm message, sent as soon as you act, does more legal and practical work than a long one sent a day later.
A workable template: “A message in this group named a specific person and included their address and phone number. I have removed it. This group will not be used to share the personal details, address, workplace or phone number of anyone, including someone who has been accused of an offence. Discuss the case, not the person’s private information. Repeated violations will result in removal from the group.”
This does three things. It documents, on the record and inside the group, that you acted promptly once you knew. It sets a standing rule going forward, which matters if the same thing happens again and you need to show you were not indifferent. And it does not attempt to argue the underlying case, admitted guilt, or an accusation being false, none of which is the admin’s role to adjudicate.
Decision table: what was posted, and what it means for you
| What was posted | Must you remove it | Your exposure if you leave it up |
|---|---|---|
| Accused’s name plus the fact of the FIR or charge, accurately stated | ✗ (not required on legality grounds, though group norms may still call for it) | Low. This is ordinary reporting of a public fact. |
| Accused’s home address or workplace, alongside the accusation | ✓ | Rising. Enables physical confrontation, feeds intimidation and stalking exposure for the poster, and for you once you have knowledge. |
| Accused’s phone number, inviting people to “call and ask him” | ✓ | High. Directly enables harassment; sits close to abetment once you know and allow it to continue. |
| A rape complainant’s name or any identifying detail, in any context | ✓, immediately | Severe. BNS section 72 is an absolute bar; there is no public interest defence. |
| A minor’s identity as accused, victim or witness in any case | ✓, immediately | Severe. JJ Act section 74 and, where sexual offence related, POCSO section 23 apply regardless of intent. |
| Fabricated or exaggerated detail presented as established fact | ✓ | High. Straightforward defamation exposure for the poster under BNS section 356. |
| A threat of harm directed at the accused, riding on the doxx | ✓, immediately | Severe. Criminal intimidation under BNS section 351, a distinct and serious offence from the doxx itself. |
Frequently asked questions
Can a WhatsApp or Telegram group admin be arrested for what a member posted?
Not automatically, and Indian courts including the Delhi High Court have specifically rejected the idea of default vicarious liability for admins. Your risk rises sharply if you had actual knowledge of unlawful content and left it up, particularly content that identifies a rape victim or a minor, or that pairs a doxx with a threat.
Is it illegal to name someone as an accused in a criminal case?
No. FIRs and court filings are generally public, and reporting that a named person has been accused, arrested or charged is lawful when accurate. What creates exposure is adding fabricated detail, presenting an accusation as established guilt, publishing unrelated private information like a home address, or pairing the post with language that invites harassment.
Does the presumption of innocence stop people from discussing a pending case?
No. The presumption of innocence governs how a court treats an accused during trial, particularly the burden of proof on the prosecution. It is not a restriction on public discussion, journalism or group chat conversation about a pending case.
What is section 79(3)(b) of the IT Act and when should I use it?
It is the provision under which an intermediary loses its safe harbour for specific content if it fails to remove that content after receiving actual knowledge, through a court order or a notification from the appropriate government agency, that the content is unlawful. Use it as a formal escalation once an informal report to the platform has not produced action.
How long does a platform’s Grievance Officer have to act on a complaint?
Under the Intermediary Guidelines 2021, the Grievance Officer must acknowledge your complaint within 24 hours and resolve it within 15 days from the date of receipt (reviewed 19 August 2026). If that does not happen, you can appeal to the Grievance Appellate Committee.
Is disclosing a rape victim’s identity ever legal?
Only with the victim’s own written consent in specific circumstances recognised by law, or a court’s specific direction, generally exercised in favour of the victim’s interest, not the public’s curiosity. BNS section 72, the successor to IPC section 228A, treats this as one of the very few near absolute prohibitions in Indian speech law.
What if the accused later turns out to have been falsely named?
The person who posted the false accusation faces defamation exposure under BNS section 356, and, depending on the facts, a civil suit for damages. If the police were misled into acting on the accusation, quashing routes exist too, and the underlying question of whether the case can even proceed against a wrongly accused person often ends up argued through the FIR itself, which is why FIR quashing orders must state the actual allegations is worth reading if that is your situation.
Can the accused sue the person who doxxed them?
Yes. A civil suit for defamation and, separately, for the tort of invasion of privacy, is available, alongside the criminal route under BNS sections 356 and 351 where the facts support it. Where the content keeps spreading across multiple accounts faster than individual complaints can reach them, a John Doe order against unnamed persons is the mechanism courts have used to get ahead of a pile on.
Does the DPDP Act 2023 help someone who has been doxxed?
Partially. If the doxxer used information the accused had not themselves made public, the DPDP Act’s exclusion for self published data does not protect the doxxer, and a complaint to the Data Protection Board is a parallel avenue to the criminal route. It runs on its own timeline and produces financial penalties, not arrests, so treat it as an addition to, not a substitute for, the criminal complaint.
Should I check whether the precedent on admin liability is still good law before relying on it?
Yes, particularly in a fast moving area where BNS has replaced the underlying IPC provisions the older admin liability cases were decided under. Checking whether a precedent is still good law before you or your lawyer cite Ashish Bhalla or the Kerala High Court ruling in a filing is a five minute step worth taking, and a tool like Niyam, built to verify a judgment’s current standing against the reported case law rather than assume it still holds, is a faster way to do that check than searching manually.
My group has thousands of members and I cannot review every post in real time. Does that change my liability?
It strengthens your position, not weakens it. Courts have accepted that an admin cannot pre screen every message in a large or fast moving group, which supports the “not liable by default” position. It does not excuse inaction once a specific post is flagged to you directly. At that point the group’s size stops being a defence and prompt removal becomes the only thing that matters.
If the case eventually settles or the charges are dropped, does the earlier post become retroactively illegal?
No. Legality is assessed at the time of posting and on the content posted, not on the eventual outcome of the case. An accurate report of an accusation that was true at the time remains lawful even if charges are later dropped, though continuing to circulate old, resolved accusations after the outcome is known can itself raise fresh defamation questions if it misleadingly implies an unresolved or ongoing matter. Checking whether the underlying case is still active, rather than relying on old screenshots, is where finding similar or updated judgments on a case’s current status earns its keep before anyone repeats an old claim as current fact.