What DoT reportedly clarified
On 16 November 2026, MediaNama reported that the Department of Telecommunications (DoT) has clarified what "continuous" SIM binding means for messaging apps: they should check for a user's SIM card every 24 hours. The report rests on an anonymous industry source, not a published DoT document, and MediaNama notes it is unclear when the clarification was issued. Treat the 24-hour figure as reported, not as a verified text.
The obligation itself dates to 28 November 2025. Trilegal's quarterly review records that DoT then directed app-based communication services to "continuously link these services to the SIM card installed in the device." That order did not define "continuous" or say how often apps must check. The compliance deadline has since been pushed to 31 December 2026, according to tele.net.
The strongest case for the rule
The regulator's logic deserves a fair hearing. Much Indian cyber-fraud runs through accounts registered on an Indian SIM and then operated from elsewhere, so the registered number stops being evidence of who is using the account. A rule that ties an account to the SIM that created it targets that gap directly. A fixed interval is also easier to audit than the undefined word "continuous," which gave neither regulators nor companies anything to measure against. Putting a number on the duty is, on its face, a move toward clarity.
The legal footing is thinner than the headline suggests
The Telecommunications (Telecom Cyber Security) Rules, 2024 were notified on 21 November 2024 as G.S.R. 720(E) under section 22 of the Telecommunications Act, 2023. Rule 4(3) requires every telecommunication entity to comply with directions, "including timelines for their implementation," that the Central Government issues to prevent misuse of telecommunication identifiers. Rule 9 says violations are dealt with under the Act's provisions.
The 2025 amendment, notified on 22 October 2025 according to AZB Partners, extended obligations to "telecommunication identifier user entities" (TIUEs). AZB paraphrases the definition as any person other than a licensee or authorised entity that uses telecom identifiers to identify users or deliver services. That is how a messaging app ends up inside a telecom cyber-security rulebook.
The practical consequence is that the 24-hour interval sits in a direction and a clarification, not in the rule text. The amended rules set a framework, and the operative detail travels through executive directions. A requirement this consequential for product design, whose compliance burden varies by operating system, is exactly the kind that benefits from notice-and-comment. Even the existence of the clarification is, for now, known from a leak.
The technical problem: apps cannot read the SIM
MediaNama's reporting quotes the industry argument that third-party apps "do not independently control access to SIM information." Parag Kar, quoted in December 2025, put it more bluntly: iOS does not expose these identifiers at all, and modern Android restricts third-party access, so continuous validation is "technically infeasible" without OS-level support. MediaNama says it could not verify a CNBC report that Apple had made the necessary iOS changes.
This changes who the rule actually regulates. The duty falls on WhatsApp, Telegram, Signal, Arattai and others, but the capability sits with Apple, Google and the telcos. A mandate that assigns liability to the party without the lever is a reliable way to produce either non-compliance or workarounds. The most likely workaround is repeated OTP verification, which shifts cost to users. Kar warned that the mobile bill "is going to shoot up."
Telcos are positioning alternatives. MediaNama reports Airtel saying in October 2026 that silent authentication can replace OTPs, and Vodafone Idea announcing a silent-verification partnership with Meta in June 2026. Silent network verification is a more privacy-proportionate route than repeated SMS codes, but it makes app compliance depend on telco integrations that do not yet cover every operator or device.
A pattern of retreat that the clarification does not resolve
The original direction was more aggressive. According to India Briefing, it gave apps 90 days to implement continuous SIM-based authentication, required web and desktop sessions to log out automatically within six hours, and demanded compliance reports within 120 days. Tele.net reported in April 2026 that DoT had rolled back the six-hour logout and moved to a risk-based approach, ending sessions immediately only on suspected fraud. It attributed the change to industry pushback and said platforms expected technical readiness only by October to November 2026.
That sequence is instructive. Regulators moved from a blunt timer toward a risk-based standard once engineers explained the limits. The 24-hour check is a fixed timer again. If DoT's own experience with the six-hour logout was that a rigid interval over-reached, the same logic suggests the 24-hour check should be framed as an outcome (reliably detect SIM removal or substitution) and not as a polling schedule.
What proportionate regulation would look like
- Publish the clarification. An obligation that carries enforcement consequences under the Telecommunications Act should exist as a public, dated document.
- Regulate the outcome. Allow apps to meet the standard through silent network authentication, OS attestation, or telco-side checks, rather than mandating one mechanism.
- Bind the enablers. If the duty only works with OS and telco cooperation, DoT should place corresponding obligations on those layers, or the app is left to guarantee what it cannot control.
- Keep a fraud-triggered tier. The risk-based logic DoT adopted for sessions is the better template: tighter checks where signals indicate abuse, not blanket friction for every user.
The fraud problem is real, and tying accounts to the registering SIM is a defensible tool against it. But a deadline of 31 December 2026 leaves about six weeks to build against a requirement whose interval was clarified through a leak and whose feasibility depends on companies the rule does not name. The credible path is to publish the standard, define success by outcome, and let the ecosystem layers that hold the SIM data carry their share of the duty.