top of page
Search

Guest Wi-Fi and the New UK Data Rules: What Event Organisers Actually Need to Do About Consent

3 days ago
5 min read

If your event Wi-Fi asks guests to tick a box before they get online, it’s worth checking exactly what that tick means, and what evidence you keep afterwards.

A captive portal can do several jobs at once: connect a visitor, record acceptance of network terms, ask for an email address and invite them to receive marketing. Those are different purposes, and one “Accept” button does not automatically provide valid consent for all of them.

The Data (Use and Access) Act 2025 (DUAA) has changed parts of the UK’s data protection and electronic privacy framework. But it has not introduced a standard retention period for guest Wi-Fi consent records. The practical task for organisers is to separate access from optional uses, document choices properly and set retention periods you can justify.

Event Wi-Fi equipment being assembled by a technician at an outdoor site

What changed under the DUAA, and what didn’t

Some DUAA provisions took effect on 5 February 2026, including changes to the rules in the Privacy and Electronic Communications Regulations (PECR) about storing or accessing information on a person’s device. The ICO describes additional, limited exceptions, including for certain statistical service-improvement purposes. These are not blanket permission for tracking, profiling or marketing: the purpose and conditions matter.

For example, a carefully designed, privacy-conscious analytics use may fall within the new statistical purposes exception if it is solely for improving the service, results in aggregate statistics, and gives users clear information and a simple, free way to object. The exception does not cover individual tracking or retaining identifiable data indefinitely.

The DUAA also amended aspects of UK data protection law, including provisions concerning research consent and the use of information for a new purpose. But it did not create a fixed period (such as six years, 12 months or two years) for keeping ordinary guest Wi-Fi consent records. The ICO’s current consent-record guidance says evidence should be kept for as long as you rely on that consent. Data must not be kept for longer than necessary.

For the legislation and commencement dates, see the Data (Use and Access) Act 2025 and the 2026 commencement regulations.

First, separate Wi-Fi access from marketing consent

A guest should not usually have to agree to unrelated marketing just to get online. If your event Wi-Fi needs a session identifier or device information to authenticate a user or manage the connection, explain that processing in your privacy information and identify an appropriate lawful basis. Don’t assume you need to call it “consent” just because the portal has an acceptance button.

Marketing is a separate choice. If you want to send marketing by email or text to individual subscribers, PECR rules generally require valid consent unless a specific exception applies. Make the choice optional, use an unticked box and say who will contact the person, for what purpose and by which channel. “I accept the Wi-Fi terms” is not a marketing opt-in.

Likewise, a portal cookie or other technology that stores or accesses information on a guest’s device may engage PECR. Some technologies used solely to provide a service the user requests may qualify for an exception, but you need to check what each tool actually does. The ICO’s guidance explains the PECR rules and exceptions.

Busy outdoor market with event Wi-Fi infrastructure supporting stalls and visitors

What records should your captive portal keep?

Keep evidence that matches the choice being made. For a marketing opt-in, the ICO says you should be able to demonstrate who consented, when, what they were told, how they consented, and whether and when they withdrew consent.

For a guest Wi-Fi portal, that could mean recording:

  • A suitable identifier: for example, an email address for an email-marketing opt-in, or a session ID where appropriate. Don’t collect extra identifying information just to create an audit trail.

  • The date and time of the person’s action.

  • The exact wording and version of the consent request, with the relevant privacy information and date or version number.

  • What they agreed to: such as the named organisation, purpose and marketing channel. Keep separate choices separate.

  • The action taken: for example, an unticked email-marketing box actively selected.

  • Any withdrawal or unsubscribe: including when it happened and whether the contact was suppressed from future messages.

Keep Wi-Fi access records distinct from marketing evidence. Depending on your set-up, operational records may include a session identifier, connection time and limited network logs. Those records can help provide and secure the service, but they do not prove that someone opted into marketing.

Before the event, agree who is responsible for each activity. The organiser may decide why guest details are collected; a connectivity provider may operate the portal or process information on the organiser’s instructions. Responsibilities depend on the actual arrangements, so document them rather than assuming the Wi-Fi supplier is automatically responsible for every data-protection duty.

So how long should you retain the records?

There is no single DUAA retention deadline for guest Wi-Fi login consents. The right period depends on why you hold each type of information and how long you need it. Explain your retention period, or the criteria you use to decide it, in the privacy information shown when you collect data. Review it and delete or anonymise records when you no longer need them.

Record type

Practical retention approach

Routine Wi-Fi session data

Keep only as long as needed to operate the service, resolve routine issues or meet a documented security need. Set a deletion or anonymisation date after the event.

Security logs

Choose a period that reflects your security risks, technical needs and any applicable obligations. Record why it is necessary and review it rather than retaining everything by default.

Marketing consent evidence

Keep it while you rely on that consent, so you can demonstrate what was agreed. Review ongoing consent where circumstances change or expectations may have moved on.

Withdrawal and suppression records

Stop the relevant marketing. Keep the minimum information needed to honour the opt-out and prevent future messages, with a documented reason and review process.

Those are categories, not statutory time limits. For example, an organiser might propose deleting routine event-session data a short time after the event and use a separate, longer period for specific security logs, but should set those periods only after checking what is needed and documenting the reasoning. Don’t treat the ICO’s suggestion to consider refreshing consent at intervals, such as every two years where appropriate, as a rule that all consent evidence must be deleted after two years.

A practical event Wi-Fi consent checklist

Before your next show, exhibition or festival:

  1. Map the portal journey. List every field, checkbox, cookie, analytics tool and third party involved.

  2. Separate necessary access from optional choices. Make marketing opt-in optional and unbundled from access to guest Wi-Fi.

  3. Check the wording. Name the organisation, explain each purpose and channel clearly, and provide accessible privacy information.

  4. Capture an audit trail. Store the identifier, timestamp, exact wording/version, choice and withdrawal status for consent-based processing.

  5. Set purpose-based retention periods. Separate routine connection data, security logs, consent evidence and suppression records. Record why each period is needed.

  6. Check the DUAA/PECR position for device technologies. Confirm which are necessary, which may fit an exception and which require prior consent. Do not assume Wi-Fi analytics is automatically exempt.

  7. Test withdrawal and deletion. Make unsubscribe straightforward, ensure it reaches the right systems and schedule routine deletion or anonymisation.

  8. Confirm supplier roles and access. Document who controls the purposes, who processes data, how it is secured and what happens after the event.

A well-planned portal should make it easy for guests to connect without confusing them about what they are agreeing to. Commsuk can help organisers plan and manage the connectivity side, including captive portal options. Read about custom Wi-Fi landing pages, explore our event technology services, or contact the team to discuss your next event.

This article is general information, not legal advice. If your portal collects personal data or uses cookies and similar technologies, check your specific arrangements against current ICO guidance.

Further guidance

 
 
 

Comments


bottom of page