Is cold email legal in India? Yes, for now (2026)
2026-11-16 · updated 2026-11-16 · 11 min read · Adam Axelsson, founder of Revexa
Yes, for now. India has no law that bans unsolicited commercial email: TRAI's anti-spam regulations cover calls and SMS only, and the IT Act's one email offence, section 66A, was struck down by the Supreme Court in 2015. That changes on 13 May 2027, when the core of the Digital Personal Data Protection Act 2023 (DPDP Act) comes into force. From then on, using a named person's email address needs their consent or one of the Act's narrow "legitimate uses", and India has no general legitimate-interest ground. The main way out is the Act's exclusion for personal data the person made public themselves. We found no guidance from the regulators on cold email or LinkedIn messages.
Checked on 16 November 2026 against the DPDP Act and the DPDP Rules 2025 in the Gazette of India, the commencement notifications of 13 November 2025, the IT Act 2000 on India Code, TRAI's TCCCPR 2018 and its amendments, and press releases from TRAI and the Department of Consumer Affairs. This is not legal advice.
India is a country where the honest answer depends on the date. Today it is closer to the United States, with no email rule at all; from May 2027 the data law asks for consent much like Canada or Australia, but through privacy law rather than an anti-spam act. All countries: cold email laws by country.
India at a glance
| Situation | Rule | Source |
|---|---|---|
| Generic company address (info@) | No email rule today; from 13 May 2027 not personal data if it identifies no individual (our reading) | DPDP Act s. 2(t) |
| Named employee | No consent rule today; from 13 May 2027 consent or a legitimate use, unless the person made the address public | DPDP Act ss. 3(c)(ii), 4, 7 |
| Sole trader | Same as named employee: the Act protects individuals, whatever their business | DPDP Act s. 2(j), 2(t) |
| Existing customers | No soft opt-in; data a customer gave you for a purpose may be used for that purpose (s. 7(a)); marketing other products is unclear (our reading) | DPDP Act s. 7(a) |
| Email asking for consent | No guidance found (our reading: not safe after 13 May 2027 unless the address was made public by the person) | None |
| LinkedIn and social DMs | No guidance found; the DPDP Act does not depend on the channel (our reading: same as email) | DPDP Act s. 2(x) |
| Cold calls and SMS | Covered by TRAI's TCCCPR: registered senders, the 140xx series for promotional calls, the recipient's preferences | TCCCPR 2018; TRAI |
| Regulator | Data Protection Board of India (DPDP Act); TRAI for calls and SMS | G.S.R. 844(E); TCCCPR |
| Maximum penalty | Up to ₹50 crore for other breaches, which in our reading include processing without a lawful ground; ₹250 crore for security failures; none before 13 May 2027 | DPDP Act s. 33, Schedule |
No email rule today
The Information Technology Act 2000 has no spam provision; the words "spam" and "unsolicited" do not appear in the updated text on India Code. Its one email offence was section 66A, which punished sending:
"(c) any electronic mail or electronic mail message for the purpose of causing annoyance or inconvenience or to deceive or to mislead the addressee or recipient about the origin of such messages"
India Code's own footnote records: "Section 66A has been struck down by Supreme Court’s Order dated 24th March, 2015 in the Shreya Singhal vs. Union of India". Section 43A, the IT Act's data protection clause, makes a company liable to pay compensation when it is negligent with "sensitive personal data or information" and causes wrongful loss or gain; it is a security rule, not a marketing rule. The DPDP Act deletes section 43A from the same date as its own core provisions.
The content still matters: the IT Act keeps offences such as "cheating by personation by using computer resource" (section 66D). A plain, honest B2B email faces no consent rule until 13 May 2027 (our reading).
The DPDP Act and its commencement dates
The Digital Personal Data Protection Act 2023 (Act No. 22 of 2023, dated 11 August 2023) comes into force in stages. On 13 November 2025 the Ministry of Electronics and Information Technology published three notifications in the Gazette:
- G.S.R. 843(E) brought the definitions and the Board's provisions into force at once; sections 6(9) and 27(1)(d), on consent managers, "one year from the date of publication"; and sections 3 to 5, sections 6(1) to (8) and (10), sections 7 to 17, most of section 27, sections 28 to 34, 36, 37 and 44(2) "eighteen months from the date of publication of this gazette".
- G.S.R. 844(E) established the Data Protection Board of India, with its head office in the National Capital Region.
- G.S.R. 846(E), the Digital Personal Data Protection Rules 2025: rules 1, 2 and 17 to 21 in force on publication, rule 4 "one year after the date of publication", and "Rules 3, 5 to 16, 22 and 23 shall come into force eighteen months after the date of publication of this Gazette."
The Gazette issues are dated 13 November 2025; the government's own explainer says the Rules were notified on 14 November 2025 (PIB, 17 November 2025). Counting from the Gazette date, the obligations that matter for cold email, the Act's scope (s. 3), lawful grounds (s. 4), notice (s. 5), consent (s. 6), legitimate uses (s. 7) and penalties (s. 33), start on 13 May 2027 (our calculation; a day later if you count from 14 November).
What changes on 13 May 2027
Section 4(1) sets the rule. A person may process the personal data of a Data Principal:
"only in accordance with the provisions of this Act and for a lawful purpose"
and that purpose must be one "for which the Data Principal has given her consent" or "for certain legitimate uses".
"Personal data" is "any data about an individual who is identifiable by or in relation to such data" (s. 2(t)), and "processing" includes "collection, recording", "storage", "use" and "disclosure by transmission" (s. 2(x)). A work address like priya.sharma@company.in identifies an individual, so building a prospect list and sending to it is processing. The Act makes no exception for business contact details (our reading).
Consent must be "free, specific, informed, unconditional and unambiguous with a clear affirmative action" (s. 6(1)), it can be withdrawn at any time "with the ease of doing so being comparable to the ease with which such consent was given" (s. 6(4)), and if challenged, the company must prove "that a notice was given" and consent was given (s. 6(10)). Under rule 3 of the DPDP Rules, the notice must include "an itemised description of such personal data" and the purpose, and a link for withdrawing consent and complaining to the Board.
The legitimate uses in section 7 are a closed list: personal data voluntarily provided for a specified purpose, state benefits and functions, legal obligations, court orders, medical emergencies and epidemics, disasters, and employment. None of them covers prospecting. India has no equivalent of GDPR's legitimate interests (compare GDPR and B2B email under legitimate interest).
Published addresses: the public data exclusion
Section 3(c)(ii) says the Act does not apply to:
"personal data that is made or caused to be made publicly available"
by "the Data Principal to whom such personal data relates" or by "any other person who is under an obligation under any law for the time being in force in India to make such personal data publicly available".
The Act's own illustration: "X, an individual, while blogging her views, has publicly made available her personal data on social media. In such case, the provisions of this Act shall not apply."
This is the most important clause for B2B senders, and we found no guidance from MeitY or the Board on how far it reaches. Our reading:
- An address the person published themselves, for example on their own website, in a conference speaker bio they wrote or in the public contact section of their profile, falls outside the Act.
- An address on the employer's team page was published by the company, not the person. Whether the person "caused" it to be published is untested.
- An address you guessed from a pattern or bought in a list was never made public by the person, so the Act applies in full.
Named employees, sole traders and info@ addresses
The Act protects the "Data Principal", "the individual to whom the personal data relates" (s. 2(j)). It does not separate private and business life, so a named employee and a sole trader are protected in the same way. A generic address such as info@ or sales@ that identifies no individual is not personal data, so in our reading the DPDP Act does not apply to it at all.
Existing customers and people who gave you their details
There is no soft opt-in. Section 7(a) allows processing "for the specified purpose for which the Data Principal has voluntarily provided her personal data", as long as she has not said she does not consent. The Act's example is a buyer who asks a pharmacy for a receipt by text. Our reading: a prospect who hands you a card and asks for your pricing has given you data for that purpose; marketing other products later needs consent.
Can the first email ask for consent?
No guidance found. After 13 May 2027, sending an email to ask for consent is itself processing of the person's address, and asking for consent is not a legitimate use. Our reading: unless the address falls under the public data exclusion, get consent by another route, such as a form on your website or a conversation the person started.
LinkedIn and social media messages
No guidance found. TRAI's regulations do not cover LinkedIn, and the DPDP Act does not depend on the channel: it applies to the processing of digital personal data however you send. Our reading: from 13 May 2027 a LinkedIn sales message to a person in India is judged like an email. A profile the person filled in and made public may fall under the public data exclusion; a phone number or email exported from it and used elsewhere is less clear. More on the platform side in LinkedIn outreach without restrictions.
TRAI's TCCCPR: calls and SMS, not email
The Telecom Commercial Communications Customer Preference Regulations 2018 define a "Commercial Communication" as "any voice call or message using telecommunication services, where the primary purpose is to inform about or advertise or solicit business". They regulate calls and SMS through telecom operators: registered senders and headers, content templates, consent and the customer's registered preferences. Email appears in them only as a channel for complaints and notices. TRAI has amended them in December 2018, February 2025, September 2026 and November 2026, and none of the amendments extends them to email (checked against the texts).
For cold calls, TRAI describes the 140xx series as designated "for regulated promotional calls". The September 2026 amendment treats automated calls made without prior declaration as unsolicited, and when a sender's numbers are flagged, operators can move to "barring of outgoing services, and disconnection of telecom resource in cases of repeated violations" (PIB, 18 September 2026).
Is an email rule coming?
The Department of Consumer Affairs published draft Guidelines for the Prevention and Regulation of Unsolicited and Unwarranted Business Communication in June 2024, aimed at "unsolicited or unwarranted business communication originating from unregistered telemarketers or 10-digit private numbers" (PIB, 20 June 2024). We found no final version. In October 2026 a law firm described a new draft from the Central Consumer Protection Authority that would extend to OTT messaging apps, social media and other electronic channels (Khaitan & Co, 6 October 2026); we could not find that draft on a government site, and it is not in force. Whether it would cover email is unclear.
Penalties and real cases
Under section 33, the Data Protection Board may impose a penalty from the Schedule if it finds that a breach "is significant", after a hearing. The Schedule's ceilings: "two hundred and fifty crore rupees" for failing to take reasonable security safeguards, "two hundred crore rupees" for breach notification failures and for children's data, and "fifty crore rupees" for "Breach of any other provision of this Act or the rules made thereunder", which is where processing without consent or a legitimate use would fall (our reading). Section 33 comes into force on 13 May 2027, so no DPDP penalty can be imposed before then.
We found no fine, order or court decision in India about cold email, B2B or consumer. The Board has published no decisions that we could find. TRAI's enforcement concerns calls and SMS.
Checklist for B2B email to India
- Until 13 May 2027: no consent rule for email, but name your company, write honestly and stop when asked.
- Prepare now for 13 May 2027: for every named contact, record where the address came from and whether the person published it themselves.
- After 13 May 2027: without consent or the public data exclusion, do not email a named person; guessed and bought addresses are the riskiest.
- When you ask for consent, give a notice that lists the data, the purpose, and how to withdraw and complain, and make withdrawing as easy as agreeing.
- Generic info@ addresses that identify no individual are outside the DPDP Act (our reading).
- Treat LinkedIn and other DMs like email (our reading).
- If you are in the EU, GDPR still applies to your own processing of Indian contacts.
How Leo handles India
Leo, the buying-signal agent Revexa builds, applies its own automatic rule only to Germany, where nothing is sent without your approval, not even in autonomous mode. India has no such rule. In review mode, the default, you read and approve every draft, and you send in your own name, so following Indian law, including the DPDP Act from 13 May 2027, is yours to check before you approve. Leo is the wrong choice if you need software that tracks Indian consent for you.
Common questions
Is B2B cold email legal in India?
Yes, until 13 May 2027: India has no anti-spam law for email, and TRAI's rules cover only calls and SMS. From 13 May 2027 the DPDP Act requires consent or a legitimate use to process a named person's email address, unless the person made it public themselves.
When does the DPDP Act come into force?
In stages. The Board and the definitions started on 13 November 2025, consent manager rules one year later, and the core obligations and penalties 18 months after the Gazette of 13 November 2025, which is 13 May 2027 by our calculation.
Does the DPDP Act have a legitimate interest ground like GDPR?
No. Section 7 lists specific "legitimate uses", such as data a person voluntarily provided for a purpose, legal obligations, emergencies and employment. Prospecting is not one of them.
Do TRAI's DND rules apply to email?
No. The TCCCPR 2018 covers voice calls and messages "using telecommunication services", meaning calls and SMS through telecom operators. Email is outside it.
What are the fines for cold email in India?
None today. From 13 May 2027 the Data Protection Board can impose up to ₹50 crore for a significant breach such as processing without a lawful ground, and up to ₹250 crore for security failures. We found no cold email case.