Is it safe to put customer data into AI tools under India’s DPDP Act?
What Indian D2C brands should check before putting customer names, phone numbers and order data into AI tools, with practical steps under the DPDP Act.
Anadoris Digital · · 4 min read

AI tools are most useful when they can see real business data: customer messages, order details, reviews, returns. That data usually contains personal information such as names, phone numbers, addresses and sometimes health details. Pasting it into whichever AI tool is handy creates risks for your customers and for your brand.
India’s Digital Personal Data Protection Act sets out how businesses should handle digital personal data, with rules being phased in. You do not need to be a lawyer to act sensibly, but you do need a few habits in place before AI tools touch customer data.
This is general information, not legal advice. Data protection rules and their implementation details can change; confirm your obligations with a qualified adviser.
The principles that matter for AI use
- Purpose: use personal data for the purposes you told customers about, and be careful about new uses they would not expect.
- Minimisation: share only the data a task needs. An AI summarising reviews does not need phone numbers.
- Responsibility: when an AI vendor processes data for you, your brand remains accountable for how it is handled.
- Security: take reasonable steps to protect data, including choosing vendors with sound security.
- Rights: customers can ask about their data and request corrections or erasure, so you should know where it goes.
Choosing AI tools with data in mind
Consumer versions of AI chat tools and business versions often have different data terms. Before using any tool with customer data, read how it stores data, where, for how long, and whether your inputs can be used to train models. Prefer business plans that offer clear contractual terms, the ability to switch off training on your data, access controls and deletion options.
Retention matters as much as storage. Ask how long the tool keeps your inputs and outputs, whether you can delete them, and whether deletion also covers backups and logs. Data kept indefinitely is data that can be exposed later, so shorter retention is usually the safer choice for customer information.
Keep a simple list of every AI tool that touches customer data, what data it receives and why. This helps you answer customer requests, respond to incidents and review vendors later. It is also the first thing an adviser will ask for.
Look at where vendors store and process data, and which other companies they rely on. Many AI tools pass data to an underlying model provider. That is not necessarily a problem, but you should know it, and the vendor’s terms should explain how those providers are bound to protect your data.
Practical habits for the team
- Use approved business tools only; no customer data in personal AI accounts.
- Remove names, phone numbers, emails and addresses before pasting text for analysis, where the task allows.
- Never paste payment details, government ID numbers or passwords into AI tools.
- Treat health information, such as skin conditions or allergies in messages, with extra care.
- Limit who can connect AI tools to your store, inbox or ERP.
- Log which automations send data to which vendor.
- Delete AI conversation history containing customer data when it is no longer needed, where the tool allows.
Customer-facing AI
When AI talks to customers directly, such as a WhatsApp assistant, be open about it. Make your privacy notice clear about the use of automated tools and service providers. Design the assistant to reveal order details only after verifying the customer, and to avoid asking for more information than it needs. Store conversation logs securely, keep them only as long as you need them, and include them when you respond to a customer’s data request.
Breaches and mistakes need a plan too. If an AI vendor reports an incident, or an automation sends data somewhere it should not, you will need to work out quickly what was affected and who must be informed. Knowing which tools receive which data, and having contact details for each vendor, makes that response far faster and calmer.
A data safety checklist
- List of AI tools that receive customer data, with purpose and data fields.
- Data terms checked for each tool, including training use and storage location.
- Business accounts with access controls, not personal logins.
- Personal details removed wherever the task allows.
- Privacy notice updated to cover automated tools and processors.
- A process to handle customer data requests across all tools.
- A plan for what to do if a vendor reports a data incident.
Where to start
Ask your team which AI tools they use and what they paste into them; the answers are often surprising. Build the tool list, move customer data work onto approved business accounts, and write a one-page rule for the team. Then review your privacy notice with an adviser. Anadoris Digital builds AI automations that send only the fields each step needs and keep logs of what went where.
Related service: AI & Automation · More on this topic: AI & Automation articles
