El manual de cumplimiento: GDPR y la privacidad de datos en WiFi para invitados

Welcome to the Purple Technical Briefing. I'm a Senior Technical Content Strategist here at Purple, and today we're covering something that every IT manager, network architect, and venue operations director needs to get right: GDPR compliance for guest WiFi. Let me set the scene. You run a hotel, a retail chain, a stadium, or a conference centre. You offer guest WiFi. The moment a visitor connects, you become a Data Controller under the General Data Protection Regulation. That is a specific legal designation. It comes with real obligations, real fines, and real reputational risk if you get it wrong. The Information Commissioner's Office is explicit on this: MAC addresses, IP addresses, session timestamps, and location data are all personal data if they can be linked to an identifiable individual. In a guest WiFi environment, they almost always can be. The moment a guest types their email address into your splash page, every other data point you collect about that device becomes personal data. So let's get into the technical architecture. This is where the detail lives. Your captive portal - the splash page guests see before they get online - is your primary compliance interface. It is also where most venues make their most serious errors. The most common mistake is bundling. This is where a venue requires a guest to accept marketing emails as a condition of getting online. Under GDPR Article 7, consent must be freely given. If you bundle network access with marketing consent, that consent is not freely given. It is therefore invalid. Full stop. Your captive portal must present at minimum two separate consent elements. The first is mandatory: acceptance of your terms of service for network access. The second is optional, unticked by default: consent to receive marketing communications. A guest must be able to connect to your WiFi without agreeing to marketing. If they cannot, you are in breach. GDPR Recital 32 explicitly prohibits pre-ticked boxes. Beyond consent structure, your portal must serve a clear privacy notice before the user submits any data. Under GDPR Article 13, this notice must explain what data you collect, why you collect it, how long you keep it, and who you share it with. It must link to your full privacy policy. And critically, your system must log every consent event: who consented, when they consented, what they consented to, and the exact version of the privacy notice they saw at that moment. That consent audit trail is your proof of compliance if a regulator comes knocking. Now let's talk about the four categories of data your guest WiFi network actually collects, because this is broader than most teams realise. First: registration data. Name, email address, phone number, social login credentials. This is the data guests actively provide on your captive portal. The lawful basis is consent, and it must be granular. Second: device and session data. MAC addresses, IP addresses, connection and disconnection timestamps, session duration, data transferred. This is collected automatically the moment a device associates with your network. Legitimate interest can cover basic session logging for network security and troubleshooting - but only if you have conducted a Legitimate Interest Assessment and can demonstrate your interests do not override the user's privacy rights. Third: location data. If you use WiFi analytics to track footfall, measure dwell time, or generate heatmaps, you are processing location data. Even if it is aggregated in your dashboard, the initial collection from an individual device is personal data. This requires explicit disclosure in your privacy notice, and in many cases, explicit consent. Fourth: usage data. Browsing behaviour, application usage patterns, bandwidth consumption. If you are inspecting or logging traffic content, you need a very clear lawful basis and robust security controls around that data. From a network architecture perspective, segmentation is non-negotiable. Your guest WiFi traffic must be isolated on a dedicated VLAN - a Virtual Local Area Network - completely separate from your corporate network. Use access control lists to block guest devices from accessing any internal subnets. Enable client isolation so guest devices cannot communicate with each other. This is not just a GDPR requirement; it is basic security hygiene. For authentication, integrate your wireless LAN controller with a cloud RADIUS server. Remote Authentication Dial-In User Service - RADIUS - is the protocol that handles authentication, authorisation, and accounting on enterprise networks. When a user completes the captive portal flow, the platform sends a RADIUS Access-Accept message to the controller, granting access. This creates a clean separation between the authentication layer and the data collection layer. On encryption: your guest SSID should use WPA3 where your hardware supports it. WPA3 uses Simultaneous Authentication of Equals, which eliminates the vulnerabilities present in WPA2's four-way handshake. At a minimum, enforce WPA2 with AES encryption. And your captive portal must be served over HTTPS with a valid TLS certificate. Serving a form that collects personal data over HTTP is a serious security failure. Purple's platform works across Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme, and Fortinet hardware. That hardware-agnostic approach means you can enforce consistent compliance controls regardless of what access points you have on the ceiling. Let's move to data retention, because this is where organisations accumulate risk silently over time. GDPR's storage limitation principle - Article 5(1)(e) - requires that personal data is kept no longer than necessary for the purpose for which it was collected. A defensible baseline looks like this. Session logs - IP addresses, MAC addresses, connection timestamps - should be purged after 30 days. Network security logs can be retained for up to 12 months. Consent records must be kept for the duration of the service relationship plus typically two years after the last interaction. Marketing profiles should be retained only as long as the user's consent is valid. The moment a user withdraws consent, their marketing profile must be deleted. Not archived. Deleted. The challenge is enforcing these policies at scale. If you are managing guest WiFi across dozens or hundreds of venues, manual data deletion is not viable. You need a platform that automates retention enforcement. Purple applies configurable retention rules to each data category, automatically purging records when they reach the end of their retention period. Across 80,000 live venues and 350 million unique users, that automation is the only way to stay compliant at scale. Now let me walk you through two real-world scenarios where these principles come together. Scenario one: a 200-room hotel. The property team wants to collect guest emails to drive loyalty programme sign-ups. Their current system requires guests to accept marketing to get online. That is a clear GDPR violation. The fix is straightforward: deploy a compliant captive portal with separate consent checkboxes. The mandatory checkbox covers terms of service. The optional, unticked checkbox covers marketing consent. The hotel will likely see a lower raw volume of marketing opt-ins compared to the bundled approach - but the quality and legality of the list improves dramatically. Guests who actively opt in are significantly more likely to engage with subsequent communications. And critically, the hotel is no longer exposed to ICO enforcement action. Scenario two: a stadium IT team. They want to use WiFi analytics to monitor crowd density and manage safety at events. The concern from the legal team is that tracking device locations without consent is a GDPR violation. The solution is two-fold. First, update the captive portal privacy notice to explicitly disclose that location data is processed for crowd management and safety purposes. Second, implement MAC address pseudonymisation at the edge - on the access points themselves - before the data reaches the cloud analytics platform. This means the analytics system works with pseudonymous identifiers rather than raw MAC addresses, significantly reducing the privacy risk and the regulatory exposure. Now let's cover implementation pitfalls and risk mitigation - the things that trip teams up even when they think they have it covered. Pitfall one: consent fatigue. If your portal is too complex, users will either abandon the connection or blindly click through everything. Keep it simple. Use plain language. Explain the value exchange clearly: fast, free WiFi in exchange for an email address and the option to hear from you occasionally. Pitfall two: failing to honour data subject rights. Under GDPR Articles 15 through 22, users have the right to access, rectify, erase, and port their data. You must have a process for this. A self-service preference centre where users can manage their consent and submit Data Subject Access Requests - DSARs - is the gold standard. Purple's platform provides the tools to facilitate exactly this, making it straightforward to respond to DSARs without manual intervention. Pitfall three: unsigned vendor agreements. Your guest WiFi platform provider is a Data Processor. Before any personal data flows to them, you must have a signed Data Processing Addendum in place. This applies to your WiFi analytics provider, your CRM, and your email marketing platform. No DPA, no data sharing. Pitfall four: no breach response plan. Under GDPR Article 33, the 72-hour notification clock starts the moment you become aware of a personal data breach. You must notify the ICO within 72 hours, even if your investigation is not complete. Build this timeline into your incident response plan now, before you need it. Right - rapid-fire questions. These are the ones we get most often. Do we need consent if we are only collecting MAC addresses for analytics? Yes. If those analytics can be tied back to a device and its user's behaviour, it is personal data. You need either explicit consent or a robust anonymisation process that occurs immediately upon collection. Is a social media login GDPR compliant? It can be, but you must be transparent about what data you receive from the social platform, and you must obtain separate consent for any use of that data beyond basic authentication. Does GDPR apply if we are a small venue? Yes. GDPR applies regardless of organisation size. One complaint to the ICO can trigger an investigation. The scale of any fine may be proportionate to your size, but the obligation to comply is absolute. Do we need a Data Protection Impact Assessment? If your guest WiFi deployment involves large-scale location tracking, behavioural profiling, or processing data from vulnerable groups, a DPIA is legally mandatory under GDPR Article 35. Even where it is not mandatory, it is good practice and demonstrates accountability to a regulator. Let me close with your next steps. Four actions you can take this week. One: audit your current captive portal. Check whether marketing consent is bundled with network access terms. If it is, fix it before your next ICO audit. Two: review your data retention settings. If you do not have automated deletion policies in place, you are accumulating risk with every passing day. Three: check your vendor agreements. Ensure you have a signed Data Processing Addendum with every third-party platform that processes guest data on your behalf. Four: implement a preference centre. Give your guests a self-service way to manage their consent and submit data subject access requests. This dramatically reduces the operational burden of handling DSARs manually. Purple holds ISO 27001 certification, is GDPR and CCPA compliant, and operates across 80,000 venues globally. We have processed 440 million logins in 2024 alone and collected 29 billion data points - all under a compliance architecture designed to protect both venues and their visitors. Our platform automates consent logging, data retention enforcement, and DSAR management, so you can focus on running your network rather than managing compliance spreadsheets. Thank you for joining this Purple Technical Briefing. For more resources on guest WiFi compliance, visit purple.ai. Stay compliant, and stay secure.