Key takeaways
- A DPIA is required before high-risk processing starts, and new technology is one of the signals that the risk may be high.
- Screen every new guest tool with five yes-or-no questions; most small changes need only a short note, not a full assessment.
- The law sets four minimum contents: a description, a necessity check, a risk assessment and the measures you will take.
- Health details such as allergies, recorded calls, CCTV and automated decisions are the usual reasons a venue's assessment needs more depth.
What the law actually requires
Under Article 35 of UK GDPR, where processing, in particular using new technologies, is likely to result in a high risk to people's rights and freedoms, the controller must assess the impact before the processing begins[1]. One assessment can cover a set of similar operations with similar risks, so a group running the same booking system in four pubs can write one DPIA, not four.
The article also sets the minimum contents. Every DPIA needs a systematic description of the processing and its purposes, an assessment of whether it is necessary and proportionate, an assessment of the risks to people, and the measures you will use to address those risks[1]. Everything else, including the template you use, is up to you.
12%
of UK food or hospitality businesses had a board member responsible for cyber security in 2025, among the lowest of any sector[2]
Five screening questions for any new guest tool
Most venues do not need a 20-page document for a new card machine. Run these questions when you buy or switch on any system that touches guest or staff data. Two or more yes answers, or a yes to question 2 or 4, means you complete the full template below.
- Is the technology new to your business, such as AI call answering, facial recognition at the door, or a guest Wi-Fi portal that builds marketing profiles?
- Will it handle health information, such as allergies, intolerances or accessibility needs, for many guests?
- Does it monitor people in a space open to the public, such as CCTV with analytics, footfall sensors or number plate cameras in the car park?
- Will it make or shape decisions about people without a person reviewing them, such as declining bookings, scoring staff or filtering job applicants?
- Will data leave your control, for example sent to a supplier who stores it outside the UK or uses it to improve its own models?
Question 2 matters more in hospitality than in most sectors. Around 23% of adults in England, Wales and Northern Ireland report a food hypersensitivity[3], and data concerning health is a special category under Article 9 of UK GDPR, which prohibits processing it unless a specific condition applies[4]. A booking system that stores allergy notes for every guest is processing special category data at scale.
How common venue tools usually screen
These are judgement calls, not legal rulings, but they reflect how the screening questions tend to land for a typical restaurant, pub or café. Your answers depend on how you configure each tool.
- Card terminal or new till: usually no DPIA. The supplier handles card security and you collect little extra personal data. Keep a short screening note.
- Online booking widget with free-text notes: often a short DPIA, because guests type allergy and accessibility details into the notes field whether or not you ask.
- AI phone answering or website chat: usually a full DPIA. It is new technology, it records or stores conversations, and callers mention health details and children's names.
- Guest Wi-Fi portal with marketing sign-up: a short DPIA, focused on consent, profiling and where the supplier stores data.
- CCTV in the bar and car park: a full DPIA if cameras cover public areas at scale, use analytics, or record audio. Audio recording in a bar is hard to justify.
- Rota, timesheet and performance apps: a short DPIA, and a full one if the tool scores staff or allocates shifts automatically.
- Recruitment software that ranks applicants: a full DPIA, because it can lead to significant decisions about people with no human review.
If the answer is no DPIA, still keep the screening note with the date and your reasons. It takes five minutes and it is the first thing you will want if a guest complains or the supplier changes the product.
The template
Copy this into a document and fill in one row at a time. Keep answers short and specific. The aim is a record that shows you thought about the risk and did something about it.
| Section | What to write | Prompt questions |
|---|---|---|
| 1. Description | What the system does, what data, from whom, where it is stored, who can see it | Which fields does the guest fill in? What is recorded automatically? |
| 2. Purpose and lawful basis | Each purpose with its lawful basis and, for health data, the Article 9 condition | Would the system still work if we collected less? |
| 3. Necessity and proportionality | Why this tool, why this data, why this retention period | Is there a less intrusive way to get the same result? |
| 4. Risks to people | What could go wrong for guests or staff, how likely and how severe | Leak, wrong decision, unexpected marketing, staff misuse |
| 5. Measures | Controls for each risk, who owns them and by when | Access limits, deletion, staff training, supplier terms |
| 6. Residual risk and sign-off | What risk remains and who accepted it | Would we be comfortable explaining this to a guest? |
If your supplier will process the data on your behalf, attach the contract terms to section 5. Article 28 says you may use only processors that give sufficient guarantees, and the contract must cover acting only on your documented instructions, confidentiality, security, help with guest rights requests, and deleting or returning the data when the service ends[5].
Example: a pub adds AI phone answering and a guest Wi-Fi portal
Example. The Fox and Hound, a fictional 120-cover pub, plans two changes in the same month: an AI assistant that answers calls, takes booking requests and passes allergen questions to staff, and a Wi-Fi portal that asks guests for an email address and offers a newsletter.
Screening
Both are new technology. The phone assistant will hear allergy details on some calls. The Wi-Fi portal sends emails to a supplier in another country. Three yes answers, so a full DPIA covering both.
Description
Calls are recorded, transcribed and summarised; summaries reach the manager's inbox. The portal collects email, device identifier and visit time.
Necessity
Recording is needed to check booking details and train staff. The portal does not need date of birth, so that field is dropped. Newsletter consent becomes a separate unticked box.
Risks
Allergy details sitting in transcripts for years; a leak of the guest email list; guests not realising the caller is an assistant; marketing sent without valid consent.
Measures
Transcripts deleted after 90 days; allergen questions routed to the duty manager, not answered by the assistant; greeting tells callers they are speaking to AI; processor agreement checked with both suppliers; Wi-Fi data kept separate from booking data.
Sign-off
The licensee signs and diarises a review in six months, or sooner if either supplier changes how data is used.
The whole document runs to three pages. It took the manager an afternoon, most of it spent getting answers from the two suppliers.
Security is part of the assessment
A DPIA is not only about lawful basis. In 2025, 30% of UK food or hospitality businesses identified a cyber breach or attack in the previous 12 months, and only 25% had sought external cyber security information or guidance, against 42% of businesses overall[6][7]. Section 5 of the template is where those gaps get closed.
- Turn on two-step login for every system in the assessment, especially shared manager accounts.
- Remove leavers on their last shift, not at the next audit.
- Check where exports go: a CSV of guest emails on a personal laptop undoes every other control.
- Ask the supplier for its breach notification time and write it into the DPIA.
Common mistakes
- Writing the DPIA after go-live. The duty is to assess before processing starts; a retrospective note still helps, but it is weaker evidence.
- Copying the supplier's own assessment. It describes their system, not your purposes, retention or staff access.
- Treating allergy notes as ordinary booking data. They are health data and need a stated Article 9 condition.
- Forgetting staff data. Rota, recruitment and performance tools often carry more risk than guest tools.
- Never reviewing it. Software updates add features. AI use is spreading quickly, with 30% of UK businesses using at least one AI technology by September 2026[8], and new features often arrive inside existing products.
Rule of thumb: if you would hesitate to explain the tool to a guest at the bar, it needs a DPIA.
For the wider legal picture, read AI and UK GDPR: what the ICO expects, and put the staff side into your AI use policy.
Frequently asked questions
Is a DPIA legally required for a restaurant booking system?
Only where the processing is likely to be high risk. A plain booking diary usually is not, but one that stores allergy notes for many guests, uses new technology or profiles guests for automatic decisions may be. Screen it and keep a note of your answer either way.
Who should write the DPIA in a small venue?
The owner or general manager, with input from the supplier. If you have a data protection officer, the law says you must seek their advice.
How long should a DPIA be?
Long enough to cover the four legal minimums for your actual use. For a single site, two to four pages is common.
Do I need to send the DPIA to the regulator?
Only if the assessment shows a high risk you cannot reduce. In that case you must consult the regulator before starting the processing.
References
legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 35: data protection impact assessment (opens in a new tab) ↑
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
Food Standards Agency (2025). Food and You 2: wave 11 key findings (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 9: processing of special categories of personal data (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 28: processor (opens in a new tab) ↑
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
Office for National Statistics (2026). Business insights and impact on the UK economy: 8 October 2026 (opens in a new tab) ↑