Escape room plugin privacy
The booking that maps your team and films your hour in the room
An escape room sells an hour of being watched: every room runs live cameras so the game master can give hints, and many venues keep the recordings. The booking itself is a social graph — a corporate team-building reservation lists employer, department, and who showed up (and who didn't); a date night is a timestamped record of who you were with. Add the per-player waiver and the victory photo posted to the venue's social feeds with first names, and a WordPress booking plugin holds footage, affiliations, and attendance nobody thinks of as data. Those fields are configured, not documented defaults. A room booking is a calendar row, not proof anyone played. A roster answer is what a booker typed, not an HR file. An intake upload is a client document in a site uploads folder. A page request is not proof anyone entered a room. The page URL can say escape room even when no form is submitted. Ask what happens to the named teammate, employer, department, waiver, room-recording, and victory-photo rows after a team-building night ends — the booking that maps your team and films your hour outlives the puzzle. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the reservation page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a CCTV/surveillance-law claim, an employment-privacy-law claim, a venue-liability-law claim, a photo-consent-law claim, or a GDPR or other compliance assessment.
Scan your site for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, bookings, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where roster intakes, room bookings, and page tags go
Intakes and bookings on your WordPress site
Check which employer, department, team-roster, waiver-upload, room-recording, or victory-photo fields you enable, who can open form entries and room bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a team-building night ends — when the booking maps your team and films your hour. Notification emails can also copy those fields off-site. One table can list every named teammate a booker typed next to a Friday private-room slot, an employer, a department, a waiver PDF, and a victory photo. Ask your web vendor not to keep room recordings and victory photos next to employer and roster rows in one open submissions list longer than operations need, and to purge booking rows when a night ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored room booking is not proof anyone played. A roster answer is not an HR file.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the escape-room reservation or roster-intake page. That page request can reach a vendor host before anyone submits. The page URL can say escape room even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off reservation and roster-intake pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. An "escape room privacy" badge is not a verified storage path.
Roster-intake, room-booking, and marketing-tag setups
No paid placement. Site-hosted tools appear first, followed by vendor-hosted tools. Names are alphabetical within each group.
Three plugins reviewed from public documentation. Specialty escape-room SaaS tools without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Easy Appointments Documented self-hosted appointment plugin marketed for service businesses (plugin version 4.0.3). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A Friday private-room slot or a corporate team-building package is a booking you create; a service name such as escape room or private room is a label you configure. Neither is a documented default. Employer, department, team-roster, waiver-upload, room-recording, or victory-photo questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof anyone played — and a CSV export of a Friday 7pm private room next to Acme Corp, Marketing, "Alex, Jordan, Sam", and a waiver PDF filename is still a calendar that holds a social graph and attendance list beside a contact name. Emails can include those custom fields and copy the appointment off-site. An optional GDPR setting can auto-remove customer data older than six months; that is not a default purge. Google Calendar, SMS, and payments are Pro. Google reCAPTCHA is optional. Public booking-form browser hosts are unverified. | Room bookings stored on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| Forminator Forms – Contact Form, Payment Form & Custom Form Builder Documented self-hosted form builder (plugin version 1.58.1). The listing states Forminator stores and organizes submissions so you can sort, analyze, and manage responses, and includes a free file-upload field with multi-file support. Version 1.58.1 helper-fields.php forminator_upload_root() writes under the WordPress uploads directory plus /forminator/, with per-form hashed subfolders from forminator_get_upload_path(). upload.php stores files through that path. Employer, department, team-roster, waiver-upload, room-recording, or victory-photo fields are fields you add; they are not documented defaults. Completing the form can store a named teammate next to a room booking, a contact name, an employer, a department, optional waiver uploads, a session recording, and a victory photo — typed once so the venue can staff the game master and know who showed up, into the same tables as a package name. A roster answer is what a booker typed, not an HR file. A room booking is a calendar row, not proof anyone played — and a staff login can open "Alex + Jordan, Acme Corp / Marketing, waiver.pdf, room.mp4, victory.jpg, Friday 7pm private room" next to everyone else's resume. Notification emails can copy field values and files off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | Employer, roster, and waiver answers stored in WordPress; optional room-recording and victory-photo uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| PixelYourSite – Your smart PIXEL (TAG) & API Manager Documented pixel and tag manager (plugin version 11.4.2.1). When a Meta Pixel ID is saved, version 11.4.2.1 dist/scripts/public.js loads https://connect.facebook.net/en_US/fbevents.js. A noscript image uses https://www.facebook.com/tr. Google Analytics 4, Google Tag Manager, and Head and Footer scripts load only when you enable them. Automated events include form submissions; those events do not by themselves prove that an employer, department, team-roster, waiver, room-recording, or victory-photo field was sent. A page request from this script is not proof anyone entered a room. The page URL can say escape room even when no form is submitted. Consent timing has not been tested. Review which tags you enable on reservation and roster-intake pages. | Marketing tags handled through Meta, Google, or other configured platforms | connect.facebook.net | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Employer, department, team-roster, waiver-upload, room-recording, or victory-photo fields often depend on the fields you configure. A room booking is a calendar row, not proof anyone played. A roster answer is what a booker typed, not an HR file. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone entered a room. The page URL can say escape room even when no form is submitted. The booking that maps your team and films your hour in the room — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that venue social-graph and camera stack, not a trampoline-park kiosk waiver, a race-registration waiver, a class-reunion RSVP list, or a photography gallery business. Ask your web vendor who can open entries, whether a marketing tag loads on the reservation page, and how long records and backups are kept. An "escape room privacy" or "team-building compliant" badge is not a verified storage path. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess CCTV/surveillance law, employment privacy law, venue liability law, or photo-consent law. Review stored records, bookings, connected services, exports, notification emails, marketing tags on reservation and roster-intake pages, and backups.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-escape-room-plugin-privacy