Guest Wi‑Fi and GDPR: privacy policy, consent and data retention
Updated
Offering Wi‑Fi to guests means processing personal data: name, e-mail and device address. Captive Portal gives you the tools to manage it; texts, legal bases and retention periods remain your choice, as the data controller.
The privacy policy
Write it in Portal settings → Privacy → Privacy policy, with one text per language.
If available, Load the template inserts a starting text: complete the parts in square brackets and have it reviewed before saving.
Every guest must accept it to sign in or use a voucher.
Every change to the text creates a new version, archived exactly as it was: Published versions shows how many registrations accepted each version. For every registration you know which text was accepted.
Marketing consent
Marketing consent in the registration form adds an optional checkbox to the form, never ticked by default, with a text you can customize. Guests who tick it and confirm their e-mail appear under Marketing contacts, with date, time and text of the consent.
From Marketing contacts you can revoke a consent and export the active consents as CSV.
Voucher access has no e-mail, so no marketing consent.
Marketing contacts do not follow the log retention: they stay until the consent is revoked.
Data retention
In Portal settings → Privacy → Guest data retention, set how many Days to keep guests’ name, e-mail and MAC address. When the period ends they are anonymized every night: only the data for statistics and counts remains. Guests still connected are anonymized when their access ends.
When a guest asks what data you hold about them, or asks you to delete it, see Answer guests’ privacy requests.
Frequently asked questions
What remains after anonymization?
Date, site, outcome, language, device type, verification method, accepted policy version and traffic: data useful for statistics, without name, e-mail or device address.
Do registered guests have to accept the updated policy again?
The new version applies to new registrations; for each registration, the accepted version stays archived.