Skip to content
← All articles

Your AI Tools Are Collecting Customer Data — Here's What India's New Privacy Law Means for You

3 November 20265 min read

India's DPDP Rules, 2025 are now in force. If you use an AI voice agent, WhatsApp bot, or personal AI assistant that stores customer data, here is what actually applies to you and when.

Your AI tools already know a lot about your customers

If you've set up an AI voice agent to answer calls, a WhatsApp bot to handle bookings, or a personal AI assistant to manage your calendar and client list, you've quietly built up a pile of personal data: phone numbers, names, call recordings, appointment history, sometimes even payment details. Most small business owners never think about this until something goes wrong.

In November 2025, India finally switched on the rulebook that governs exactly this. The Digital Personal Data Protection (DPDP) Rules, 2025 were notified by the Ministry of Electronics and Information Technology on 13 November 2025, giving teeth to the Digital Personal Data Protection Act that was passed back in 2023. If you run a clinic, a coaching centre, a salon, a property business, or an export firm — and you use any tool that stores customer phone numbers, chats, or recordings — this law applies to you.

What changed, and when

The rules don't all land at once. They roll out in three stages:

  • Immediately (13 November 2025): the Data Protection Board is set up, and the basic definitions and groundwork provisions take effect.
  • After 12 months (13 November 2026): the framework for "Consent Managers" — registered platforms that help people manage their consent across apps — comes into force.
  • After 18 months (13 May 2027): everything else becomes enforceable, including the core rules on notice, security safeguards, and breach reporting that matter most to a small business.

That gives you real runway. You don't need to overhaul anything this week. But the direction is clear, and the habits worth building are cheap to start now and expensive to retrofit later.

The three things that will actually affect you

1. You have to tell customers what you're collecting, in plain language. Under Rule 3 of the new rules, any notice asking for consent must be separate from your terms and conditions, written without legal jargon, and must clearly list what data you're collecting, why, and how someone can withdraw consent later. If your WhatsApp automation or booking bot currently just starts chatting without saying anything about this, that's the gap to close first — a single clear line like "We'll use your name and number to confirm your appointment and send reminders" does most of the job.

2. You're expected to keep the data reasonably secure. The law doesn't demand enterprise-grade security from a ten-person salon chain, but it does expect you to take "reasonable security safeguards." The Schedule to the Act sets the maximum penalty for failing this at up to ₹250 crore — a figure aimed at large platforms with millions of users, not at you, but it signals how seriously the law treats a careless data leak. In practice, this means: know which vendor is storing your call recordings or chat logs, don't let data sit around longer than you need it, and limit who on your team can access customer records.

3. If something leaks, you have to say so, fast. Under Rule 7, a business that suffers a data breach must notify the Data Protection Board "without delay" and send a detailed follow-up report within 72 hours, while also informing every affected customer about what happened and what to do next. Failure to notify a breach carries a separate maximum penalty of up to ₹200 crore under the Act's Schedule. For a small business, the practical takeaway is simpler: know who to call and what to say if your WhatsApp account or voice agent platform is ever compromised, before it happens.

What this doesn't mean

This isn't a reason to drop AI tools or go back to pen and paper. It's also not an immediate compliance deadline — the provisions that matter most to a small business don't bite until May 2027. What it does mean is that "we didn't think about it" stops being a reasonable answer from a legal standpoint, eventually, and in the meantime it's genuinely good business practice: customers increasingly notice when a business is careless with their number or chat history.

A few things worth doing this month

  • Add one plain-language line to your WhatsApp or voice agent greeting explaining what data you collect and why.
  • Ask whoever built or sold you your AI automation where the data is actually stored, and for how long.
  • Delete or archive customer chat and call data you no longer have a business reason to keep.
  • Write down — even in one paragraph — what you'd do and who you'd tell if a data leak happened tomorrow.
  • Avoid collecting more than you need: a booking bot doesn't need to ask for a customer's date of birth or address unless the service actually requires it.

None of this requires a lawyer or a big budget. It requires about an hour of attention, ideally before the next time someone asks you where their data goes.

If you're not sure whether your current WhatsApp automation, voice agent, or AI assistant setup is handling customer data sensibly, message us on the WhatsApp button on this page, or ask for a free 15-minute review — we'll give you a straight answer, not a sales pitch.

Sources

Every figure in this article comes from the sources below. We link to the originals so you can check them yourself.

Want this set up for your business?

Tell us what you need, we reply within 24 hours and can usually quote the same day.

Start a project