Slounger is built to evidence how loungers were managed — not to profile the people using them. Here is what the system collects, what it does not, and who controls it.
Last updated · July 2026
Guests can scan any lounger or zone QR code and browse live availability without identifying themselves. No account, no app install, no personal data.
Identification happens only at the moment a guest claims a lounger, books a slot, or requests a staff check — via their cabin card, booking reference, or a magic link. Booking references are stored as hashes, never in plain text.
The audit trail is an operational record of actions around loungers: requests, staff checks, grace periods, releases, blocks, reassignments and overrides — each with an actor role, a timestamp, an outcome and a reason.
It exists so operators can evidence active management. It is not a guest-surveillance log: it records what was done about a lounger, not where a guest is or what they do elsewhere.
Anonymous scans are counted to help operators understand demand and signage placement. These events carry no personal data — only the scanned target, an outcome, and a rate-limiting fingerprint hash. They are retained for 30 days, then deleted.
We do not sell or share guest data with advertisers. We do not track guest location. We do not show one guest another guest’s identity or booking details. Staff see lounger status and tasks — not guest profiles.
For pilot and production deployments, the operator is the data controller and Slounger processes data on the operator’s instructions under a data-processing agreement. Retention periods for audit records are set per property, within agreed limits.
Ask us anything about data handling at hello@slounger.app — including during a pilot scoping conversation.
Start with a QR-led pilot in one zone and measure the impact on complaints, staff response, guest flashpoints and usable availability.
Not sure yet? Assess your sunbed management risk