What the DPDP Act means for your restaurant.
Every restaurant in India collects personal data, usually without noticing. A phone number at billing, a name for a table, a Wi-Fi login, a face on CCTV. From 13 May 2027 the DPDP Act decides what you can do with it. This guide explains what changes and what to do, in the order a restaurant owner would actually do it.
Does the DPDP Act apply to my restaurant?
Yes, if you keep any customer or staff information in digital form. That includes phone numbers in your billing software, booking details, Wi-Fi login records, digital CCTV footage and staff records. There is no exemption for small restaurants. Your restaurant is the "Data Fiduciary" for this data, which means you decide why it is collected and you are responsible for it.
Most duties apply from 13 May 2027. By then you need a clear notice wherever you collect data, separate consent before you use phone numbers for offers, reasonable security for your systems, a contact person for privacy questions and a plan for data breaches. You also need to delete data you no longer need. A small restaurant can do most of this in a few weeks without buying any software.
Last reviewed by the Decipher compliance practice.
How a restaurant collects personal data in one ordinary day
Think about a normal Saturday. A family books a table for eight on the phone, and the manager types the name and number into the booking system. At the door, the host asks for a phone number to put another group on the waitlist. The guests join the free Wi-Fi, which asks for a mobile number and sends an OTP. At billing, the cashier asks for a number "for the bill and points". Someone scans the QR code on the table to leave feedback. On the way out, the camera at the entrance records every face.
Meanwhile the kitchen is sending out delivery orders. Each order comes with a customer name and address. Some come through the aggregator apps, some through your own website or WhatsApp. That evening someone in the office sends a "Happy Weekend, 20% off" message to the whole customer list.
None of this feels like handling data. But every one of these steps collects personal data, and the DPDP Act covers all of it once it is in digital form. Here is where it usually sits in a restaurant.
One detail matters here. Paper records sit outside the Act until they are typed, scanned or photographed (Section 3). A handwritten booking diary is not covered. The moment someone copies those numbers into a phone or a spreadsheet, it is. In most restaurants today, almost everything ends up digital sooner or later.
How the DPDP Act applies to a restaurant
You are the Data Fiduciary
The Act calls the business that decides why and how personal data is used the "Data Fiduciary" (Section 2(i)). For your booking list, your billing database, your marketing list and your CCTV, that is you. It does not matter whether you are a sole proprietor, a partnership or a company, or whether you run one outlet or twenty. The Act has no exemption based on size.
Your software and service vendors are "Data Processors" when they handle data on your behalf. The POS company, the Wi-Fi vendor, the WhatsApp marketing agency and the CCTV cloud provider all fall here. You can use them, but only under a contract (Section 8(2)), and you stay responsible for what they do with your customers' data (Section 8(1)).
Delivery aggregators are different. They collect the customer's data themselves and decide how to use it, so for that data they are Data Fiduciaries in their own right. Your duty covers what you do with the order details they pass to you.
When you can use data without asking again
Section 7(a) is the most useful rule for a restaurant. If a customer gives you their data for a specific purpose and does not say they object, you can use it for that purpose. A guest who gives a phone number to book a table can be called about that booking. A delivery customer has given you the address so you can deliver the food. For staff, Section 7(i) allows you to use their data for employment purposes, such as payroll and attendance.
What Section 7(a) does not cover is using the same number for something else. A booking number does not become a marketing number on its own. For offers, festival greetings and "we miss you" messages, you need consent under Section 6. That consent must be free, specific and clear, and it must come from an action by the customer, such as ticking a box that was not ticked in advance.
The notice
When you ask for consent, you must give a notice first (Section 5). Rule 3 says the notice must make sense on its own, without the customer having to open a long privacy policy. It must list the data you collect and why, and explain how to withdraw consent, how to use their rights and how to complain to the Board. You can give it in English or in any language in the Eighth Schedule of the Constitution. For a restaurant, this can be a few lines on the Wi-Fi login page and the online booking form, and a small card at the counter.
Withdrawal and deletion
Withdrawing consent must be as easy as giving it (Section 6(4)). If a guest opted in with one tap, they should be able to opt out with one tap or one reply. Once the purpose is over, or the customer withdraws consent, you must erase the data and have your vendors erase it too (Section 8(7)), unless another law needs you to keep it. Tax laws require you to keep invoices for several years, so you keep the invoice. You do not need to keep that customer on your marketing list.
Security and breaches
You must take reasonable security safeguards to prevent a breach (Section 8(5)). Rule 6 explains what that means in practice: control over who can access data, encryption or masking where it makes sense, logs of who accessed what, backups, and keeping those logs for a year. If a breach happens, say a laptop with the customer list is stolen or someone leaks the database, you must tell the affected customers and the Data Protection Board (Section 8(6)). Rule 7 asks for a first report to the Board without delay and a detailed one within 72 hours.
Children
If you run birthday packages or kids' clubs and collect a child's name and birth date, that is a child's personal data. The Act treats anyone under 18 as a child. You need verifiable consent from a parent before you process it (Section 9 and Rule 10), and you cannot target advertising at children (Section 9(3)). In practice, take such details from the parent, use them for the event only, and keep them out of your marketing list.
The dates
The DPDP Rules were notified in November 2025. The Consent Manager provisions started on 13 November 2026. Most of the duties above, including notice, consent, security, breach reporting and the penalties, apply from 13 May 2027. Until then, the older IT Act rules on sensitive data, such as card and bank details, still apply.
What happens if a restaurant ignores it
The penalties in the DPDP Act are large because one law covers every business in India, from a dhaba to a hotel chain. Nobody expects a 40-cover cafe to pay Rs 250 crore. But the Board looks at what happened, what kind of data was involved and what you did about it. A business that never thought about data at all will find that hard to explain.
The realistic risks for a restaurant are everyday ones. A customer keeps getting offers after asking you to stop. A former employee walks off with the customer list. The CCTV recorder is stolen with weeks of footage on it. Your Wi-Fi vendor's server is hacked. From May 2027, each of these can become a complaint the Board can act on. Each one also costs you goodwill in the neighbourhood, which matters more to most restaurants than any fine.
| 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 database sits on a shared laptop with no password, or a former manager still has a POS admin login. |
| Breach intimation, Section 8(6) | Up to Rs 200 crore | Your customer list leaks and you quietly fix it without telling customers or the Board. |
| Children's data, Section 9 | Up to Rs 200 crore | You send birthday offers to children whose details you took for a party, without a parent's consent. |
| Other duties: notice, consent, withdrawal, erasure, grievances | Up to Rs 50 crore | You send offers to booking numbers without consent, give no way to unsubscribe, or ignore a request to delete data. |
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 restaurant can get this right
You do not need expensive software for most of this. You need a clear picture of what you collect, a few honest notices, one person who owns the topic and some discipline with your vendors. Work through the steps below in order. Each one names the section or rule behind it, so you can check our reading yourself.
Map what you collect
Fix how you ask
Sort out your vendors
Secure the systems
Keep only what you need
Be ready for questions and problems
The DPDP checklist for restaurants.
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
Most restaurants can work through the checklist above on their own, and we would rather you did that than leave it for later. Some owners prefer to hand it over, especially chains with several outlets, cloud kitchens with their own ordering apps and restaurants that run large loyalty programmes.
In a DPDP Readiness engagement we map your data across outlets and vendors, write your notices and consent wording, review your vendor contracts and give you a plan in order of priority that you can finish before May 2027. A named practice lead stays with you from the first call to sign-off.
DPDP Readiness starts at Rs 49,999 plus GST, a fixed fee for two weeks of work. See all prices.
Questions restaurants ask us
Can I ask customers for their phone number at billing?
You can ask, but do not make it a condition for giving the bill. In May 2023 the Department of Consumer Affairs advised retailers that insisting on a mobile number before a sale is an unfair trade practice. Under the DPDP Act, if you want to use the number for offers, you also need separate consent.
We have only one outlet. Does the Act still apply?
Yes. The Act has no exemption for small businesses. The extra duties for Significant Data Fiduciaries, such as appointing a Data Protection Officer and annual audits, will not apply to a typical restaurant. The core duties do.
Do we need a Data Protection Officer?
Not unless the government notifies you as a Significant Data Fiduciary, which is unlikely for a restaurant. You do need a named person who can answer customers' questions about their data, and you must publish that contact (Section 8(9)).
Is CCTV footage covered?
Yes. Digital footage that shows identifiable people is personal data. The DPDP Act has no general "legitimate interest" ground like Europe's GDPR, so the exact legal basis for filming customers is not settled yet. Until the Board or the government gives guidance, the safe course is a clear notice at the entrance, cameras only where you need them, short retention and tight control over who can view or copy footage.
The aggregator gives us the customer's name and address. Can we add them to our marketing list?
Not without the customer's consent. The details reached you so you could deliver an order. Marketing to that customer is a new purpose. Your contract with the aggregator may also forbid it.
Our guest Wi-Fi is run by a vendor. Who is responsible?
Usually you are the Data Fiduciary and the vendor is your Data Processor, so you must make sure the vendor protects the data. Check the contract, ask where login data is stored and for how long, and put a short notice on the login page.
When do we actually need to be ready?
Most duties apply from 13 May 2027. It is easier to spread the work over a few months than to rush it in the last weeks, especially if you need to change POS settings or vendor contracts.
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.