Skip to content
Security7 min read

The Complete Guide to GDPR-Compliant Guest WiFi Data Collection

Founder, VoqadoWiFi

31 March 2026
Share

Written by , Founder, VoqadoWiFi · Updated

A brass service bell shelters a guest identity card and privacy shield.
Editorial illustration. Fictional scene; not an actual customer, venue or product interface.

Why GDPR and WiFi Marketing Are Not in Conflict

Many hospitality operators assume that collecting guest data through WiFi is legally risky. That belief pushes venues one of two ways: they avoid WiFi marketing entirely, or they go ahead without proper safeguards and create the very risk they feared.

WiFi data collection is lawful under GDPR when it rests on a valid legal basis, and for marketing email that means consent that is freely given, specific, informed and unambiguous. The regulation does not ban collecting data. It governs how you collect it, store it and use it. All references below are to the GDPR, Regulation (EU) 2016/679. The UK applies the same principles through the UK GDPR, enforced by the ICO.

This is general information, not legal advice. If you run venues in several countries, check national rules with a local adviser.

Put this guide to work

Free worksheets, campaign templates and a venue growth calculator. No email gate.

Explore the free toolkit

The Six Lawful Bases Under GDPR

GDPR Article 6 sets out six lawful bases for processing personal data. For WiFi marketing in a hospitality setting, two matter:

Consent (Article 6(1)(a)): The guest has agreed to processing for one or more specific purposes. This is the basis to use for marketing emails.

Legitimate interests (Article 6(1)(f)): Processing is necessary for your legitimate interests, unless the guest's rights override them. Running and securing the network fits here.

Recital 47 does say direct marketing "may be regarded as carried out for a legitimate interest". But email marketing has a second set of rules on top of GDPR: the ePrivacy Directive and its national versions, which in the UK is PECR. Under PECR, marketing email to individuals needs their specific consent. The only exception is the "soft opt-in" for existing customers who bought, or negotiated to buy, a similar product from you, and you must offer an opt-out when you collect the address and in every message (ICO guidance on electronic mail marketing). A WiFi login is not a sale, so do not build your list on the soft opt-in. Ask for consent.

What "Freely Given" Actually Means for WiFi

Article 7(4) says that when assessing whether consent is freely given, "utmost account" is taken of whether a service is made conditional on consent to processing it does not need. Recital 43 goes further and presumes consent is not freely given in that situation. The ICO says the same: consent should be unbundled from other terms (ICO, What is valid consent?).

For a WiFi portal, that means internet access cannot depend on accepting marketing. In practice your portal offers two outcomes:

Path A: Connect to WiFi and agree to receive marketing emails. (Full access.)

Path B: Connect to WiFi without subscribing to marketing. (Full access.)

Keep the access the same for both. If guests who decline marketing get slower WiFi or shorter sessions, you are attaching a penalty to saying no, and the consent you collect from everyone else is hard to defend as freely given.

Use a separate, unticked marketing box, kept apart from the WiFi terms, so that WiFi access does not depend on whether it is ticked. VoqadoWiFi's login page works this way. Settings such as automatic marketing opt-in, or treating WiFi terms acceptance as marketing consent, do not meet this standard; on VoqadoWiFi the Auto Marketing Opt-In toggle is off for every venue, and accepting the terms is never treated as marketing consent. Pre-ticked boxes are not valid consent (Recital 32; CJEU, Planet49, C-673/17, 2019).

What "Specific" and "Informed" Require

Your consent wording must say clearly what the data will be used for. "We may contact you about our services" is too vague. Wording that works looks like this:

"I agree to receive email marketing from [Venue Name] about upcoming events, promotions, and news. I can unsubscribe at any time."

The wording must also say who is asking. The ICO says you need to identify yourself and name any third party controllers who will rely on the consent. If you run several venues under different brands and each brand will email guests, name each one. A vague reference to "group companies" is unlikely to be specific enough.

The privacy notice (linked from the consent form) must include, among other things (Article 13):

  • Who the data controller is, with contact details
  • The purposes and the lawful basis for processing
  • How long data is kept, or how you decide that
  • Who receives the data (e.g., Mailchimp)
  • The guest's rights (access, erasure, portability, objection)
  • The right to withdraw consent at any time
  • The right to complain to the supervisory authority

Record-Keeping: The Requirement Venues Most Often Miss

Article 7(1) says that where processing relies on consent, the controller must be able to demonstrate that the person consented. In practice you need a consent record for every email address on your list.

A useful consent record includes:

  • The date and time consent was given
  • The exact consent wording the guest saw (versioned, if you change it)
  • How it was collected (WiFi portal login)
  • The version of your privacy notice in force at the time

Whatever system you use, check that it captures these fields for every guest, and confirm it with your provider rather than assuming. If a guest complains to the regulator, you need to show what they agreed to and when. Without a record, you cannot demonstrate consent as Article 7(1) requires.

Data Minimisation: Only Collect What You Need

Article 5(1)(c) requires personal data to be "adequate, relevant and limited to what is necessary". For venue marketing emails, first name and email address are enough. Date of birth, phone number and postal address are not needed to send a newsletter.

Every extra field adds data you must protect and justify. A two-field form also asks less of the guest than a five-field form, so more of them finish it.

Retention Limits and Suppression Lists

Article 5(1)(e) says personal data must be kept "for no longer than is necessary". GDPR does not set a number of months, so you need your own written policy. Here is a policy we think is defensible for venue marketing (our suggestion, not a legal standard):

  • Active subscribers: Keep while they stay subscribed and engaged
  • Unsubscribed contacts: Remove them from marketing, but keep a minimal suppression record (the address or a hash of it, plus the unsubscribe date) so you never re-add them by mistake. Article 21(3) says that once someone objects to direct marketing, their data must no longer be processed for that purpose.
  • Contacts who have not engaged in a long time: Send one re-permission email, then delete those who do not respond

When a guest asks you to erase their data (Article 17), Article 12(3) gives you one month to respond, extendable by two further months where necessary if you tell the guest why. Delete the data from every system, including your email platform, and note the date. Check that your Mailchimp (or equivalent) setup lets you delete a contact fully, not just unsubscribe them.

A Compliance Checklist for Venue Operators

Before you run your first WiFi marketing campaign, confirm the following:

  • [ ] WiFi access is not conditional on marketing consent
  • [ ] The opt-in box is unticked by default
  • [ ] The consent wording names your venue (and each brand that will email)
  • [ ] A privacy notice URL is linked from the consent form
  • [ ] Your privacy notice covers the elements listed above
  • [ ] Consent records are stored with timestamp, wording version and email
  • [ ] You have a documented process for erasure and access requests
  • [ ] Your email platform unsubscribe links are active and tested
  • [ ] You have a written retention policy and a date to apply it
  • [ ] Processors (email platforms, analytics tools) are covered by an Article 28 contract

These requirements are specific, but a venue of any size can meet them. The cost of ignoring them is real: Article 83(5) allows fines of up to €20 million or 4% of total worldwide annual turnover, whichever is higher, for breaches of the basic principles, including consent. Those are ceilings, not typical amounts, but guests can complain to the regulator directly, and you will need your records when they do.

Build it right from the start. Our compliance page explains how VoqadoWiFi handles consent, and the WiFi consent generator drafts portal wording you can adapt.

Get the free Guest WiFi Growth Kit

A diagnostic worksheet, signage copy guests can follow, a campaign brief and a monthly scorecard. Yours to print and share with your team.

4 files, ready to download on this page. No account needed.

#GDPR#compliance#data protection#consent#legal

Share this article

Related articles