The Reliance-Facebook Leak Case: What SEBI's Final Word on Market Rumours Means for Compliance Officers

Primary source: SEBI, Adjudication Order in the matter of Reliance Industries Limited, Ms. Savithri Parekh and Shri K. Sethuraman, dated 20 June 2022 (order PDF) — upheld by SAT, Mumbai on 2 May 2025, and by the Supreme Court on 2 December 2025.

Why this matters

Every listed company eventually faces the same scenario: a deal that isn't signed yet, a term sheet that hasn't been approved by the board, and a newspaper report that somehow already knows the broad shape of it. The instinctive reaction of many compliance teams is to say nothing until there is something "final" to announce. The Reliance Industries–Facebook/Jio Platforms case — now finally settled after passing through SEBI, SAT, and the Supreme Court — tells you that instinct is wrong, and has been wrong since at least the 2015 PIT Regulations' fair disclosure code came into force.

This case has been working its way through the system for years, but it only reached finality recently: SAT dismissed RIL's appeal on 2 May 2025, and the Supreme Court — a bench of the Chief Justice and Justice Joymalya Bagchi — refused to interfere on 2 December 2025, holding there was no substantial question of law. With the litigation now closed at every level, the underlying SEBI reasoning is settled law that every designated person and compliance officer handling deal-stage UPSI should build into their playbook.

The facts: a slow-moving deal, a fast-moving leak

RIL's discussions with Facebook Inc. about an investment in Jio Platforms Limited (JPL) began on 1 September 2019 and were entered into RIL's structured digital database just nine days later. Over the following months, RIL and Facebook exchanged term sheets, conducted management meetings, and ran due diligence — all properly treated as UPSI internally.

On 24 March 2020, the Financial Times, London, reported that Facebook was in advanced talks to buy a stake in Jio worth several billion dollars. Indian media picked up the story immediately. RIL's share price rose 2.16% the next trading session and then surged a further 14.72% intraday — by SEBI's own finding, unambiguous proof the market considered the news price-sensitive. RIL did not issue any clarification to the exchanges at that point. The final valuation (₹43,574 crore for a 9.99% stake) wasn't agreed until 29 March 2020; board approvals came on 18 April; transaction documents were signed on 21 April in the US; and RIL finally informed the exchanges on 22 April 2020 — 28 days after the Financial Times report broke, and roughly a month after the market had already priced in a chunk of the deal.

SEBI's Adjudicating Officer found RIL, its Company Secretary (Ms. Savithri Parekh) and its Group CFO (Mr. K. Sethuraman) in violation of Principle 4 of Schedule A to the PIT Regulations — the Code of Practices and Procedures for Fair Disclosure of UPSI — and imposed a joint penalty of ₹30 lakh.

What SEBI clarifies: "credible and concrete" is not a shield once a leak happens

RIL's central defence was a harmonious-construction argument: Principle 1 of Schedule A only requires disclosure once information is "credible and concrete," and as of the Financial Times report, the deal's valuation and structure were still being negotiated — so, RIL argued, there was nothing concrete yet to disclose, and Principle 4's "prompt dissemination" obligation couldn't have been triggered.

SEBI rejected this. The Adjudicating Officer found that by the time the story broke, RIL's own chronology showed the deal was already well past the exploratory stage — a signed NDA, months of due diligence, a term sheet, and named advisors on both sides. That combination, plus the market's own emphatic price reaction, was enough to establish that credible, price-sensitive information about the deal had reached the public domain through the leak — regardless of whether every commercial term was locked down. Once that selective (if inadvertent) disclosure occurred, Principle 4 obligated RIL to promptly make the substance of the deal generally available, rather than wait for finality on price and structure.

What SEBI intends: the fair disclosure code is built to close the gap between what insiders and their counterparties already know and what the market knows, at the moment that gap starts being exploited — not at the moment a company finds it administratively convenient to announce. Letting a company wait for "finality" before responding to a market-moving leak would hand every listed company a ready-made excuse to stay silent through the entire window in which informed insiders (and anyone who received the leak) could trade on an information advantage.

Practical takeaway: Don't calibrate your disclosure trigger to deal completeness. The trigger is: (a) has UPSI escaped into the market, however imperfectly or informally, and (b) is the market treating it as price-sensitive? If both are yes, silence is not a defensible option merely because the transaction has open points.

From "may" to "must": Regulation 30(11) has hardened since this case arose

At the time of RIL's leak in 2020, the relevant LODR provision — Regulation 30(11) — only said a listed entity "may on its own initiative" confirm or deny a reported event. SEBI's order in effect read a mandatory duty into the PIT fair-disclosure principles even though the parallel LODR provision was still framed as optional. Compliance officers should note that this gap has since been closed directly: SEBI's 2023–24 amendments to Regulation 30(11) made confirmation, denial, or clarification of market rumours affecting price mandatory (not merely permissive) for large listed entities — now in force for the top 100 listed companies by market capitalisation from 1 June 2024, and the top 250 from 1 December 2024.

What SEBI intends: the RIL case shows SEBI was already treating "confirm or deny" as a practical necessity under the fair-disclosure principles well before it made the obligation explicit and mandatory in the listing regulations. The 2023–24 LODR amendment removes any residual argument — available to RIL in 2020 — that responding to rumours was discretionary. For the companies now covered by the mandatory regime, the RIL reasoning on what counts as a market-moving "leak" requiring a response is directly relevant to how quickly and on what trigger they must act.

The compliance officer's personal exposure

A detail worth flagging for company secretaries specifically: SEBI didn't confine the penalty to the listed entity. It held RIL's Company Secretary and Group CFO jointly and severally liable alongside the company for the fair-disclosure lapse. The order treated the compliance function's role in monitoring media coverage and escalating a response as a personal, not merely corporate, obligation.

Practical takeaway: Media and social-media monitoring for rumours touching your company's UPSI should be a documented, active function of the compliance office — not something that happens only when a director calls in reacting to a stock price move. Build an internal escalation SOP (who monitors, who verifies against the SDD, who authorises the exchange filing, and within what number of hours) and be able to show it was followed the next time a leak occurs.

Bottom line for your compliance checklist

• Treat a credible media report about a live UPSI matter as a trigger for immediate internal escalation, not as something to be addressed once the deal is signed.
• Don't rely on "the terms aren't final yet" as a reason to stay silent — SEBI assesses whether the market is already treating the leaked information as price-sensitive, not whether your term sheet is complete.
• If your company is among the top 100 or top 250 listed entities by market capitalisation, confirm you have a documented process to meet the now-mandatory Regulation 30(11) rumour-verification timelines.
• Ensure your escalation SOP names specific individuals and timeframes for monitoring, verifying against the structured digital database, and authorising a stock-exchange clarification — and keep records showing it was actually followed.
• Remember that compliance officers and CFOs can be held personally, jointly and severally liable for a company's fair-disclosure failures — this is not a risk that stops at the corporate veil.

This post is an interpretation of publicly available SEBI, SAT, and Supreme Court materials for general informational purposes and does not constitute legal advice. Readers should verify details against the original orders and SEBI's website and consult a qualified professional before acting on any point discussed here.