Paintball plugin privacy
The team-building booking that files your coworkers' injury waivers together
Paintball's biggest bookings aren't birthday parties — they're corporate team-building days. HR books once, and thirty employees sign injury waivers acknowledging bruising risk and listing pre-existing conditions, all stored under the company's reservation. Your health acknowledgment now lives in a paintball field's WordPress because your employer wanted a bonding exercise — data you never chose to give a business you never chose to visit, indexed by the one party (your employer) who should least see it. Those fields are configured, not documented defaults. A team-building booking is a calendar row, not proof anyone played. A waiver answer is what a guest typed or uploaded, not a medical finding. A pre-existing-condition note is what someone typed, not a diagnosis. A page request is not proof anyone stepped onto a field. The page URL can say paintball even when no form is submitted. Ask what happens to the company reservation, the coworker names, the bruising-risk acknowledgments, and the pre-existing-condition notes after the outing ends — the team-building booking that files your coworkers' injury waivers together outlives the last match. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a venue-liability-law claim, a workers-comp claim, an employer-access-law claim, a HIPAA assessment, an injury-claim assessment, 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 company-indexed waivers, team bookings, and page tags go
Intakes and bookings on your WordPress site
Check which company-name, injury-waiver, bruising-risk, pre-existing-condition, or coworker-roster fields you enable, who can open form entries and team-building bookings, which inboxes receive copies, and how long records, emails, and backups are kept after the outing ends — when the team-building booking that files your coworkers' injury waivers together still holds that row. Notification emails can also copy those fields off-site. One table can list a company reservation next to thirty legal names, bruising-risk acknowledgments, and pre-existing-condition notes. Ask your web vendor not to keep employer-indexed health acknowledgments next to coworker rosters in one open submissions list longer than operations need, and to purge those fields when a team booking closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored team-building booking is not proof anyone played. A waiver answer is not a medical finding.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the paintball team-building booking page. That page request can reach a vendor host before anyone submits. The page URL can say paintball even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "paintball privacy" badge is not a verified storage path.
Team-building waiver, booking, and marketing-tag setups
Three plugins reviewed from public documentation. Specialty paintball / field 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 corporate team-building block or a field check-in window is a booking you create; a service name such as paintball or team day is a label you configure. Neither is a documented default. Company-name, injury-waiver, bruising-risk, pre-existing-condition, or coworker-roster 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 "Acme Corp team day, Sam Rivera: bruising risk ack, prior shoulder injury, employer contact: HR" next to a contact name is still a calendar that holds thirty coworker waivers under one company reservation. 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. | Team-building and field 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. Company-name, injury-waiver, bruising-risk, pre-existing-condition, or coworker-roster fields are fields you add; they are not documented defaults. Completing the form can store a legal name next to a bruising-risk acknowledgment, a pre-existing-condition note, a company reservation label, a contact name, and optional waiver uploads — typed once so the field does not have to re-key thirty employee waivers, into the same tables as a paintball label. A waiver answer is what a guest typed or uploaded, not a medical finding. A team-building booking is a calendar row, not proof anyone played — and a staff login can open "Acme Corp team day — Sam Rivera, bruising risk ack, prior shoulder injury" 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. | Waiver and pre-existing-condition answers stored in WordPress; optional 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 company-name, injury-waiver, bruising-risk, pre-existing-condition, or coworker-roster field was sent. A page request from this script is not proof anyone stepped onto a field. The page URL can say paintball even when no form is submitted. Consent timing has not been tested. Review which tags you enable on team-building 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. Company-name, injury-waiver, bruising-risk, pre-existing-condition, or coworker-roster fields often depend on the fields you configure. A team-building booking is a calendar row, not proof anyone played. A waiver answer is what a guest typed or uploaded, not a medical finding. A pre-existing-condition note is what someone typed, not a diagnosis. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone stepped onto a field. The page URL can say paintball even when no form is submitted. The team-building booking that files your coworkers' injury waivers together — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that company-indexed waiver stack, not a laser-tag kids party roster, an axe-throwing waiver-plus-bar-tab, a go-kart license kiosk, a rock-climbing health intake, or an EAP counseling employer-adjacent form. Ask your web vendor who can open entries, whether a marketing tag loads on the booking page, and how long records and backups are kept. A "paintball privacy" or "team-building-safe" 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 venue liability law, workers-comp, employer-access law, HIPAA, or injury claims. Review stored records, bookings, connected services, exports, notification emails, marketing tags on 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-paintball-plugin-privacy