Key takeaways
- Decide first whether you need a sign-up at all. A password on the table card is lawful and simple; a captive portal brings data protection duties.
- Marketing emails and texts need prior consent under PECR[1]. Getting online must not depend on agreeing to marketing[2].
- Tell guests at the point of sign-up who you are, why you want the data, how long you keep it and their rights[3].
- Keep the guest network apart from tills and card machines: 30% of food and hospitality businesses identified a cyber breach or attack in a year[4].
First decision: do you need a sign-up?
Guest Wi-Fi can be run three ways. An open network with no password is easy but invites anyone nearby and gives you no control. A shared password printed on table cards or the menu is simple, collects no personal data and suits most venues. A captive portal, the page that asks for an email address or a social login before connecting, gives you a list of guests but makes you responsible for that data under UK GDPR and, if you market to them, under PECR.
Choose a captive portal only if you have a clear use for the data and someone who will look after it. A list nobody emails is a liability, not an asset: it must still be secured, kept up to date and deleted on schedule.
- Do you plan to send marketing emails or texts? If not, a password is enough.
- Will someone own the list, answer data requests and delete old records?
- Does your Wi-Fi provider act as your processor under a written contract, or does it want to use the data for its own purposes too?
- Can your network keep guest devices apart from tills, card machines and the office computer?
What a captive portal collects, and why it matters
Most portals collect more than the email address on the screen. Typical fields include name, email, sometimes date of birth or postcode, and in the background the device's identifier, connection times and how often the device returns. Some social login options pass profile data from the guest's account. All of this is personal data. Switch off any field you do not need and ask the provider for a list of what is collected by default.
| Purpose | Likely lawful basis | What you need to do |
|---|---|---|
| Providing the Wi-Fi connection | Legitimate interests or contract | Collect the minimum; explain it in a short privacy notice |
| Security and abuse prevention logs | Legitimate interests or legal obligation | Keep logs only as long as needed; restrict access |
| Marketing emails or texts | Consent under PECR | Unticked box, separate from connecting, easy to withdraw |
| Visit analytics (how often devices return) | Legitimate interests, with care | Explain it; give a way to object; aggregate where you can |
| Sharing data with partners | Usually consent | Avoid unless there is a strong reason; name the partners |
The table is a starting point for your own assessment, not legal advice. If your provider suggests uses beyond these, ask what lawful basis they rely on and who is the controller.
Consent for marketing: the rules that trip venues up
Under the Privacy and Electronic Communications Regulations, marketing emails and texts to individuals need their prior consent[1]. The main exception, the soft opt-in, lets a business market its own similar products to customers whose details it obtained during a sale or negotiation for a sale, provided they were given a simple way to refuse at the time and in every message[1]. Do not assume a Wi-Fi login meets that test. The safer route is a clear consent box.
UK GDPR adds conditions to any consent you rely on. You must be able to show the person consented, the request must be clearly separate from other matters, it must be as easy to withdraw consent as to give it, and you should not make a service conditional on consent to processing that the service does not need[2]. For Wi-Fi that means guests should be able to connect without agreeing to marketing.
Example sign-up screen (fictional): 'Welcome to The Granary. Enter your email to connect. We use it to run the Wi-Fi and keep it secure, and we delete it after 12 months. [ ] Yes, send me news and offers from The Granary by email. You can unsubscribe at any time. Privacy notice. Connect.' The box starts unticked and the Connect button works either way.
Tell guests what you are doing
When you collect personal data directly from someone, UK GDPR requires you to give certain information at the time the data are obtained: who you are and how to contact you, the purposes and lawful basis, any legitimate interests relied on, who receives the data, how long you keep it, the guest's rights, the right to withdraw consent and the right to complain[3]. On a phone screen, do this in layers: two lines on the portal, with a link to a full notice.
- Name the business that runs the venue, not only the Wi-Fi provider.
- Say how long you keep connection data and marketing data, as separate periods.
- Say whether the provider uses the data for its own purposes. If it does, it is likely a separate controller and must be named.
- Give an email address for data requests that someone actually reads.
- Keep the notice up to date when you change provider or start a new use.
Setting up a compliant portal
Map the data
Ask your provider for a list of every field and background identifier collected, where it is stored and who can access it. Turn off what you do not need.
Sign a processor contract
If the provider processes data on your behalf, UK GDPR requires a written contract setting out its duties. Check whether its standard terms let it reuse guest data; if so, negotiate or choose another provider.
Write the screen and the notice
Short portal text, an unticked marketing box, a link to the full privacy notice and a Connect button that works whether or not the box is ticked.
Set retention
Decide how long to keep connection records and marketing records. Automate deletion if the platform allows it.
Connect marketing properly
Only addresses with a recorded consent flow into your email tool. Keep the date, time and wording of the consent.
Test unsubscribe
Sign up yourself, unsubscribe and check you stop receiving emails across every tool that holds the list.
Security: separate networks and keep it simple
Hospitality is a frequent target and often under-protected. In the 2025 Cyber Security Breaches Survey, 30% of UK food or hospitality businesses identified a breach or attack in the previous 12 months, compared with 43% of businesses overall, and only 25% had sought external cyber security guidance, against 42% overall[4]. Only 12% had a board member responsible for cyber security[4].
- Food or hospitality
- All businesses
Source: Department for Science, Innovation and Technology, 2025[4]
Show the data
| Item | Food or hospitality | All businesses |
|---|---|---|
| Identified a breach or attack in the last 12 months | 30% | 43% |
| Sought external cyber security guidance | 25% | 42% |
- Run guest Wi-Fi on a separate network or VLAN from tills, card terminals, kitchen screens and the office.
- Change the admin password on the router and the portal from the default, and keep firmware up to date.
- Turn on client isolation so guest devices cannot see each other.
- Limit who can export the guest list, and log exports.
- Rotate the staff network password when people leave.
Example: a bar cleans up its list
Example (fictional): A city-centre bar finds that its Wi-Fi provider has collected 14,000 email addresses over three years, with a pre-ticked marketing box and no retention period. The manager stops emailing the whole list, deletes records with no clear consent, keeps only the addresses of guests who later signed up through the booking form with a recorded consent, and replaces the portal screen with an unticked box and a 12-month deletion rule. The list is smaller, but every address on it can be emailed lawfully and opens are higher.
The example's point is the order of work: stop sending first, then fix the consent record, then rebuild with a compliant screen. For what to send once you have a clean list, see email marketing and PECR consent.
Checklist
- A clear reason for a sign-up, or a simple password instead.
- Only necessary fields collected; social login data limited.
- Processor contract in place, or the provider named as a separate controller.
- Unticked, separate marketing consent; Connect works without it.
- Short notice on the portal and a full privacy notice linked.
- Retention periods set and deletion automated or diarised.
- Guest network separated from payments and the office.
- Someone named to answer data requests.
Related reading: order and pay at table apps, which raise similar data questions, and QR code menus.
Frequently asked questions
Is it legal to ask for an email address before giving Wi-Fi?
It can be, if you explain why, collect only what you need and keep it secure. Do not make connecting depend on agreeing to marketing; consent to marketing has to be a separate, free choice.
Can we email everyone who logged in to our Wi-Fi?
Only those who gave valid consent to marketing, or who clearly fall within the soft opt-in. A login alone is not consent, and a pre-ticked box does not count.
How long can we keep Wi-Fi sign-up data?
No longer than you need it for the purpose you stated. Set a period, such as 12 months for connection records, say it in your notice and delete on schedule.
Is our Wi-Fi provider responsible for data protection?
Usually you are the controller and the provider is your processor, so you remain responsible. If the provider uses the data for its own purposes, it becomes a controller for that use and must be named in your notice.
References
legislation.gov.uk (The National Archives) (2003). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 22 (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 7: Conditions for consent (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 13: Information to be provided where personal data are collected from the data subject (opens in a new tab) ↑
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑