Small-business operations
The DPDP Act for small businesses: forms, WhatsApp and CRM before May 2027
India’s Digital Personal Data Protection Act was passed in 2023, and its Rules were published on 13 November 2025. Most of the duties on businesses start eighteen months after that, on 13 May 2027. If you collect enquiries through a website form, a Facebook or Google lead form, WhatsApp, or a CRM, those duties reach you whatever your size. This guide explains what changes for each of those places, what is still unclear, and what to fix first. It is general information, not legal advice.
When does the DPDP Act start to apply?
In three steps. The government’s commencement notification of 13 November 2025 and the DPDP Rules, 2025 published the same day set the dates. Counting from that day:
| When | What comes into force | Does it affect a small business? |
|---|---|---|
| 13 November 2025 | Definitions, and the sections that set up the Data Protection Board | Not directly. Until May 2027 the IT Act’s section 43A and the 2011 rules on sensitive personal data still apply. |
| 13 November 2026 | Registration and duties of consent managers (section 6(9) and Rule 4) | Only if you plan to use a registered consent manager. Most will not. |
| 13 May 2027 | Notice and consent, legitimate uses, security, breach reporting, children’s data, people’s rights, and the penalties (sections 3 to 17 except 6(9), section 27 except 27(1)(d), sections 28 to 34, 36, 37 and 44(2), with Rules 3, 5 to 16, 22 and 23) | Yes. This is the date that matters. |
The notification says “eighteen months from the date of publication”, and the Gazette is dated 13 November 2025. A PIB release of 16 May 2026, on a MeitY workshop at which its Secretary spoke, describes the Act as “becoming fully enforceable from 13 May 2027”. One thing was not ready as of August 2026: the government told Parliament that it had advertised the Data Protection Board’s chairperson and member posts in June 2026, and did not say that any appointments had been made.
Until 13 May 2027, the older regime applies. Section 43A of the IT Act and the 2011 rules on sensitive personal data already expect reasonable security practices from businesses that handle sensitive personal data such as medical records. The DPDP Act removes section 43A on 13 May 2027, when its own duties take over.
Is there an exemption for small businesses?
No. The Act applies to digital personal data, and to paper records that are later digitised. Its one carve-out for individuals covers data used for a “personal or domestic purpose”, which a shop, clinic or agency is not. Section 17(3) lets the government exempt some businesses, startups included, from a short list of duties such as the notice requirement; the Act defines a startup as a private limited company, partnership firm or LLP incorporated in India and recognised under the government’s startup criteria, so a sole proprietor would not qualify. Section 17(5) lets it exempt classes of business from any provision within five years of commencement. As of 12 November 2026 we found no notification using either power, and the Rules do not mention small businesses or MSMEs at all. The government’s summary promises “a facilitative compliance regime for startups and smaller enterprises”. That describes how it means to enforce the Act. It exempts nobody.
In the Act’s language, your business is a Data Fiduciary: the one that “determines the purpose and means of processing”. Your CRM provider, your website host and your WhatsApp platform are usually Data Processors, which process data “on behalf of” you. That split decides most of what follows.
Does replying to an enquiry need consent?
Probably not, and this is the most useful thing in the Act for a small business. Section 7(a) allows processing, without separate consent, of data a person has “voluntarily provided” for a “specified purpose”, as long as they have not said they object. The Act’s own illustration is a person who gives a property broker their details to find a rental. The broker may use them for that, and must stop when the person says they no longer need the help.
Our reading, which is not settled law: when someone fills in your enquiry form or messages you to ask about a service, calling or messaging them back about that enquiry fits section 7(a). Adding them to a newsletter, a WhatsApp broadcast list, an ad audience, or sharing their details with a partner does not. Those need consent.
What consent has to look like
Where you need consent, section 6(1) sets the bar: it must be “free, specific, informed, unconditional and unambiguous with a clear affirmative action”, and limited to the data needed for the purpose. In practice:
- A separate, unticked box for marketing messages. A box ticked by default is not a clear affirmative action.
- Do not make the enquiry depend on agreeing to marketing. Consent must be unconditional.
- Ask only for the fields you use. If you never post anything to a customer, you do not need their address.
- Make withdrawing as easy as giving. Section 6(4) says withdrawal should be possible “with the ease” comparable to giving consent. A one-tap opt-in with an email-us-to-opt-out policy is unlikely to meet that.
- Keep a record. Under section 6(10), if there is a dispute, it is the business that has to prove consent was given.
What should the notice on your form say?
When you ask for consent, section 5 requires a notice, in English or any language in the Eighth Schedule of the Constitution if the person prefers. Rule 3 says it must be standalone, in clear and plain language, and give:
- an itemised description of the personal data you collect (name, phone number, email, the message, and so on);
- the specific purpose, and the goods or services that the data is for;
- a link or other means to withdraw consent;
- how the person can exercise their rights; and
- how they can complain to the Data Protection Board.
Section 5 ties the notice to a request for consent, and section 7 does not mention a notice. But section 7(a) covers data given for a “specified purpose”, and the Act defines that as the purpose mentioned in the notice you gave. So even where you rely on legitimate use, show a notice that states the purpose.
A short notice beside the form is the usual shape. Rule 3 says the notice must be understandable on its own, so the short notice itself should carry the items above; a link to your fuller privacy policy can sit beside it, not replace it. For a simple enquiry form, something like this:
If you already hold contacts gathered with consent before May 2027, section 5(2) asks you to give them a notice as soon as it is reasonably practicable. A customer list that has sat in a spreadsheet for years is the obvious place to start.
What about Facebook and Google lead forms?
You remain the Data Fiduciary for leads that arrive through an ad platform. The platforms already require much of what the Act will:
- Meta’s Lead Ads terms require every lead form to include “all disclosures and choice mechanisms”, and make you responsible for getting consent if you use the data for anything beyond what the person asked for.
- Google’s lead form requirements need a link to your privacy policy, and say advertisements for healthcare-related content are not allowed to use lead forms at all.
- Google stores leads for 60 days and tells advertisers to download them often. Once they sit in your spreadsheet or CRM, the security and retention duties are yours.
If you upload customer lists to build ad audiences, that is a separate use. It needs consent that covers it, and for health businesses Google’s policies and Meta’s Business Tools Terms restrict it anyway. Our guide on Google Ads for clinics covers those platform rules.
What changes for WhatsApp?
Less than you might fear, if you already follow WhatsApp’s own rules. The WhatsApp Business Messaging Policy lets you message people only if they gave you their number and you have “received opt-in permission”, and says “You are solely responsible for determining the method of opt-in”. It also requires a published privacy policy and that you honour requests to stop.
The Act adds three things. Consent for promotional messages must meet the section 6 standard above. Stopping must be as easy as starting, so a reply such as STOP should actually stop broadcasts. And if you use the free WhatsApp Business app on staff phones, customer chats sit on devices you may not control. From May 2027, Rule 6’s security duties will apply to that data too. For more on the app and the API, see our guide to the WhatsApp Business API in India.
Is your CRM provider responsible for your data?
Not instead of you. From 13 May 2027, section 8(1) makes the business responsible for processing done on its behalf “irrespective of any agreement to the contrary”, and section 8(2) allows a business to use a Data Processor “only under a valid contract”. Rule 6(1) lists the minimum security safeguards and says the contract with a processor must include a provision for taking them. Ask every vendor that touches customer data, from your CRM and form builder to your WhatsApp provider and any AI tool, four questions:
- Will you sign a contract that names you as our Data Processor and commits you to reasonable security safeguards?
- Which other companies (sub-processors) handle our data, and in which countries?
- If you have a breach, how quickly will you tell us?
- When we leave, how do we get our data out, and how do you erase it?
Keep a simple list of these vendors. From May 2027, under section 11, a person can ask you for the identities of every Data Fiduciary and Data Processor you have shared their data with, and you will need to answer. If you are weighing a CRM, our comparison of custom and off-the-shelf CRMs covers the data questions too.
What security does the Act expect?
Section 8(5) asks for “reasonable security safeguards to prevent personal data breach”. Rule 6(1) sets out the minimum, which reads like a checklist for a small office:
- encryption, obfuscation, masking or virtual tokens for personal data;
- control over who can access the systems that hold it;
- logs and monitoring, so that unauthorised access can be detected and investigated;
- backups, so that data can be restored after a breach or loss;
- keeping those logs and the personal data for one year, unless another law says otherwise; and
- a security clause in every processor contract, plus organisational measures to make all of this happen.
For a ten-person business that usually means individual logins rather than a shared password, two-step sign-in on the CRM and email, removing access the day someone leaves, and not exporting full customer lists to personal laptops.
What if there is a breach?
From May 2027, section 8(6) and Rule 7 require you to tell each affected person “without delay”, in plain terms, what happened, the likely consequences, what you are doing about it and what they can do to protect themselves, with a contact. You must also tell the Data Protection Board without delay, and send it a detailed report within seventy-two hours of becoming aware of the breach, unless the Board allows longer on a written request.
A separate duty applies already. The CERT-In Directions of April 2022 require organisations to report listed cyber incidents, including data breaches and data leaks, within six hours of noticing them. The same Directions ask you to name a point of contact for CERT-In and to keep system logs for a rolling 180 days, stored in India. Decide now who in your business would make those calls.
How long can you keep enquiry data?
Two rules pull in different directions. Section 8(7) says to erase personal data once the person withdraws consent or the purpose is no longer being served, unless another law requires you to keep it, and to make your processors erase it too. From May 2027, Rule 8(3) says every business must keep personal data and the logs of processing “for a minimum period of one year from the date of such processing”, for purposes the government may need, and then erase them unless another law requires longer. Our reading of the two together: keep enquiry data and logs for a year from the last processing, then erase what no longer serves its purpose unless another law needs it. Write that period down and apply it. A lead from 2019 who never became a customer is data you are still responsible for and no longer use.
Do you collect data about children?
The Act treats everyone under eighteen as a child. From May 2027, section 9 requires verifiable consent from a parent before processing a child’s data, and bans tracking, behavioural monitoring and “targeted advertising directed at children”. Coaching centres, schools, tuition businesses and paediatric clinics should check every form that a parent or student fills in. The Rules lift the parental-consent and tracking rules for clinics and healthcare professionals only for providing health services, “to the extent necessary for the protection of her health”, and for educational institutions only for tracking connected with their educational activities or children’s safety. Our reading is that marketing to children or their parents gets no exemption.
What else will people be able to ask of you?
From May 2027 a person can ask what data you hold and who you shared it with, ask you to correct or erase it, and complain. Rule 9 requires you to publish contact details of a person who can answer questions about processing, and Rule 14 requires you to publish how long you will take to respond to a grievance, which cannot be more than ninety days. Under section 13(3), a person must use your grievance process before going to the Board.
What are the penalties?
The Schedule to the Act sets maximums, each one “may extend to”:
| Breach | Maximum penalty |
|---|---|
| Failing to take reasonable security safeguards (section 8(5)) | Rs 250 crore |
| Failing to notify the Board or affected people of a breach (section 8(6)) | Rs 200 crore |
| Breaking the rules on children’s data (section 9) | Rs 200 crore |
| Breaking most other provisions of the Act or Rules | Rs 50 crore |
Two further tiers exist: up to Rs 150 crore for the extra duties of Significant Data Fiduciaries (section 10), which a small business is unlikely to be, and up to Rs 10,000 for a person’s own duties under section 15. These are maximums. Section 33(2) tells the Board to weigh the nature, gravity and duration of the breach, the type of data, whether it was repeated, any gain or loss avoided, what the business did to mitigate it and how quickly, whether the penalty is proportionate, and its likely impact on the business. The process includes an inquiry, a hearing, the option of mediation and of a voluntary undertaking, and an appeal to the Telecom Disputes Settlement and Appellate Tribunal.
A checklist to finish before May 2027
- List every place personal data comes in: website forms, ad lead forms, WhatsApp numbers, phone calls noted in a sheet, walk-in registers.
- List every tool and vendor it goes to, with the country each one stores data in.
- Split each use into replying to an enquiry (legitimate use, on our reading) and everything else (consent).
- Rewrite form notices to Rule 3’s list, and add a separate, unticked marketing box.
- Make opting out of WhatsApp and email marketing work in one step, and test it.
- Put a processor clause in front of each vendor that handles customer data.
- Turn on individual logins and two-step sign-in, and remove old staff access.
- Write a one-page breach plan: who decides, who tells CERT-In, the Board and customers.
- Set a retention period for cold enquiries and delete on schedule.
- Publish a contact for data questions and your grievance response time.
QUESTIONS
Common questions
When does the DPDP Act apply to businesses?
Most duties on businesses, and the penalties, commence eighteen months after the DPDP Rules were published on 13 November 2025, on 13 May 2027. The definitions and the sections setting up the Data Protection Board are already in force.
Does the DPDP Act apply to small businesses?
Yes. There is no general exemption by size. The government has a power to exempt some businesses, startups included, from some or all of the Act, but as of 13 November 2026 we found no notification using that power.
Do I need consent to reply to a customer enquiry?
Probably not, on our reading. From 13 May 2027, section 7(a) allows using data a person voluntarily gave you for the purpose stated in your notice, unless they object. We read a call-back on an enquiry as fitting that; it is not yet tested. Marketing to them later, adding them to ad audiences or sharing their data needs consent.
Can I send WhatsApp marketing messages under the DPDP Act?
Yes. From 13 May 2027 you will need consent that is free, specific, informed, unconditional and given by a clear action, and with an opt-out as easy as the opt-in. WhatsApp’s own policy already requires opt-in permission and a published privacy policy.
Is my CRM provider responsible for protecting my customers’ data?
Your business stays responsible. From 13 May 2027 the Act makes the business answerable for processing done on its behalf whatever the contract says, and allows using a processor only under a valid contract that includes security safeguards.
What is the maximum penalty under the DPDP Act?
Up to Rs 250 crore for failing to take reasonable security safeguards, once the penalties apply from 13 May 2027. The Board must weigh the gravity, duration, mitigation and impact on the business, so the amounts are maximums, not fixed fines.
REFERENCES
Sources and further reading
Each link was opened and checked on .
- India Code: Digital Personal Data Protection Act, 2023
- Gazette of India (13 November 2025): G.S.R. 843(E), DPDP Act commencement notification
- Gazette of India (13 November 2025): G.S.R. 846(E), Digital Personal Data Protection Rules, 2025
- PIB (14 November 2025): DPDP Rules notified
- PIB (16 May 2026): release on a MeitY workshop stating the Act becomes fully enforceable from 13 May 2027
- Lok Sabha unstarred question 3960 (12 August 2026): DPDP implementation and the Data Protection Board
- IT (Reasonable Security Practices and Sensitive Personal Data) Rules, 2011 (PRS copy)
- Meta: Business Tools Terms
- CERT-In: Directions under section 70B(6) of the IT Act, 28 April 2022
- WhatsApp Business Messaging Policy
- Meta: Lead Ads Terms
- Google Ads policy: lead form requirements
- Google Ads Help: lead form assets
