What does the DPDP Act mean for D2C customer data in the cloud?
A practical overview of India's DPDP Act for D2C brands storing customer data in the cloud: consent, security, breaches, retention, vendors and where to start.
Anadoris Digital · · 4 min read

D2C brands collect a lot of personal data: names, phone numbers, addresses, email addresses, order history, and sometimes birthdays, skin or hair concerns, or sizes. That data flows through Shopify, payment gateways, courier partners, marketing tools, your own databases and cloud storage. The Digital Personal Data Protection Act, 2023, together with the rules made under it, sets out how businesses must handle such data.
This article is a practical overview for founders, not legal advice. The rules are being brought into force in phases, and obligations depend on your business, so confirm details with a qualified adviser. What follows focuses on the cloud and systems side: the things your technology setup needs to support.
Laws, rules and their commencement dates change. Check the current text of the Act and its rules, and take legal advice before relying on any summary, including this one.
Key ideas in plain language
- Data principal: the customer whose data it is.
- Data fiduciary: your brand, which decides why and how the data is processed.
- Data processor: vendors that process data on your behalf, such as cloud providers, email tools and couriers.
- Notice and consent: customers should be told what you collect and why, and consent should be clear and easy to withdraw.
- Security safeguards: you must take reasonable steps to protect data, including at your processors.
- Breach notification: personal data breaches must be reported to the Data Protection Board and affected people, as the rules set out.
- Rights: customers can ask to access, correct or erase their data and to have grievances handled.
Using a cloud provider does not move responsibility
When you store customer data in AWS, AWS is responsible for the security of its infrastructure, but you remain responsible for how your account is configured and how data is used. This is often called the shared responsibility model. A public S3 bucket, a database open to the internet or a leaked key are your responsibility, not your cloud provider's. The same applies to every vendor that handles your customers' data: you should know who they are and have suitable agreements in place.
What your cloud setup should support
- A data map: what personal data you hold, in which systems and regions, and why.
- Encryption at rest and in transit for databases, storage and backups.
- Least-privilege access, multi-factor login and access reviews.
- Logging of who accessed or changed data, kept securely.
- Retention rules that delete or anonymise data you no longer need.
- The ability to find, export, correct and delete a specific customer's data across systems.
- Incident response steps for suspected breaches, including who decides on notification.
- Masked or synthetic data in staging, not raw customer data.
Marketing data and consent
Marketing is where many D2C brands collect the most data and the least clear consent. Pop-ups, quizzes, WhatsApp opt-ins and contests should say plainly what data is collected and how it will be used, and let people withdraw easily. Your systems should record when and how consent was given and honour withdrawals across all tools, not just one. Keep data collected for one purpose from quietly being reused for another without a proper basis. Exports of customer lists into spreadsheets for campaigns are a common weak point; limit who can create them and delete them when the campaign ends.
Data location
The Act allows transfers outside India except to countries the government may restrict, while some sectors have their own localisation rules. Many Indian brands choose to keep customer data in AWS Mumbai or Hyderabad as a sensible default and to simplify conversations with partners. Location alone does not make you compliant; consent, security and rights handling matter more.
Vendors and data processors
Most of a D2C brand's customer data is handled by vendors: the commerce platform, payment gateway, couriers, marketing and messaging tools, helpdesks and analytics. Each one processes data on your behalf, and you remain accountable for choosing them carefully. Keep a list of vendors that receive personal data, what they receive and why, and check their security and data processing terms.
Limit what you share. A courier needs a name, phone number and address, not purchase history. An analytics tool rarely needs names at all. When you stop using a vendor, ask for your data to be deleted and remove any connections or keys. These habits reduce your exposure and make it easier to answer customer requests accurately, because fewer systems hold copies of the same data.
Where to start
Build a simple data map this month: list every system that holds customer data, what it holds, where it is hosted and who can access it. Fix the obvious risks first, such as public buckets, shared logins and unencrypted backups. Write down how you would find and delete one customer's data across all systems. Then review your notices, consent flows and vendor agreements with a qualified adviser.
Related service: AWS & Cloud Management · More on this topic: AWS & Cloud Management articles
