Trampoline park plugin privacy

The kiosk waiver that files a child's injury history forever

A trampoline park's lobby kiosk looks like a gate to bounce. The same waiver form stores each minor's name, date of birth, and pre-existing injury or condition disclosures next to a parent's signature and contact — a liability form built to survive lawsuits, retained for years in the same WordPress install as the party-deposit form. Birthday-party bookings add full guest lists of other people's children, entered by a host who never asked those parents. Those fields are configured, not documented defaults. Before anyone jumps, the kiosk asks what already hurt. A party booking is a calendar row, not proof a child bounced. A pre-existing-injury answer is the parent's note, not a chart. A guest-list name is what a host typed, not consent from that child's parent. A child named in the form never touched it. A signed-waiver upload is a client document in a site uploads folder. A page request is not proof any child bounced. The page URL can say trampoline park even when no form is submitted. Ask what happens to the injury disclosure and the party guest list after the visit — the kiosk waiver that files a child's injury history forever outlives the first bounce. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the waiver page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a COPPA or child-privacy-law claim, a child-safeguarding or park-safety claim, a liability-waiver enforceability claim, a medical-fitness claim, or a GDPR or other compliance assessment.

Scan your site for third-party requests

The 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 open-jump bookings, kiosk waivers, and page tags go

Waivers and bookings on your WordPress site

Check which minor-name, date-of-birth, pre-existing-injury, parent-signature, parent-contact, party-guest-list, emergency-contact, or signed-waiver-upload fields you enable, who can open form entries and open-jump or birthday-party bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the kiosk waiver files a child's injury history forever. Notification emails can also copy those fields off-site. One table can list every pre-existing-injury note a parent typed next to a party slot and a guest list of other people's children. Ask your web vendor not to keep signed waivers next to injury disclosures in one open submissions list longer than operations need, and to purge booking rows when a party is cancelled or a visit closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored party booking is not proof a child bounced. A guest-list name is not consent from that child's parent.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the trampoline-park waiver or party-booking page. That page request can reach a vendor host before anyone submits. The page URL can say trampoline park even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off kiosk-waiver and birthday-party pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "kids bounce safety" badge is not a verified storage path.

Open-jump booking, trampoline-park kiosk waiver, 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 park-management SaaS tools without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
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 open-jump block or a birthday-party slot is a booking you create; a service name such as open jump or birthday party is a label you configure. Neither is a documented default. Minor-name, date-of-birth, pre-existing-injury, parent-signature, parent-contact, party-guest-list, or emergency-contact questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof a child bounced — and a CSV export of a party row next to a minor name and a pre-existing-injury note is still a calendar that holds an injury history 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.

Open-jump and birthday-party bookings stored on your WordPress siteBrowser hosts not verifiedNot assessedNot tested
  • None
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. Minor-name, date-of-birth, pre-existing-injury, parent-signature, parent-contact, party-guest-list, or emergency-contact fields are fields you add; they are not documented defaults. Completing the form can store a child's name and date of birth next to a pre-existing-injury disclosure, a parent signature, a parent contact, a birthday-party guest list of other people's children, an emergency contact, and optional signed-waiver uploads — typed once as the kiosk waiver that files a child's injury history forever, into the same tables as a newsletter signup. A pre-existing-injury answer is the parent's note, not a chart. A guest-list name is what a host typed, not consent from that child's parent — and a staff login can open "Jordan, DOB 2017-04-12, prior ankle sprain, parent sig on file, mom cell, party guests: Avery Mia Noah, emergency dad, waiver.pdf" next to everyone else's resume. A child named in the form never touched it. 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.

Trampoline-park kiosk waiver intake stored in WordPress; optional signed-waiver uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
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 minor-name, date-of-birth, pre-existing-injury, parent-signature, parent-contact, party-guest-list, or emergency-contact field was sent. A page request from this script is not proof any child bounced. The page URL can say trampoline park even when no form is submitted. Consent timing has not been tested. Review which tags you enable on open-jump, birthday-party, and trampoline-park kiosk-waiver pages.

Marketing tags handled through Meta, Google, or other configured platformsconnect.facebook.netNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Minor-name, date-of-birth, pre-existing-injury, parent-signature, parent-contact, party-guest-list, emergency-contact, or signed-waiver-upload fields often depend on the fields you configure. A party booking is a calendar row, not proof a child bounced. A pre-existing-injury answer is the parent's note, not a chart. A guest-list name is what a host typed, not consent from that child's parent. A child named in the form never touched it. A signed-waiver upload is a client document in a site uploads folder. A marketing-tag page request is not proof any child bounced. The page URL can say trampoline park even when no form is submitted. The kiosk waiver that files a child's injury history forever — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that same-day kiosk waiver and party guest list, not a summer-camp multi-day camper card, a youth-sports-league season roster, or a race-registration adult/event waiver. Ask your web vendor who can open entries, whether a marketing tag loads on the waiver page, and how long records and backups are kept. A "kids bounce safety" 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 COPPA, child-safeguarding standards, park or facility safety, liability-waiver enforceability, or medical fitness. Review stored records, bookings, connected services, exports, notification emails, marketing tags on waiver pages, and backups.

Documentation snapshot: Oct 14, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-trampoline-park-plugin-privacy