Request a quote WhatsApp

15 September 2026 · 3 min read

Guest Wi-Fi and data protection: privacy notice, consent and retention

Which data does your portal process and on what basis? Privacy notice, explicit consent, retention and the line between legal logging and marketing.

Guest Wi-Fi carries two duties side by side: legal logging and personal data protection. They do not conflict, but confusing them leads to collecting too much data while still missing required records. This guide separates the two.

The core distinction: data collected for legal records and data collected for marketing do not rest on the same basis. One is an obligation, the other needs separate permission.

What the portal processes

DataWhyNote
Phone numberAuthenticationRequired for verification
Name / room numberIdentity matchVia PMS in hotels
MAC and IPSession recordTechnical necessity
Session timeLegal recordStored with timestamp
Email, birth dateMarketingOnly with separate consent
Visit analyticsBusiness insightPrefer anonymised data

What the privacy notice must say

  • Who processes the data (full legal name of the business)
  • Which data, for which purposes
  • Legal basis and retention period
  • Any transfers (for example the SMS provider)
  • How to exercise data subject rights

The notice must be readable in the portal, not buried in small print, and versioned: store which version each guest accepted, with a timestamp.

Legal logging does not require marketing consent; the record stems from an obligation. Sending campaigns, building profiles or sharing data with third parties does require separate, explicit permission. That checkbox must not be pre-ticked, nor a condition of getting online.

Data minimisation

The most common mistake is asking for unnecessary fields: occupation, birth date, gender. Every extra field lowers conversion and increases your protection burden. Start with the minimum needed to verify.

Retention and deletion

Legal record retention follows regulation; marketing data follows the scope of the consent. Delete them on separate schedules, automatically, and log the deletion. Technical detail: signed log archive.

Checklist

  • Is the privacy notice visible and versioned in the portal?
  • Is marketing consent a separate, optional checkbox?
  • Is every requested field genuinely necessary?
  • Is consent stored with a timestamp?
  • Are deletion schedules separate for legal and marketing data?
  • Are transfers such as the SMS provider documented?

FAQ

Can I send campaign messages without marketing consent?

No. The legal logging basis does not cover marketing communication; separate explicit consent is needed.

Can I make consent a condition of access?

You should not. Tying internet access to marketing consent makes that consent questionable.

What if a guest asks for deletion?

Marketing data is deleted. Records under a legal retention obligation are kept until the period ends.

Is a MAC address personal data?

Treat it as such where it can be linked to a person; session records therefore need protection and time-limited retention.

How can I use data for analytics?

Anonymised, aggregated measures (visits, dwell time, return rate) carry lower risk.

This content is informational; compliance assessment is the responsibility of the business and its legal counsel.

Let’s simplify your guest Wi-Fi journey

Keep your existing infrastructure and bring access, engagement and 5651 records into one panel.

Request a Free Demo

We use cookies for visit statistics. Cookie policy