Your shop asks for a phone number. Here is what the law now says.
Clothing stores, electronics showrooms, mobile shops, opticians, supermarkets and multi-brand outlets all collect customer data at the counter. The DPDP Act changes how you may ask for it, use it and keep it. This guide is written for the owner or store manager, not for a lawyer.
Does the DPDP Act apply to my retail store?
Yes. If your store keeps customer details in billing software, a loyalty app, a WhatsApp list or any other digital form, you are a Data Fiduciary under the DPDP Act 2023. Size does not matter. A single neighbourhood shop and a chain of fifty stores have the same core duties.
From 13 May 2027 you need to tell customers clearly what you collect and why, take separate consent before using their numbers for offers, keep the data secure, make opting out easy, delete what you no longer need and have someone who answers privacy questions. One habit needs to change straight away: a customer should never be refused a bill, an exchange or a refund because they did not give a phone number.
Last reviewed by the Decipher compliance practice.
Where a retail store picks up personal data
Picture a busy Sunday in a mid-sized store. A customer buys two shirts and the cashier asks, out of habit, "Sir, mobile number?" The number goes into the billing software and an e-bill arrives by SMS a minute later, sent by a vendor you may never have met. Another customer buys a mixer grinder and fills a warranty card for the brand. A third picks a television on EMI, and the finance company's desk in your store photographs their PAN and Aadhaar. A fourth hands over an old phone in an exchange offer, still full of photos and chats.
In the afternoon a delivery boy takes three addresses for home delivery. The tailoring counter writes names and numbers on alteration slips and then types them into a phone to send "ready for pickup" messages. In the evening, the manager forwards a festive offer to a WhatsApp broadcast list of 2,000 customers from his own phone.
All of this is personal data. Here is where it usually sits.
A multi-brand store adds one more layer. Data flows in from the brands' promoters and out to the brands for warranties and offers. Some of that data is yours, some belongs to the brand, and the line between them is often blurred. Sorting out who owns which data is one of the most useful things a multi-brand retailer can do this year.
How the DPDP Act applies to a retail store
Who is responsible for what
For the data your store collects for its own purposes, such as the billing database, your loyalty programme and your marketing list, your store is the Data Fiduciary (Section 2(i)). The POS company, the e-bill SMS vendor, the loyalty app and your delivery partner are your Data Processors. You may use them only under a contract (Section 8(2)), and you remain responsible for them (Section 8(1)).
Data that a brand's promoter collects on the brand's own form, for the brand's own purposes, belongs to the brand. The brand is the Data Fiduciary for it. Your store should not copy that data into its own lists. In the other direction, when you send a customer's details to a brand to register a warranty, you are sharing data with another Data Fiduciary. Tell the customer this at the time, and send only what the warranty needs.
The EMI desk works the same way. The finance company is a Data Fiduciary in its own right for the loan data. Your staff should not keep copies of the customer's KYC documents "for reference".
The phone number question
In May 2023 the Department of Consumer Affairs advised retailers not to insist on a customer's mobile number as a condition for a sale. It said that refusing a sale, an exchange, a return or a refund because a customer did not share a number is an unfair trade practice under the Consumer Protection Act, 2019. The DPDP Act points the same way. Collect only what you need for the purpose (Section 6(1)), and if a number is not needed to make the sale, it must be optional.
If the customer gives the number for a specific reason, such as an e-bill or a delivery update, you can use it for that reason (Section 7(a)). Using it for offers is a different purpose and needs consent under Section 6, given through a clear action such as ticking an empty box or replying yes.
Notice, consent and withdrawal
Before you ask for consent, give a short notice (Section 5). Rule 3 requires it to be clear on its own, to list what you collect and why, and to explain how to withdraw consent, use their rights and complain to the Board. A small card at the counter, a line on the loyalty sign-up screen and a link in the e-bill message can cover most stores. Withdrawing must be as easy as joining (Section 6(4)). A customer who joined by giving a number at the counter should be able to leave by replying STOP.
Keeping and deleting data
Delete personal data once its purpose is over or the customer withdraws consent, and ask your vendors to do the same (Section 8(7)). The exception is data another law requires you to keep. Tax invoices and the PAN details you record for high-value sales must be kept for the period those laws set. Keep them in your accounts, separate from your marketing list, and use them only for that legal purpose.
Security, breaches and the exchange counter
Section 8(5) and Rule 6 require reasonable security: individual logins, access only for those who need it, logs of access kept for a year, backups and care with devices. A customer list on a manager's personal phone is a weak point, because it leaves the store when the manager leaves.
Old phones and laptops taken in exchange or for repair can hold photos, chats and saved passwords. Ask customers to wipe their devices before handing them over, and wipe them yourself before resale. If a device with customer data on it is lost or misused, that may be a personal data breach.
If a breach happens, you must inform the affected customers and the Data Protection Board (Section 8(6)). Rule 7 asks for a first report without delay and a detailed report within 72 hours.
Children and footfall tracking
Toy stores, school uniform shops and kids' sections often collect a child's name or birthday for clubs and offers. Anyone under 18 is a child under the Act. You need verifiable consent from a parent (Section 9 and Rule 10), and you cannot target advertising at children (Section 9(3)). Footfall tools that track phones or faces are another area to handle with care. If a tool can single out a person, it is processing personal data, and you need a proper legal basis and notice before you use it.
The dates
The DPDP Rules were notified in November 2025. Most duties, including notice, consent, security, breach reporting and penalties, apply from 13 May 2027. Until then, the IT Act rules on sensitive data, such as card and bank details, continue to apply.
What can go wrong for a store
The penalty figures in the Act are ceilings set for the whole economy. The Board will look at the actual harm, the type of data and the steps you took (Section 33(2)). What should worry a store owner is not the headline number but how easily the common problems arise.
A customer who keeps getting offers after asking you to stop can complain. A salesperson who joins a competitor can take your WhatsApp list along. An exchanged phone resold with the previous owner's photos on it can reach social media in a day. A customer turned away at the returns counter for refusing to give a number can go to the National Consumer Helpline today, even before the DPDP penalties start.
| Duty you could break | Maximum penalty | How it could happen to you |
|---|---|---|
| Reasonable security safeguards, Section 8(5) | Up to Rs 250 crore | The customer list lives on staff phones, or an exchanged phone is resold with the old owner's data still on it. |
| Breach intimation, Section 8(6) | Up to Rs 200 crore | A leaked loyalty database is found and fixed, but customers and the Board are never told. |
| Children's data, Section 9 | Up to Rs 200 crore | A kids' club sends targeted offers to children using birthdays collected without a parent's consent. |
| Other duties: notice, consent, withdrawal, erasure, grievances | Up to Rs 50 crore | Billing numbers used for offers without consent, no working opt-out, or a deletion request ignored. |
These are the upper limits in the Schedule to the Act. The Board decides the actual amount after looking at how serious the breach was, how long it lasted, the type of data, whether it was repeated and what you did to limit the harm (Section 33(2)).
How a store can put this right
Start with the counter, because that is where most data comes in. Then sort out who owns which data, tighten security on phones and devices, and put a simple process in place for questions and problems. A single store can finish most of this in a few weeks. A chain should do it store by store, using the same notices everywhere.
Fix the counter
Draw the lines with brands and partners
Secure people, phones and devices
Keep only what you need
Handle children's data carefully
Be ready for questions and breaches
The DPDP checklist for retail stores.
Every step above on one printable page, with tick boxes. Pin it up in the office, or hand it to the person who looks after your data. We email you the link, and a short note when the rules change.
How dcomply can help
A single store can work through this list with a few hours of effort and a firm word with staff. Multi-brand retailers and chains usually find the brand and vendor side takes longer, because it means reading contracts and agreeing terms with partners.
In a DPDP Readiness engagement we map data across your stores, brands and vendors, write your counter notices and consent wording in the languages your customers read, review partner contracts and hand you a plan you can finish before May 2027. A named practice lead stays on your file throughout.
DPDP Readiness starts at Rs 49,999 plus GST, a fixed fee for two weeks of work. See all prices.
Questions retail stores ask us
Can a store refuse a return if I do not give my phone number?
No. The Department of Consumer Affairs advised in May 2023 that refusing a sale, exchange, return or refund because a customer did not share a mobile number is an unfair trade practice. You can still be asked for a bill or other proof of purchase.
Do I need consent to send an e-bill by SMS?
If the customer chose an e-bill and gave the number for it, you can use the number for that bill (Section 7(a)). You need separate consent to use the same number for offers.
A brand promoter in my store collects customer data. Am I responsible?
If the promoter collects it on the brand's form for the brand's purposes, the brand is the Data Fiduciary. Put that in writing with the brand, and make sure the data does not mix with your own records.
Can I keep a copy of the customer's PAN for big purchases?
Yes, where the Income Tax Rules require you to record it, and only for that purpose. Store it with your accounts, limit access, and do not use it for anything else.
Do I need a Data Protection Officer?
Only if the government notifies your business as a Significant Data Fiduciary, which is unlikely for most stores. You still need a named contact for privacy questions, published on your bills or website (Section 8(9)).
Is it fine to run WhatsApp offers from the store manager's phone?
It is risky. The list leaves with the manager, you cannot control who sees it and you cannot easily prove consent or honour opt-outs. Move it to a business account the store controls.
When does all this start?
Most DPDP duties apply from 13 May 2027. The DoCA advice on phone numbers applies already, under the Consumer Protection Act.
Where these facts come from
Primary sources, checked on 18 November 2026. This guide explains the law in plain words. It is not legal advice for your specific situation.
- Digital Personal Data Protection Act, 2023 (MeitY)
- Digital Personal Data Protection Rules, 2025 (MeitY)
- PIB explainer on the DPDP Rules, 17 November 2025
- Data Protection Board of India portal
- DPDP Act, section by section (dpdpa.dcomply.in)
- Business Standard: Government asks retailers not to insist on mobile numbers (23 May 2023)
Related guides
Last reviewed by the Decipher compliance practice.