Key takeaways
- A guest’s name, mobile number, email, birthday and order history are personal data. The PDPA applies to how your outlet collects, uses, discloses and looks after them.
- Tell guests why you are collecting their data before you collect it. Don’t make marketing consent a condition of ordering, and use an unticked opt-in box for marketing.
- Marketing sent to Singapore numbers by SMS, calls or WhatsApp falls under the Do Not Call rules. See our WhatsApp templates for restaurants for examples. Either hold clear and unambiguous consent, or check the DNC Registry within 21 days before sending.
- PDPC’s guidelines say organisations are generally not allowed to collect NRIC numbers. Use a mobile number or email for loyalty accounts instead.
- Appoint a Data Protection Officer and publish their contact details. If a breach is notifiable, PDPC must be told within 3 calendar days of that assessment.
This is general information, not legal advice. It summarises guidance published by the Personal Data Protection Commission (PDPC), checked in September 2026, and applies it to typical restaurant, café and bar situations. PDPC guidance is updated from time to time, so read the linked sources and speak to a qualified adviser for your specific circumstances.
Does the PDPA apply to your restaurant?
Almost certainly. PDPC’s PDPA overview describes personal data as data about an individual who can be identified from that data, or from that data and other information the organisation has or is likely to have access to. It covers data in electronic and non-electronic formats, so a paper reservation book counts as much as your CRM.
In a typical F&B outlet, personal data turns up in:
- loyalty and membership sign-ups (name, mobile, email, birthday)
- QR ordering and online orders (mobile number for order updates, email for receipts)
- reservations and queue systems (name, mobile, party size, notes such as allergies)
- delivery orders you fulfil yourself (address and phone number)
- CCTV footage of guests and staff
- feedback forms (see our customer feedback guide), lucky draws and event sign-ups
The overview notes the PDPA generally does not apply to business contact information, such as someone’s work phone and title. So a supplier’s office number is treated differently from a diner’s personal mobile.
The core obligations: consent, purpose and notification
PDPC’s Advisory Guidelines on Key Concepts in the PDPA (revised 29 April 2026) explain the main obligations. Three matter most at the point where you collect data from guests.
Notification
Under section 20, you must tell the individual the purposes for collecting, using and disclosing their personal data on or before collecting it. For a loyalty form, that means the purpose sits on the form itself, not in a policy nobody sees.
Consent
You generally need consent for those purposes. The guidelines make two points that matter for F&B:
- Don’t over-reach. Section 14(2) says you must not, as a condition of providing a product or service, require consent beyond what is reasonable to provide it. You can ask for marketing consent, but a guest should be able to order or join a basic programme without agreeing to extra uses such as sharing their data with third parties. The guidelines do say that offers, discounts or lucky draws may be made conditional on data use for specified purposes, as long as those purposes are reasonable.
- Marketing needs opt-in. The guidelines say deemed consent by notification does not apply to sending direct marketing messages. Organisations should generally get express consent through an opt-in, such as an unchecked box the person ticks. PDPC does not consider a pre-checked box appropriate for marketing consent.
Guests can withdraw consent at any time (section 16). When they do, you must stop using their data for that purpose and make sure your service providers stop too.
Purpose limitation
Section 18 limits you to purposes a reasonable person would consider appropriate and that you have told the individual about. PDPC’s own example is a retailer’s membership form that allows use for “any other purpose that it deems fit”; the guidelines say that wording would not be considered reasonable. Name your real purposes: managing membership points, sending order updates, sending promotions if they opt in.
Marketing by SMS, calls and WhatsApp: the DNC rules
The Do Not Call (DNC) provisions are part of the PDPA. According to PDPC’s Organisation’s Guide to Singapore’s DNC Provisions and its Advisory Guidelines on the DNC Provisions:
- What’s covered. “Specified messages” are marketing messages, such as ones that advertise or promote goods or services. The advisory guidelines state that the rules apply to voice calls, SMS and data applications such as WhatsApp, iMessage or Viber that use a Singapore telephone number.
- Check or get consent. Before sending a specified message to a Singapore number, check it against the DNC Registry. The check must be made within 21 days before sending. You don’t need to check if you have the person’s clear and unambiguous consent to receive the message.
- What counts as consent. PDPC’s guide says consent should not be hidden in general terms and conditions, and must be in a form you can refer to later: written, electronic or another accessible form.
- Mixed messages count. A service message with any marketing element is still a specified message. PDPC gives examples such as a delivery update that includes a discount code, or an order confirmation that offers a referral bonus.
- Ongoing relationship. Messages related to the subject of an ongoing relationship may not need a DNC check. The advisory guidelines give examples for existing rewards programme members, including a birthday-month discount message. But PDPC says one-off transactions are not enough to create an ongoing relationship, so a one-time diner is not the same as a loyalty member.
- Identify yourself. Marketing messages must include information identifying the sender and how the recipient can contact you.
- Make opting out easy. PDPC’s guide suggests including instructions such as “Reply UNSUB to stop receiving messages”. The advisory guidelines set 21 days as the period within which you must give effect to a withdrawal of consent for DNC purposes. Treat that as a deadline, not a target.
If you need to check numbers, PDPC’s DNC Registry checking page lists a one-time account set-up fee of S$32.70 including GST for Singapore-registered organisations, 1,000 free credits a year per main account, and results valid for 21 days. It also explains how to buy extra credits.
For a restaurant, the simplest approach is to collect clear opt-in consent for WhatsApp and SMS promotions at sign-up, keep a record of it, and put an opt-out line in every broadcast. Our restaurant marketing guide has more on consent-based WhatsApp campaigns.
Don’t collect NRIC numbers
PDPC’s Advisory Guidelines on the PDPA for NRIC and Other National Identification Numbers say organisations are generally not allowed to collect, use or disclose NRIC numbers or copies of NRIC, unless it is required under the law or it is necessary to verify identity to a high degree of fidelity. The same treatment applies to birth certificate numbers, FINs and work permit numbers, and the guidelines ask organisations to treat passport numbers in a similar way. The document notes it will be updated following a December 2024 government statement on NRIC use, and that PDPC advises against organisations using NRIC numbers to authenticate identity.
What this means for F&B:
- Loyalty accounts: PDPC’s retail membership example suggests using mobile numbers, email addresses or a user-generated ID instead.
- Lucky draws with valuable prizes: the guidelines accept partial NRIC numbers (up to the last three digits and checksum, such as “567A”) for verifying winners. Partial numbers are still personal data and need protecting.
- Feedback forms and pre-orders: collect names and contact details, not NRIC numbers.
If an old membership form or spreadsheet still has an NRIC field, remove it and review the data you already hold.
Loyalty, QR ordering, reservations and WhatsApp in practice
| Touchpoint | Typical data | What to do |
|---|---|---|
| Loyalty sign-up | Name, mobile, email, birthday | State the purposes on the form. Separate, unticked opt-in for marketing by each channel you use. Collect only the birthday detail you need (day and month may be enough for a birthday reward). |
| QR ordering and online orders | Mobile or email for order status and receipts | Use the number for the order unless the guest opts in to marketing. Don’t add promotions to order updates for guests who haven’t opted in. |
| Reservations and queue | Name, mobile, party size, notes | Use the number for confirmations, reminders and queue calls. Keep allergy and health notes need-to-know. |
| WhatsApp and SMS marketing | Mobile number, consent record | Send only to opted-in guests or DNC-checked numbers, identify your outlet, include an opt-out, and act on opt-outs promptly. |
| Own delivery | Address, mobile | Share only what the courier needs to deliver. |
A reservation or queue confirmation that is purely about the booking is a service message. Adding “and 20% off your next visit” turns it into marketing, which brings in the DNC rules. Our guide to reducing no-shows covers reminder messages, and loyalty programme ideas covers birthday and win-back offers.
CCTV in your outlet
PDPC’s Advisory Guidelines for Selected Topics (CCTV section updated in 2022) say that for CCTVs in areas open to the public, where people can reasonably expect cameras, organisations can rely on the publicly available exception to consent. It is still good practice to put up notices that the area is under CCTV surveillance. For areas not open to the public, such as back-of-house, an organisation may rely on the legitimate interests exception. That means doing a risk assessment and telling people it relies on the exception, for example in its data protection policy. PDPC again recommends notices. For workplaces, the guidelines suggest telling employees through the staff handbook or HR policies.
The guidelines include a karaoke (KTV) example: showing footage from private rooms in open areas needed patrons’ consent, obtained through the room terms and notices inside the rooms. The lesson for F&B is to use CCTV for security and safety, put up clear notices, and think carefully before using footage for anything else, such as posting clips on social media. Guests can also ask for access to footage of themselves, so decide who handles those requests. For a fuller walk-through, see PDPA rules for CCTV in restaurants and shops.
Staff access, security and retention
PDPA obligations are the business’s responsibility, but your staff are the ones who handle the data every day.
- Need-to-know access. Cashiers may need to look up a member by phone number. They rarely need to export the full customer list. Use staff permissions in your POS and CRM so exports, bulk messaging and data deletion sit with a manager or owner.
- No shared logins. Individual logins let you see who accessed or changed what.
- Protection. The Key Concepts guidelines say organisations must make reasonable security arrangements. PDPC has published an enforcement decision issuing a warning to Watami Food Service Singapore for failing to make reasonable security arrangements to prevent unauthorised access to employees’ personal data stored online. Staff data is personal data too.
- Retention. The guidelines say the PDPA does not set a fixed retention period. Keep personal data only while it serves the purpose you collected it for or a legal or business purpose, and don’t keep it “just in case”. Review what you hold regularly: for example, lapsed member records, old reservation notes and exported spreadsheets on personal devices.
- Access requests. Guests can ask what data you hold about them. The guidelines say to respond as soon as reasonably possible. If you can’t respond within 30 days, you must tell the individual in writing within that time when you will be able to.
- Vendors. Your POS, CRM, reservation and messaging providers may process data for you. Under the Key Concepts guidelines, a data intermediary must notify the organisation it works for of any data breach it detects. Check your contracts cover this.
ChaChaCha’s POS includes staff permissions, and our CRM and loyalty tools cover points and stamps, stored value, vouchers, birthday rewards and WhatsApp marketing. Before you choose any system, including ours, ask the vendor where customer data is stored, who on their side can access it, and how consent and opt-outs are recorded. Get the answers in writing; ask us and we will walk you through it.
Your DPO and data breach notification
Appoint a Data Protection Officer
PDPC’s Getting Started as a DPO page calls appointing a DPO the “mandatory first step” in complying with the PDPA. The Key Concepts guidelines explain that the PDPA requires organisations to designate one or more people responsible for compliance, and that legal responsibility stays with the organisation. You must make the DPO’s business contact details publicly available, either by registering them with PDPC or publishing them on your website. For a small restaurant group, the DPO is often the owner or operations manager.
When a breach must be reported
According to PDPC’s data breach reporting page, a breach is notifiable if it is likely to result in significant harm to individuals, or if it affects 500 or more individuals. If it is notifiable:
- notify PDPC as soon as practicable, and no later than 3 calendar days after determining the breach is notifiable;
- notify affected individuals where the breach is likely to cause them significant harm, after or at the same time as PDPC, unless an exception applies.
The Key Concepts guidelines add that you should assess a suspected breach quickly, generally within 30 calendar days, and document the steps you take. PDPC recommends its C.A.R.E. approach: contain, assess, report, evaluate. F&B examples include a lost tablet with the member list, a CSV of customer numbers shared in the wrong WhatsApp group, or a hacked online ordering account.
Penalties
PDPC’s enforcement page says it can direct organisations to stop collecting or using data, destroy unlawfully collected data, provide access or correction, or pay a financial penalty. Its DPO page states that organisations may face fines of up to S$1 million or 10% of annual Singapore turnover (for turnover above S$10 million), whichever is higher. The cost to your reputation can be just as damaging.
Sample consent wording and a practical checklist
Example only, not legal advice. Adapt it to your outlet and have it reviewed.
Sample loyalty sign-up notice:
“We collect your name, mobile number, email and birthday (day and month) to set up and manage your [Outlet] membership, record your points and rewards, and contact you about your account. Read our privacy policy at [link]. Questions? Contact our Data Protection Officer at [email].”
Separate opt-in boxes, left unticked by default:
- ☐ “Yes, send me promotions and offers from [Outlet] by WhatsApp and SMS.”
- ☐ “Yes, send me promotions and offers from [Outlet] by email.”
Sample message footer: “From [Outlet], [phone/email]. Reply UNSUB to stop promotional messages.”
Checklist
- Appoint a DPO and publish their business contact details.
- List every place you collect personal data: forms, QR ordering, reservations, queue, Wi-Fi, CCTV, feedback.
- Remove NRIC fields; use mobile, email or a member ID instead.
- Put a short purpose notice at each collection point.
- Use unticked, channel-specific opt-in boxes for marketing, and record when and how consent was given.
- Keep service messages free of promotions for guests who haven’t opted in.
- Check the DNC Registry within 21 days before messaging anyone without clear consent.
- Add sender details and an opt-out line to every marketing message, and give effect to opt-outs promptly.
- Put up CCTV notices and tell staff about workplace cameras.
- Set staff permissions so only managers can export or bulk-message customer data.
- Set a retention schedule and delete data you no longer need, including old exports.
- Write a one-page breach plan: who to call, how to assess, and the 3-day notification deadline.
- Check vendor contracts cover security and breach notification.
- Brief new staff on the basics during onboarding.
Moving systems? Our guide to switching POS covers moving customer data safely.