If your AI chatbot collects names, phone numbers or other personal details, India's DPDP Act applies to it. You need a clear notice, consent for a stated purpose, reasonable security, a way to correct or delete data, and deletion once the purpose is over. Most duties start on 13 May 2027.
AI chatbots on websites and WhatsApp have become the first point of contact for many Indian businesses. A visitor types their name, mobile number and requirement, and the bot qualifies the lead and passes it to sales. That is useful. It is also processing of personal data, which is exactly what the Digital Personal Data Protection Act, 2023 (DPDP Act) regulates.
This article explains, in plain language, what the Act and the DPDP Rules, 2025 mean for a business that runs a chatbot, and gives a practical checklist. It is general information, not legal advice. For your specific case, speak to a lawyer who works on data protection.
What is the DPDP Act and when does it apply?
The Digital Personal Data Protection Act, 2023 is India's main law on digital personal data. It applies to personal data collected in digital form, or collected offline and later digitised. A business that decides why and how personal data is processed is a Data Fiduciary. The person whose data it is, such as your website visitor, is the Data Principal. A company that processes data on your behalf, such as a chatbot or CRM provider, is a Data Processor.
The Ministry of Electronics and IT notified the DPDP Rules on 14 November 2025, with a phased start. According to a summary of the Rules by SCC Online, the procedural rules took effect immediately and the main obligations on businesses (notice, security, breach reporting, retention, children's data and rights) start eighteen months after publication. Several legal analyses put that date at 13 May 2027. Rules for registered consent managers follow their own, separate timeline.
In early 2026 the ministry asked industry for views on shortening the timeline to 12 months. Before you plan around a date, check the latest notification from MeitY.
Why does a chatbot fall under the DPDP Act?
A chatbot does not need to ask for an Aadhaar number to be covered. Any information about an identifiable person counts. Typical chatbot data includes:
- name, mobile number and email address;
- the conversation itself, which may include health, financial or family details the visitor chose to share;
- booking, order or payment references;
- location, device and IP details stored in logs;
- WhatsApp profile name and number.
Your business is responsible for this data even if the chatbot runs on a third-party platform or an AI model from an overseas company. You choose the purpose, so you are the Data Fiduciary.
What must a chatbot do to comply?
| Requirement | What it means for a chatbot |
|---|---|
| Notice | Before collecting details, show a short, clear notice: what data you collect, why, and how the person can withdraw consent or complain. |
| Consent | Consent must be free, specific, informed and unambiguous, for a stated purpose. Collecting a number "to answer your enquiry" is not consent for marketing campaigns. |
| Purpose limitation | Use the data only for the purpose you stated. A new purpose needs fresh consent or another lawful ground. |
| Security | Reasonable safeguards such as encryption, access control, logging and backups, including at your processors. |
| Breach reporting | If data is exposed, inform the Data Protection Board and the affected people as the Rules require. |
| Retention and deletion | Delete data when the purpose is complete, unless a law requires you to keep it. The Rules also require some logs to be kept for at least one year. |
| Rights | People can ask to access, correct or erase their data and raise grievances. Publish a contact for these requests. |
| Children | Processing a child's data needs verifiable consent from a parent or guardian. |
What does a good consent flow look like in a chatbot?
Consent does not have to be a long legal page. In a chat window, it can be one short message before the bot asks for details:
- State the purpose. "To send you a quote, we need your name and mobile number."
- Link the full notice. A link to your privacy policy, written in plain language.
- Ask for a clear action. A button such as "I agree, continue". Do not pre-tick boxes.
- Separate optional uses. Offers and newsletters get their own opt-in, not bundled with the enquiry.
- Record it. Save the time, the notice version and what the person agreed to, alongside the lead in your CRM.
The Rules also say notices should be understandable on their own. For Indian audiences, offering the notice in Hindi or Gujarati as well as English is a sensible step where your customers use those languages.
What about the AI model behind the chatbot?
Most chatbots send each message to a large language model, often hosted by a company outside India. Under the DPDP Act, that company is acting for you, so you remain responsible. Questions to settle before launch:
- Does the AI provider use your data for training? Business API terms from the major providers usually say they do not by default, but read the current terms and record your settings.
- Where is the data stored and for how long? Note the provider's retention period for API logs.
- Do you have a contract? A data processing agreement with your chatbot platform and AI provider should cover security, breach notice and deletion.
- Do you need to send everything? Strip phone numbers and other identifiers from the text sent to the model when the answer does not need them.
- Cross-border transfers. The Act allows transfers except to countries the government restricts. Check whether any restriction applies to your provider.
How long should you keep chatbot conversations?
Set a retention period for each kind of data instead of keeping everything forever:
- Leads that did not convert: keep them only as long as a sales follow-up is reasonable, then delete or anonymise them.
- Customers: keep what you need for service, warranty, tax and accounting, as those laws require.
- Raw chat transcripts: often the riskiest data. Keep a summary in the CRM and delete the full transcript sooner.
- Security logs: keep them for at least the period the Rules require.
Automate this. A scheduled job that deletes old transcripts is far more reliable than a reminder in someone's calendar.
What are the penalties?
The Schedule to the Act sets maximum penalties per breach. The highest, up to ₹250 crore, applies to failing to take reasonable security safeguards to prevent a personal data breach. Other failures, such as not reporting a breach or not meeting the duties for children's data, carry lower but still serious maximums. The Data Protection Board decides the actual amount based on factors such as the nature and duration of the breach.
A DPDP checklist for chatbot owners
- List every place the chatbot stores data: chat platform, CRM, spreadsheet exports, email alerts, WhatsApp inbox.
- Write a plain-language notice and add a consent step before the bot collects contact details.
- Keep marketing consent separate from enquiry consent.
- Restrict who in your team can see full transcripts.
- Sign data processing terms with your chatbot, CRM and AI vendors.
- Set retention periods and automate deletion.
- Publish a contact for data requests and grievances, and decide who answers them.
- Write a short breach response plan: who checks, who decides, who informs the Board and customers.
- Avoid targeting children, or add a guardian consent process if your service is meant for them.
FAQs
Does the DPDP Act apply to small businesses?
Yes. The Act does not exempt businesses by size. The government can exempt certain classes of Data Fiduciaries, including startups, from some provisions by notification, so check whether any exemption applies to you.
Is a WhatsApp chatbot covered as well as a website chatbot?
Yes. Personal data collected through WhatsApp, a website, an app or a voice bot is all digital personal data. The same duties apply to every channel.
Do I need consent if the customer messaged me first?
A customer who contacts you for a quote expects you to use their details for that quote. Using the same number later for promotions is a different purpose, so ask for separate consent before you add them to marketing campaigns.
When do the main DPDP obligations start?
Under the Rules as notified in November 2025, the main obligations on businesses start eighteen months later, which legal analyses place at 13 May 2027. The government has consulted on bringing this forward, so check the latest notification.
Can I use an overseas AI model for my chatbot?
Generally yes, unless the government restricts transfers to that country. You stay responsible for the data, so choose a provider with clear terms on training, retention and security, and sign a processing agreement.
Want a chatbot that respects your customers' data?
We build chatbots with a consent step, role-based access, retention rules and CRM records of consent from day one. See our AI chatbot development and WhatsApp automation services, or our AI CRM development work. To review an existing chatbot, talk to our team.



