Privacy policy
Last updated 2026-11-17
VenueScreen is operated by venuescreen.com. This policy explains what we collect when you use https://venuescreen.com, the admin and remote at admin and control subdomains, the TV player, and the game controller at play.venuescreen.com, and what we do with it.
Who this covers
- Venue staff who create an account and manage screens (account holders).
- Guests who scan a QR code in a venue to play a game (players).
- Anyone who visits this website or sends us a message.
What we collect from account holders
- Your email address, which is also how you sign in. We send a one-time code to it; the code is stored hashed and expires after ten minutes.
- Your organisation and venue names, venue timezone and address if you add one, team members' email addresses, and roles.
- The content you upload or create: videos, images and Instant Cards, with their titles and schedules.
- Session records so you stay signed in: thirty days rolling, ninety days at most.
- Billing status from Stripe. Card details are entered on Stripe's pages and never reach our servers. We keep a Stripe customer reference, plan and subscription status.
- An audit log of administrative actions in your organisation (who did what, when).
What we collect from screens
- A pairing code and a device token for each TV, the browser's user agent and resolution, and a regular heartbeat so you can see which screens are online.
- A playback log: which item played on which screen and whether it completed. This is what powers proof-of-play reports.
- QR scan counts for smart QR codes you add to slides. A scan records the time, the screen, and the scanner's IP address and user agent for abuse prevention.
What we collect from players
Playing a game needs a verified email address. When a guest scans the QR code on a venue's screen:
- We send a one-time code to the email address they enter and store the code hashed. Codes expire in ten minutes.
- We store the verified email, a nickname, a chosen colour, a device fingerprint used to apply venue bans, and scores.
- On first verification we record the guest as a subscriber of that venue with the source (screen, game and date), their consent choice, the time of consent and their IP address.
- The consent box is unticked by default. Declining still allows play; the email is kept only as the game identity, with consent recorded as false.
- A long-lived play token is stored in the guest's browser for ninety days per venue so returning guests skip the email step.
The venue controls its subscriber list. We process it on the venue's behalf and never use it for our own marketing. Every message a venue sends through us carries an unsubscribe link at https://venuescreen.com/u/ which sets an unsubscribed flag that is honoured in every export.
This website
The marketing site is static and sets no cookies. It loads one third-party script, Cloudflare Web Analytics, which counts page views without cookies, fingerprinting or cross-site tracking; Cloudflare processes that data on our behalf and we see only aggregate numbers. If you change the pricing currency, that choice is kept in your browser's local storage only. If you use the contact form we receive what you type, your IP address for rate limiting, and the time.
Why we process it
- To provide the service you or your venue asked for (contract).
- To keep the service secure and prevent abuse, including rate limits and venue bans (legitimate interests).
- To send venue marketing to players who opted in (consent, withdrawable at any time via the unsubscribe link).
- To meet legal obligations, including tax and accounting records.
Where it lives and who sees it
Data is hosted in AWS eu-west-2 (London, United Kingdom). Our processors are Stripe (billing, including tax calculation), Google Workspace (outbound transactional email, sent from login@ and play@ addresses at venuescreen.com), Amazon Web Services (hosting) and Cloudflare (the network every request passes through). We do not sell personal data and do not share it with advertisers.
How long we keep it
- Account and venue data: for the life of the account and a short period after closure to allow recovery, then deleted.
- One-time codes: deleted on use or expiry.
- Original uploads: deleted seven days after successful encoding; the encoded versions remain while the asset exists.
- Playback and scan logs: kept for reporting while the organisation exists.
- Player identities and subscriber records: while the venue keeps them; venues can delete entries, and unsubscribes are kept so they are honoured.
- Server logs: retained for ninety days.
Your rights
Depending on where you live you can ask to access, correct, export or delete your personal data, object to or restrict processing, and withdraw consent. Account holders can do most of this from the admin. Players can unsubscribe from any venue message or write to us. For anything else, use the contact form. You can also complain to your local data protection authority.
We operate under the GDPR in the European Union, the Spam Act and Privacy Act in Australia, the PDPA in Singapore and the PDPL in the United Arab Emirates. The consent model described above is designed to satisfy all of them.
Changes
If this policy changes materially we will update the date above and, for account holders, say so in the admin.