Laser tag plugin privacy
The party roster that files twelve kids' names and birthdays under one parent's email
A laser tag booking is never one person's data — it's a party manifest. One parent's email becomes the index key for a dozen other families' children: every kid's name and birthday from the invite list, signed into the waiver kiosk in a queue while the party host holds the pizza. The scoreboard then broadcasts those kids' nicknames on the lobby TV, and the plugin keeps the roster long after the cake is gone. The person whose inbox anchors the record never consented on behalf of anyone but their own child. Those fields are configured, not documented defaults. A party booking is a calendar row, not proof anyone played. A roster answer is what a booker typed, not a school enrollment file. An intake upload is a client document in a site uploads folder. A page request is not proof anyone entered an arena. The page URL can say laser tag even when no form is submitted. Ask what happens to the host email, kids' names, birthdays, invite list, waiver, and lobby nicknames after the party ends — the party roster that files twelve kids' names and birthdays under one parent's email outlives the cake. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the party page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a children's-privacy-law claim, a COPPA claim, a parental-consent-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 party answers, roster bookings, and page tags go
Intakes and bookings on your WordPress site
Check which party-host email, child-name, birthday, invite-roster, waiver, or scoreboard-nickname fields you enable, who can open form entries and party bookings, which inboxes receive copies, and how long records, emails, and backups are kept after the cake is gone — when the party roster files twelve kids' names and birthdays under one parent's email. Notification emails can also copy those fields off-site. One table can list every kid a host typed next to a birthday, a waiver signed at the kiosk, and a lobby nickname that played on the TV. Ask your web vendor not to keep kids' names next to host emails and waiver scans in one open submissions list longer than operations need, and to purge roster fields when a party closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored party booking is not proof anyone played. A roster answer is not a school enrollment file.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the laser-tag party or booking page. That page request can reach a vendor host before anyone submits. The page URL can say laser tag even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off party and booking pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "laser tag privacy" badge is not a verified storage path.
Party-roster, booking, and marketing-tag setups
Three plugins reviewed from public documentation. Specialty laser-tag / arena SaaS tools without a WordPress.org listing are outside this sample.
No paid placement. Site-hosted tools appear first, followed by vendor-hosted tools. Names are alphabetical within each group.
| 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 Saturday birthday-party slot or an arena block is a booking you create; a service name such as laser tag or birthday package is a label you configure. Neither is a documented default. Child-name, birthday, invite-roster, waiver, scoreboard-nickname, or party-host 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 "host@mail.com, Mia (8), Noah (9), Ava (7), Sat party" next to a contact name is still a calendar that holds a party roster under one parent's email. 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. | Party and arena 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. Party-host email, child-name, birthday, invite-roster, waiver, or scoreboard-nickname fields are fields you add; they are not documented defaults. Completing the form can store one parent's email next to a dozen kids' names and birthdays from an invite list, a waiver signed at the kiosk while the host holds the pizza, lobby nicknames, a contact name, and optional waiver uploads — typed once so the front desk does not have to re-key the party, into the same tables as a birthday-package label. A roster answer is what a booker typed, not a school enrollment file. A party booking is a calendar row, not proof anyone played — and a staff login can open "host@mail.com, Mia (8), Noah (9), Ava (7), waiver PDF" 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. | Party-host, child-name, and birthday answers stored in WordPress; optional waiver 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 a party-host email, child-name, birthday, invite-roster, waiver, or scoreboard-nickname field was sent. A page request from this script is not proof anyone entered an arena. The page URL can say laser tag even when no form is submitted. Consent timing has not been tested. Review which tags you enable on party intake and booking 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. Party-host email, child-name, birthday, invite-roster, waiver, or scoreboard-nickname fields often depend on the fields you configure. A party booking is a calendar row, not proof anyone played. A roster answer is what a booker typed, not a school enrollment file. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone entered an arena. The page URL can say laser tag even when no form is submitted. The party roster that files twelve kids' names and birthdays under one parent's email — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that party-manifest and kid-roster stack, not a trampoline-park single-jumper kiosk waiver, a youth-sports-league season roster, an escape-room adult group booking, or a race-registration self-registered adult waiver. Ask your web vendor who can open entries, whether a marketing tag loads on the party page, and how long records and backups are kept. A "laser tag privacy" or "arena-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 children's privacy law, COPPA, parental-consent law, venue liability law, or photo-consent law. Review stored records, bookings, connected services, exports, notification emails, marketing tags on party and booking 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-laser-tag-plugin-privacy