Policies · eGov

Businesses sending promotional SMS and voice calls in India must satisfy two separate consent regimes — one governing the telecom channel, the other governing the processing of personal data used to target recipients.
✦ AI SUMMARY 30-second read

- The Third Amendment Regulations, 2026 expressly state that TCCCPR compliance does not exempt a sender from obligations or liability under the DPDP Act.
- Core DPDP notice and consent obligations under Sections 5 and 6 are scheduled to come into force on 13 May 2027, though the Consent Manager framework under Rule 4 is scheduled to commence on 13 November 2026.
- A valid DLT consent record does not by itself establish that the underlying personal data processing — such as profiling or audience segmentation — is lawful under data protection law.
Why it matters: Businesses that treat telecom consent as sufficient for all marketing activity face compliance exposure under both frameworks simultaneously.

This summary was generated by AI. Editors may review and update it.
Document details
| Document type | Rules & Regulation |
|---|---|
| Issued by | Government of India |
| Region | India |
| Published | 21 November 2026 |
Businesses in India that send promotional SMS messages or voice calls are required to satisfy two distinct regulatory frameworks: the Telecom Commercial Communications Customer Preference Regulations, 2018, administered by the Telecom Regulatory Authority of India, and the Digital Personal Data Protection Act, 2023. The two frameworks operate independently and address different aspects of a marketing campaign.

The Telecom Commercial Communications Customer Preference (Third Amendment) Regulations, 2026 have made the relationship between the two frameworks explicit, clarifying that nothing in the telecom regulations exempts a sender from its obligations or liability under the DPDP Act. Businesses must therefore evaluate their marketing consent processes, customer databases and communication workflows against both sets of requirements.
What the documents say
Under the amended TCCCPR, consent is defined as voluntary permission — whether explicit or inferred — given by a customer to a sender to receive commercial communications relating to a specific purpose, product or service. The amended definition limits this consent to permission for establishing the communication channel itself. Explicit consent must be verified directly from the recipient in a robust and verifiable manner and recorded by the Consent Registrar, or obtained through another verifiable means and registered in the Consent Register in accordance with the procedure specified by TRAI.
The DPDP Act approaches the matter from the perspective of personal data processing. A mobile number linked to an identifiable individual constitutes personal data, as may information used to profile customers, segment audiences or personalise campaigns. Under Section 6 of the DPDP Act, consent must be free, specific, informed, unconditional and unambiguous, expressed through a clear affirmative action, and limited to the personal data necessary for the specified purpose. Section 5 requires a Data Fiduciary to provide a notice before or at the time of seeking consent. Rule 3 of the Digital Personal Data Protection Rules, 2025 further requires the notice to be clear, independently understandable and sufficiently detailed to enable informed consent.
A broad statement in general terms and conditions or a privacy policy may not, by itself, establish valid consent for every form of marketing-related processing under the DPDP Act. Equally, the existence of a privacy notice or an affirmative marketing consent on a website or application does not dispense with the applicable telecom requirements.
Who is affected
Any business that sends commercial communications through promotional SMS or voice calls and processes customer data to identify, segment or target recipients is subject to both frameworks. This includes businesses that use marketing automation platforms, outsourced telemarketing services or customer profiling.
The obligations are relevant to Principal Entities — broadly, the businesses or organisations that send commercial communications, whether directly or through a registered telemarketer — as well as to entities that maintain large customer databases or rely on purchase history and behavioural data to create marketing segments.
Background
The TCCCPR was notified on 19 July 2018 and came into force on 28 February 2019. The framework has evolved through successive amendments: the 2025 amendments strengthened measures against unsolicited commercial communications, while the Third Amendment Regulations, 2026 introduced revised definitions of consent and explicit consent, provisions concerning application-to-person calls and enhanced enforcement mechanisms.
The DPDP Act was enacted in 2023 and the DPDP Rules were notified in November 2025. The framework is being brought into force in phases. As at November 2026, the core obligations relating to notice and consent under Sections 5 and 6, along with the corresponding substantive provisions of the DPDP Rules, are scheduled to come into force on 13 May 2027. The Consent Manager framework under Rule 4 is scheduled to commence on 13 November 2026.
What happens next
Businesses should not wait for the DPDP consent provisions to become enforceable before reviewing their compliance architecture. Organisations are advised to begin assessing consent workflows, privacy notices, data flows and vendor arrangements in advance of the 13 May 2027 implementation date.
Consent withdrawal requires coordinated action across both frameworks. Under Section 6(4) of the DPDP Act, a Data Principal may withdraw consent at any time through a process that must be as easy as the one through which consent was given, after which the Data Fiduciary must cease the relevant processing within a reasonable time. The TCCCPR separately governs revocation of telecom consent and customer preferences. A business must be able to distinguish the purpose for which consent was obtained, the channel to which it relates and the systems in which it is recorded, so that withdrawal under one framework is correctly reflected without inadvertently affecting lawful processing under the other.