PubWatch is one of the oldest and most effective community safety schemes in UK hospitality. It operates in hundreds of towns and cities across England, Wales, Scotland, and Northern Ireland. Its purpose is straightforward: to create a network of licensed premises that share information about individuals who pose a risk to staff, customers, or the wider community. When that network works well, it keeps people safe. When it fails, people get hurt.
The question facing PubWatch schemes today is how to modernise enforcement without overstepping legal boundaries — particularly around data protection. Facial recognition technology offers a potential solution, but it comes with significant legal and ethical requirements that must be understood before any venue considers implementation.
What PubWatch is and how it works
PubWatch is a voluntary scheme run by licensees in a specific area — usually a town centre or borough. Member venues agree to share information about individuals who have been barred from one or more premises, typically because of violence, antisocial behaviour, drug use, or other conduct that poses a risk. When a PubWatch exclusion order is issued, all member venues agree to refuse entry to that individual for the duration of the ban.
The scheme is supported by local police licensing teams but is not a police operation. It is a voluntary agreement between private businesses. This distinction matters legally — it means the data-processing obligations fall on the individual venues and the PubWatch scheme itself, not on the police.
Exclusion orders are typically issued through a formal process. An incident occurs at a member venue. The licensee reports it to the PubWatch coordinator, usually with a description of the individual, a photograph if available, and details of the incident. The coordinator reviews the report, and if it meets the scheme's criteria, an exclusion order is issued. The individual's details — name, photograph, description, and exclusion period — are circulated to all member venues.
Bar notices and legal exclusion
A PubWatch exclusion is not a criminal sanction. It is a civil measure. Licensed premises have the right to refuse entry to anyone, provided they do not do so on discriminatory grounds protected under the Equality Act 2010. A PubWatch ban is an exercise of this right, coordinated across multiple venues.
The individual subject to a ban should be notified in writing, given the reasons for the exclusion, and informed of any appeals process. Most PubWatch schemes have a formal appeals procedure, usually involving a panel of licensees and sometimes a police representative. The ban period varies — typically between three months and two years, depending on the severity of the incident.
The challenge is enforcement. A photograph circulated by email or displayed on a staff noticeboard is only effective if the door team or bar staff happen to recognise the individual. In a busy venue on a Saturday night, with hundreds of people entering over the course of an evening, relying on human recognition of a photograph pinned to a corkboard is not reliable. This is where technology enters the conversation.
Duty of care under the Licensing Act 2003
The Licensing Act 2003 places specific obligations on premises licence holders regarding the prevention of crime and disorder, public safety, prevention of public nuisance, and the protection of children from harm. These are the four licensing objectives, and they are not optional — failure to promote them can result in licence review or revocation.
Allowing a banned individual to enter your premises when you have the means to prevent it is a failure of the first licensing objective — prevention of crime and disorder. If that individual then causes harm to a staff member or customer, the venue faces potential liability both under the Licensing Act and in civil negligence. The question is not whether you should exclude banned individuals — you must. The question is how effectively you can do so.
GDPR legal basis for facial recognition
Facial recognition data is biometric data. Under UK GDPR, biometric data processed for the purpose of uniquely identifying a natural person is classified as special category data under Article 9. Processing special category data requires both a lawful basis under Article 6 and a specific condition under Article 10 of the Data Protection Act 2018 (for criminal conviction data) or a condition under Article 9(2) of UK GDPR.
The most commonly cited lawful basis for facial recognition in a PubWatch context is legitimate interests under Article 6(1)(f) of UK GDPR. This requires the venue to demonstrate that the processing is necessary for a legitimate interest (safety of staff and customers, compliance with licensing objectives), that the processing is necessary to achieve that interest (alternative methods are inadequate), and that the individual's rights and freedoms do not override that legitimate interest.
For the special category condition, venues typically rely on substantial public interest under Schedule 1, Part 2 of the Data Protection Act 2018, specifically the condition relating to the prevention or detection of unlawful acts. This requires an Appropriate Policy Document to be in place.
Critically, any venue deploying facial recognition must conduct a Data Protection Impact Assessment (DPIA)before going live. This is not optional — it is a legal requirement under Article 35 of UK GDPR for any processing that is likely to result in a high risk to individuals' rights and freedoms. Biometric data processing in a public-facing environment meets this threshold without question.
UK ICO guidance on biometric data
The UK Information Commissioner's Office has published guidance on the use of biometric data, including facial recognition technology. The ICO's position is not that facial recognition is prohibited — it is that it must be deployed proportionately, with appropriate safeguards, and with full compliance with data protection law.
Key requirements from the ICO include: transparency (individuals must be informed that facial recognition is in use, via clear signage at the point of entry), purpose limitation (the data must only be used for the stated purpose — in this case, identification of excluded individuals), data minimisation (you must not collect or retain more data than necessary), storage limitation (biometric templates must not be retained longer than necessary), and security (appropriate technical and organisational measures must be in place to protect the data).
What venues need in place before going live
ICO registration. Every venue processing personal data must be registered with the ICO. If you are using facial recognition, your registration must reflect this. The annual registration fee is nominal, but failure to register is a criminal offence.
Data Protection Impact Assessment. A formal DPIA must be completed before any facial recognition system is deployed. The DPIA must identify the risks to individuals, assess whether the processing is proportionate, and document the mitigations in place. This is a living document that must be reviewed regularly.
Signage. Clear, visible signage must be displayed at every entry point informing customers that facial recognition technology is in use, the purpose of the processing, and how to exercise their data rights. The signage must be easily readable and cannot be hidden in small print.
Retention policy. Biometric data must not be retained longer than necessary. For PubWatch purposes, facial templates should only be retained for the duration of the exclusion order plus a reasonable administrative period. Once the exclusion expires, the template must be deleted.
Appropriate Policy Document. If relying on the substantial public interest condition, an Appropriate Policy Document must be in place that explains the lawful basis, the condition relied upon, and the retention and erasure policies.
Minnie's implementation
Minnie's approach to PubWatch facial recognition is designed around three principles: real-time matching, minimal data retention, and alert-only output.
Real-time matching. Camera feeds at entry points are analysed in real time. When a face is detected, it is compared against the active exclusion list. If there is a match, an alert is generated. If there is no match, the facial data is discarded immediately — it is not stored, logged, or retained in any form.
No template storage of non-excluded individuals. The system only stores biometric templates for individuals who are subject to an active PubWatch exclusion order. No templates are created or stored for customers, staff, or any other individual. This minimises the data footprint and significantly reduces the risk profile.
Alert only. The system does not make an access control decision. It does not lock doors, activate barriers, or prevent entry. It generates an alert to the designated staff member — typically the door supervisor or duty manager — who then makes the operational decision about how to respond. The technology informs; the human decides.
A note on legal advice. This article provides general information about the legal framework surrounding facial recognition in licensed premises. It is not legal advice. Any venue considering deploying facial recognition technology should obtain independent legal advice specific to their circumstances, particularly regarding the DPIA process, the applicable lawful basis, and the special category condition. The regulatory landscape is evolving, and compliance requirements may change.