Consent rules vary by jurisdiction and by the kind of communication being sent, so this page is not legal advice. The practical design principle is simpler: do not hide a marketing relationship inside the act of requesting internet access.
Practical checklist
- Make access terms and marketing permission understandable.
- Do not pre-check optional marketing boxes where that would be inappropriate.
- Record what a person agreed to and when.
- Make unsubscribe and preference controls easy to find.
- Review SMS, email and privacy requirements for the jurisdictions you serve.
Separate four different decisions
A clear implementation distinguishes: permission to use the network, acceptance of network terms, permission to receive marketing, and permission for any additional tracking or profiling. The exact legal requirements vary, but combining all four into one vague checkbox creates both user-experience and compliance risk.
Operational records to keep
- The wording shown at the time of consent.
- Timestamp and relevant guest/account identifier.
- The channel or purpose the person agreed to.
- Unsubscribe or withdrawal events.
- Retention/deletion rules for guest records.
Design for the guest, not only the database
Shorter, clearer permission language can improve data quality because guests understand what will happen next. Avoid collecting fields or permissions that the business cannot operationally honor.
Make withdrawal as operational as opt-in
Consent is not useful if the business cannot honor a later unsubscribe or deletion request. Document which system is the source of truth, how suppression status moves between the WiFi platform and email/SMS tools, and who owns requests that arrive through support staff. Test the process with an internal record before collecting large volumes of guest data.
Review changes when the workflow changes
New CRM integrations, new messaging channels and new profiling/analytics can change what happens to a guest record. Treat those changes as a reason to review the visible notice and internal retention process rather than assuming an old checkbox still describes the current workflow. This is operational guidance, not legal advice; requirements depend on jurisdiction and the business’s actual practices.
For implementation, see how to capture emails from guest WiFi.