Is Your Website Chatbot DPDP Act Compliant? A Plain Checklist
India’s DPDP Act applies to chatbots that collect names, phone numbers or chat messages. Here’s a plain-English checklist, key dates and questions to ask your vendor.

Think about what your website chatbot actually does all day. It talks to strangers. Some of them type their name, their phone number or their email. Some paste an order number, an address or a long story about what went wrong. A few share things you never asked for.
All of that is data about real people. And in India, a law now governs how businesses handle it.
The Digital Personal Data Protection Act, 2023 (the DPDP Act) and its Rules are being phased in, and a key date is close. This article explains, in plain language, what the law means for a website chatbot, what you should do before the main deadline, and what to ask your chatbot provider. It won’t make you a lawyer, but it should leave you knowing which questions to ask one.
Where things stand today
Here’s the timeline, based on the official notifications and reputable legal commentary.
The Act and Rules. The DPDP Act received assent in August 2023. The Ministry of Electronics and IT notified the DPDP Rules, 2025 on 13 November 2025. The government’s own release describes an 18-month phased compliance timeline.
Three phases. Legal commentary summarises the phasing like this: the Data Protection Board provisions took effect on notification in November 2025, provisions for Consent Managers follow after 12 months (13 November 2026, this week), and most core duties for businesses, such as notices, consent, security safeguards, breach reporting and individuals’ rights, apply after 18 months, in mid-May 2027. Sources give 13 or 14 May 2027, a one-day difference in how the date is counted, so plan to be ready by early May.
Could it be sooner? In January 2026, MeitY consulted on shortening the window to 12 months, mainly for large “Significant Data Fiduciaries.” Trackers checked in September and October 2026 found no notification making that change, so May 2027 remained the legal date. Check again before you rely on it. The government also confirmed the November 2026 and May 2027 dates in a written Lok Sabha answer in August 2026, according to one tracker.
Is the regulator active? The Board exists in law, but as of mid-2026 the government was still inviting applications for its chair and members, and its power to hear complaints and impose penalties is expected to bite around May 2027.
The takeaway: you have roughly six months. That’s enough time to do this properly, and not enough to leave it until spring.
Does the law apply to your chatbot?
In most cases, yes. If your chatbot collects or processes digital personal data about people in India, you’re likely a Data Fiduciary under the Act, which is the business that decides why and how the data is used. (The Act also reaches some processing outside India that relates to offering goods or services to people in India.)
Two other terms matter:
Data Principal: the person the data is about. For you, that’s your website visitor or customer.
Data Processor: a company that processes data on your behalf. Your chatbot provider is typically one.
The crucial point, set out in the Act’s Section 8, is that the Data Fiduciary remains responsible for compliance even when a processor does the work, and may only use a processor under a valid contract. In other words, you can’t hand the problem to your chatbot vendor. You share the work, but the responsibility stays with you.
One more warning: be cautious about any chatbot marketed as “DPDP compliant.” Even one vendor that sells a privacy-focused chatbot says its controls support your obligations, while your overall compliance also depends on your notices, lawful bases, internal processes and other systems. No tool can make you compliant by itself.
The 12-point chatbot checklist
Here’s what to work through. Each point includes what to do and what to ask your vendor.
1. Map your data
Write down what your chatbot collects, where it’s stored, who can see it and what you use it for. A one-page table is enough. You can’t protect, explain or delete what you haven’t listed.
2. Give a clear notice before you collect
The law requires that a request for consent be accompanied or preceded by a notice. Under the Rules, the notice must be understandable on its own, separate from your other information, itemise the data you’re collecting and the purpose, give a link to your website or app, and explain how to withdraw consent, exercise other rights and complain to the Data Protection Board.
For a chatbot, that means a short plain-language message and a link to your privacy notice at the moment of collection, ideally in the chat’s first message or just before you ask for details.
3. Get proper consent where it’s needed
Consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action. Practically:
Don’t pre-tick boxes or assume silence is consent.
Don’t bundle “contact me about offers” with “answer my question.”
Ask for contact details after being helpful, and explain why.
Not everything needs consent, though. The Act recognises certain “legitimate uses” in addition to consent, so don’t assume every piece of website processing needs a tick box. What counts as a legitimate use is a legal question, so take advice before relying on one.
4. Make withdrawal as easy as agreeing
The Rules say that withdrawing consent must be as easy as giving it. If someone can start a chat in one click, they shouldn’t need three emails and a phone call to stop. Offer a clear contact route and honour requests quickly.
5. Collect only what you need
Ask for the smallest amount of personal data that serves the purpose. A name and a phone number to call back may be fine. Asking for an ID number, a bank detail or a medical history inside a chat window usually isn’t. Tell the chatbot, in its content, never to ask for sensitive details, and tell customers not to share them.
6. Decide how long you’ll keep it
Don’t keep chat transcripts and leads forever “just in case.” Set a retention period for each kind of data, such as 90 days for general chats and a longer one for active customers, and delete on schedule. The Rules also tie retention to purpose. Ask your vendor how deletion works and whether you can delete a single person’s data on request.
7. Be ready for people’s rights
Individuals can ask to access their data, correct it, erase it and raise grievances. You need a simple process:
A published contact for privacy questions
A way to find one person’s chats and lead records
A way to correct or delete them
A record that you did
8. Protect the data
The law requires reasonable security safeguards. The Rules point to measures such as encryption, masking, access controls, logging and appropriate contract terms with processors. For you, that means:
Strong, unique passwords and two-factor authentication on your chatbot dashboard, if offered
Giving access only to people who need it, and removing it when they leave
Not exporting chat logs to personal devices or shared spreadsheets
Never uploading sensitive documents to your chatbot’s knowledge base. Only upload what you’d be comfortable putting on your public website.
9. Have a breach plan
If personal data is exposed, the Rules require notifying the affected individuals without delay and the Board without delay, followed by a detailed report within 72 hours (with a possible extension from the Board). Write down who decides, who contacts whom and what the notices will say. Ask your vendor how quickly they’d tell you about an incident, since you’ll be the one answering to the regulator and your customers.
10. Handle children’s data with care
The Rules require verifiable parental consent before processing the personal data of anyone under 18, and restrict tracking or behavioural monitoring of children, with limited exemptions for certain organisations such as healthcare providers and educational institutions. If your chatbot is likely to talk to minors (a tuition centre, a coaching institute, a gaming site), don’t assume the exemption covers you. Get advice and consider whether you need an age-appropriate approach, such as inviting a parent or guardian to share details instead.
11. Sign a proper agreement with your chatbot provider
Your vendor should give you a written agreement covering what they do with your data. Ask for it, and read it.
12. Keep records
Keep dated evidence: what your notice said and when, the consent you captured, who you shared data with, requests received and how you handled them. If the Board ever asks questions, hours matter more than weeks.
Ten questions to ask your chatbot provider
Copy these into an email:
Do you act as our Data Processor, and will you sign a data processing agreement?
Where is our data stored and processed, and which sub-processors do you use?
Do you use our chat data to train AI models? Can we opt out?
How can we delete a single person’s chats and lead data?
What are the retention settings, and can we change them?
Who at your company can see our data?
What security measures do you use, and can we enable two-factor authentication?
How and how quickly would you notify us of a breach?
Can we export our data if we leave, and is it deleted afterwards?
How do you support consent notices and withdrawal in the chat window?
A good vendor will answer plainly. Vagueness is information too.
What Glanceia says (and what we’d check)
We make Glanceia, so here’s the straight version.
What the site says: each company gets a fully isolated data environment, with data used only for that company’s chatbot. It also lists lead capture of names, emails and phone numbers, routing to your inbox, a privacy policy and a free plan with limited chat history.
What the site doesn’t spell out: details such as data-processing agreements, data location, sub-processors, deletion tools, breach-notification commitments and consent-notice features. If those matter to you (and for a DPDP checklist, they do), ask the team directly through the contact page and read the privacy policy before you rely on any assumptions.
A note on chat history: Glanceia’s pricing lists plans with different chat-history lengths, such as one day on Free and unlimited on Pro (which is marked “Coming Soon”). That’s a product limit, not a retention policy. Whatever the plan, set your own rules about how long you keep conversations and leads.
Sample wording you can adapt
These are drafts to show the idea. Have a lawyer review the final text.
A first message that points to your notice:
“Hi, I’m an AI assistant. I can answer common questions about [Business]. Please don’t share sensitive details like ID or bank numbers here. See how we handle your data: [privacy notice link].”
A line before collecting contact details:
“Want a team member to follow up? Share your name and phone number, and we’ll use them only to contact you about this enquiry. [Privacy notice link]. You can ask us to delete them anytime at [email].”
A boundary entry for your chatbot’s content:
“If a customer shares an ID number, bank details or health information, don’t repeat it. Tell them not to share sensitive details here and offer to connect them with the team.”
What your privacy notice should cover (outline):
What data you collect through the chatbot and website
Why you collect it, with each purpose stated
How long you keep it
Who you share it with (including your chatbot provider)
How to withdraw consent, access, correct or delete data
Who to contact, and how to complain to the Data Protection Board
What are the penalties?
Understand the scale, but don’t panic. The penalties are caps, not typical outcomes. Legal commentary on the Act and Rules lists up to ₹250 crore for failures relating to security safeguards, up to ₹200 crore for breach-notification failures or violations concerning children’s data, and up to ₹50 crore for other contraventions. How the Board will apply them in practice isn’t yet known, since enforcement hasn’t started.
A six-month plan to May 2027
This month (November): Map your chatbot’s data. Read your vendor’s privacy policy and email the ten questions.
December: Draft your privacy notice and the chatbot’s first message. Decide your retention periods.
January: Set up your rights process: who handles requests, how to find and delete a person’s data.
February: Tighten security: access, passwords, two-factor authentication, removal of old users. Write your breach plan.
March: Review children’s data issues and your vendor agreement. Get legal review of your notice and wording.
April: Test everything: run a mock access request, a mock deletion and a mock breach drill.
Early May 2027: Final check, update records and re-read the latest MeitY notifications.
Common mistakes to avoid
Assuming your vendor handles it. They share the work. You carry the responsibility.
Buying a “DPDP compliant” badge. Compliance depends on how you use the tool.
Burying the notice. A link in a footer nobody reads isn’t enough.
Collecting too much. Every extra field is extra risk.
Keeping everything forever.
Uploading sensitive documents to the knowledge base.
Forgetting about minors.
Skipping the breach plan. A 72-hour clock is short if you’ve never practised.
Treating this as a one-off. Review it whenever the rules or your chatbot change.
FAQ
Does the DPDP Act apply to my website chatbot?
Probably, if it collects or processes personal data about people in India, such as names, phone numbers, emails or chat messages that identify someone. You’d typically be the Data Fiduciary and your chatbot provider the Data Processor.
When do I need to comply?
Most core duties apply from mid-May 2027, 18 months after the Rules were notified on 13 November 2025. A separate milestone for Consent Managers begins in November 2026. MeitY consulted on shortening the timeline for large entities, but trackers hadn’t found a change as of October 2026, so check for updates.
Do I need consent for every chat?
Not necessarily. The Act allows certain “legitimate uses” as well as consent. When you do need consent, it must be free, specific, informed, unconditional and unambiguous. Ask a lawyer which applies to each purpose.
Is my chatbot vendor responsible if something goes wrong?
Both of you may have obligations, but under the Act the Data Fiduciary (you) remains responsible for compliance even when a processor handles the data, and must have a valid contract with the processor.
What happens if there’s a data breach?
You’d need to notify affected individuals without delay and the Data Protection Board, with a detailed report within 72 hours, unless the Board allows longer.
Can my chatbot talk to children?
Processing the data of anyone under 18 generally requires verifiable parental consent, with limited exemptions. If minors might use your chatbot, get specific advice.
Does Glanceia comply with the DPDP Act?
We’d rather you ask than assume. Glanceia’s site says each company’s data is kept in an isolated environment. For specifics like agreements, data location and deletion, ask the team through the contact page. Remember that your own notice, consent and processes are part of compliance too.
Should I hire a lawyer?
For a final privacy notice, consent wording and your vendor contracts, yes, a lawyer who knows Indian data protection law is worth the cost.
Start with the data map
You don’t need to become a privacy expert by May. You need to know what your chatbot collects, tell people clearly, collect only what you need, protect it, delete it on schedule and respond when someone asks. Start with a one-page data map this week.
If you’re looking for a chatbot for your website, Glanceia is free to start with no credit card required. See the docs to get set up, or contact the team with your compliance questions.


