Przejdź do treści
Finance & Risk in Foodservice

GDPR in Restaurants 2026: QR, WhatsApp, Mail

Author: Updated: 10 min read
GDPR in Restaurants 2026: QR, WhatsApp, Mail

QR menus, WhatsApp reservations and mailing: three places where a restaurant processes guests' data. Legal bases, consents and a checklist.

A customer sits down at a table, scans a QR code and opens the menu in their browser. Then they write to the restaurant on WhatsApp: "do you have lactose-free coffee?" (and you should know how to mark allergens on a menu correctly). After they leave, you save their number in your newsletter database. From the guest's point of view, it is a convenient service. From the GDPR point of view - 3 separate processes of processing personal data, each requiring its own legal basis and its own information notice for the customer.

This post does not explain GDPR from scratch. It shows 3 typical points where your restaurant touches a guest's personal data, where mistakes are easy, and what exactly to change to stay on the right side of an inspection by UODO (the Polish data protection authority). It is another topic from the area of finance and risk in foodservice, where an oversight can end in a fine.

Touchpoint 1: QR menu and the duty to inform

The customer scans a QR code leading to the menu on your website. The page loads in their browser. What happens under the hood:

  • Google Analytics or another tracker records the visit (IP address, device type, approximate location).
  • Your server saves the customer's IP address in its logs (how long the logs are kept depends on the server configuration).
  • If you run Facebook/Google Ads remarketing, the customer is "tagged" and their data goes to the advertising platform.

Each of these processes is processing of personal data. The customer has the right to know that it is happening, why, and who the controller is. In practice, a QR menu page needs:

  1. A consent mechanism for cookies and similar technologies that are not necessary for the page to work (e.g. analytics and advertising): Art. 399 of the Act of 12.07.2024 - Electronic Communications Law requires prior information and consent, except where access to information is necessary to provide a service requested by the user.
  2. Information for visitors about the processing of their data (Art. 13 GDPR); its form, e.g. a privacy policy with a visible link in the footer, is a matter of practice.
  3. The information under Art. 13 GDPR covers, among other things, the controller's details (your company), the purposes and legal basis of processing, the recipients of the data (e.g. the analytics tool provider), the retention period and the rights of the data subject.

A menu page without cookie information and without the information required by Art. 13 GDPR breaches the rules. Administrative fines for infringing the rights of data subjects (Art. 12-22 GDPR) can reach EUR 20 million or 4% of annual worldwide turnover, whichever is higher (Art. 83(5) GDPR); for infringing the controller's obligations under Art. 25-39, up to EUR 10 million or 2% of turnover (Art. 83(4)). The authority sets the specific amount in each case, using the criteria in Art. 83(2); we found no reliable data on typical fines for small foodservice businesses, so we do not give any. Remember that a financial penalty for non-compliance is only one of the costs - also check how much it costs to have no HACCP documentation, because both inspections can overlap.

Touchpoint 2: WhatsApp for guests

More and more restaurants use WhatsApp to communicate with guests: reservation confirmations, the daily menu, takeaway pickup. From the GDPR point of view:

  • The customer's phone number is personal data.
  • Saving it in your contacts or in a spreadsheet is processing.
  • Sending the message "Today we recommend carbonara" to a list of customers who once booked a table is marketing - and requires separate consent (consent to handle the reservation is not enough). Using telecommunications terminal equipment, including interpersonal communications services, to send commercial information without the recipient's prior consent is prohibited (Art. 398(1) of the Electronic Communications Law).

A practical path:

  1. Operational WhatsApp (reservation confirmations, replies to the customer). The customer makes contact first. Your legal basis: necessity for the performance of a contract (the reservation). No separate consent is required.
  2. Marketing WhatsApp (newsletter about your offer). Requires explicit consent. "Would you like to receive information about the seasonal menu?" when booking. Without "Yes" ticked - you do not send.
  3. The contact list on a waiter's phone. If a waiter keeps their contacts with guests on a private phone, it is still guest data processed as part of your business, for which the controller, that is the company, is responsible; a person processing data on the controller's instruction acts on the controller's authorisation (Art. 29 GDPR), and a private phone makes it harder to control that data. Best practice: WhatsApp Business on a company number, managed centrally.

Touchpoint 3: Mailing list and marketing

A customer left their email when booking online (via ResDiary, TheFork or your own form). You entered it in an Excel sheet called "regular customers". What next:

Without consent to receive commercial information, you cannot send them a Christmas offer (Art. 398(1) of the Electronic Communications Law; we did not check the provisions of the Act on Providing Services by Electronic Means). You can only: operational contact related to a specific reservation.

If you want to send a newsletter with the seasonal menu, you must have for each customer:

  1. Consent to receive marketing (a separate checkbox, not "together with the privacy policy"; Art. 7(2) GDPR requires that the request for consent be clearly distinguishable from other matters).
  2. The option to opt out: withdrawing consent must be as easy as giving it (Art. 7(3) GDPR); an "unsubscribe me" link in every message is common practice.
  3. A record of the consent: you must be able to demonstrate that the person gave it (Art. 7(1) GDPR). The date, the wording of the consent and the way it was obtained are the practical minimum; the IP address is a common additional piece of evidence, but the provision does not require it.

An Excel sheet of regular customers without these elements is a risk of breaching the rules. An alternative is newsletter tools (e.g. Mailchimp, Brevo, ConvertKit), many of which let you store consent records; we did not compare their features, so check whether the tool you choose allows this, and conclude a data processing agreement with the provider (Art. 28 GDPR). Keeping GDPR consent registers requires similar discipline to keeping HACCP registers - in both cases what counts is consistency and dates.

GDPR checklist for foodservice

A GDPR checklist for a small restaurant (as of 2026):

  1. Check your QR menu page. Does it have a cookie banner? A privacy policy in the footer? If not, add them. A privacy policy generator can help, but its content must match the actual processes in your venue (Art. 13 GDPR).
  2. Check your WhatsApp. Do you have a separate company number (WhatsApp Business), or do you use a private one? If private, switch to a company one. Set up an automatic welcome message with a link to the privacy policy.
  3. Check your mailing list. Did customers give explicit consent to marketing? If not, send a re-permission email ("reminder - do you still want our newsletter, click here if yes"). Customers who do not click - you remove from the list.
  4. Check your privacy policy. Does it list all the processors (Google Analytics, ResDiary, Mailchimp, website hosting)? Update it if any are missing.
  5. Appoint a person responsible for GDPR in the venue (usually the owner or the manager). This person can handle incidents (e.g. a database leak), customer enquiries ("what do you know about me") and contact with UODO; however, legal responsibility remains with the controller, that is the company.

Frequently asked questions

Does a small restaurant have to have a Data Protection Officer (DPO)?

Usually not. GDPR (Art. 37) contains no numerical threshold - the obligation to appoint a DPO depends on the nature of the processing: it applies to public authorities and to entities whose core activity consists of regular and systematic monitoring of people on a large scale or of large-scale processing of special categories of data (e.g. health data). A typical restaurant meets neither condition, so it does not have to have a DPO - but it is worth appointing a person responsible for GDPR, typically the owner or the manager.

Are images from CCTV in the venue personal data?

Yes, an image recorded on a video is personal data. CCTV monitoring requires a legal basis (most often the controller's legitimate interest, Art. 6(1)(f) GDPR, for the purpose of protecting security), informing the people recorded in line with Art. 13 GDPR (in practice a sign or pictogram plus the full information being available) and limiting the retention period of the recordings to what is needed for the purpose (Art. 5(1)(e)); "a typical 30 days" is practice, not a legal provision. For employees, the Labour Code provisions on monitoring also apply, which we did not check.

Can I publish photos of guests in Instagram Stories?

As a rule, with consent: distributing a person's image requires the permission of the person depicted (Art. 81(1) of the Act on Copyright and Related Rights), and an image is also personal data. An exception applies, among others, to a person who is only a detail of a whole, such as a gathering, a landscape or a public event (para. 2, point 2); whether a guest in a venue qualifies requires an assessment in the specific case. In practice: you blur faces, you take photos of a table with food (without people), or you ask the specific person "may I take a photo and publish it".

What if a customer asks me to delete their data?

You have one month from receiving the request to report on the action taken, with the possibility of an extension by a further two months for a complex request or a large number of requests (Art. 12(3) GDPR). The right to erasure (Art. 17) has exceptions, among others where processing is necessary for compliance with a legal obligation (Art. 17(3)(b)). So you delete the data from the database, the newsletter and the Excel sheet, keeping only what you must retain under the law (e.g. accounting and tax records; we did not check the retention periods). Confirming to the customer that the request has been carried out is good practice.

Is WhatsApp Business GDPR-compliant?

It is not that straightforward. The standard WhatsApp / WhatsApp Business app raises doubts under GDPR: among others the issue of syncing the phone's address book (whether the numbers of people who did not consent to this reach the provider). We did not check this in Meta's documentation. We only checked that WhatsApp publishes the Business Data Processing Terms, in which it acts as a processor for the business "to the extent" indicated by the Business Terms; whether and to what extent they cover the WhatsApp Business app, as opposed to only the WhatsApp Business Platform (API), we did not determine. Before choosing a solution, check Meta's current terms. If you stay with the app: a company number, private contact sync switched off, information about WhatsApp in your privacy policy and separation of operational contacts from marketing ones - this is the minimum that limits the risk, but does not reduce it to zero.


Legal status as of: 4 October 2026
Legal basis: Regulation (EU) 2016/679 (GDPR: Art. 5, 6, 7, 12, 13, 17, 28, 29, 37, 83); Act of 12.07.2024 - Electronic Communications Law (Journal of Laws (Dz.U.) 2024, item 1221, Art. 398-399, published text; amendments from 2025-2026 were not checked for these articles); Act on Copyright and Related Rights (consolidated text Dz.U. 2025, item 24, Art. 81); WhatsApp Business Data Processing Terms (the provider's page, general scope only). Not checked: the Act on Providing Services by Electronic Means, the Labour Code provisions on monitoring, retention periods for accounting and tax records, guidance of UODO and the EDPB, or Meta's terms other than the document named.
Last review: 4 October 2026

Need complete HACCP documentation?

GastroReady offers ready-made HACCP, GMP and GHP templates for every type of foodservice business. From 299 PLN.

See the HACCP documentation packages →

Topics:gdpr restaurant polandqr menu gdprwhatsapp restaurant gdprrestaurant newsletter gdprgdpr checklist restaurant

Free, straight to your inbox

Poster: the 14 allergens. For the kitchen wall.

Ready to print in A4 and A3. All 14 allergens subject to mandatory information, laid out so the whole kitchen can read it. In three languages: English, Polish and Ukrainian. The poster is sent by email to the address you give us.