Water park plugin privacy

The season pass that keeps a photo diary of your child's summer

A season pass is the only retail product that requires a photograph of your child: the pass-holder record pairs that photo with the child's name and birthday, then logs a timestamped row at the gate every single visit — by Labor Day the plugin holds a summer-long attendance diary of a minor, renewed with a fresh photo each year. Parents happily hand this over for line-skipping; no one ever asks where the previous summers' photos went. Those fields are configured, not documented defaults. A season-pass booking is a calendar or membership row, not proof a child entered the park. A pass photo is a file a parent uploaded or staff stored, not a school ID or government photo. A gate stamp is a timestamped row staff logged, not proof of custody. A page request is not proof anyone bought a pass. The page URL can say water park even when no form is submitted. Ask what happens to the season-pass rows, the pass photos, the birthdays, and the gate-visit stamps after Labor Day — the season pass that keeps a photo diary of your child's summer outlives the last splash. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the pass page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a minors-law claim, a COPPA assessment, a photo-ID-retention-law claim, an attendance-diary-as-consent 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 season passes, pass photos, gate stamps, and page tags go

Intakes and bookings on your WordPress site

Check which season-pass, child-name, birthday, pass-photo, or gate-visit fields you enable, who can open form entries and pass bookings, which inboxes receive copies, and how long records, emails, and backups are kept after the season ends — when the season pass that keeps a photo diary of your child's summer still holds that row. Notification emails can also copy those fields off-site. One table can list a parent name next to a child name and birthday, a pass photo, and a summer of gate-visit stamps. Ask your web vendor not to keep pass photos next to attendance diaries in one open submissions list longer than operations need, and to purge those fields when a season closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored season-pass booking is not proof a child entered the park. A pass photo is not a school ID.

Page tags handled by a vendor

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

Season-pass, booking, and marketing-tag setups

Three plugins reviewed from public documentation. Specialty water-park / season-pass 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.

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 season-pass renewal window or a gate check-in block is a booking you create; a service name such as water park or season pass is a label you configure. Neither is a documented default. Season-pass, child-name, birthday, pass-photo, or gate-visit 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 entered the park — and a CSV export of "Jordan Lee, child: Maya DOB 2016-06-12, pass photo on file, gate visits: 47" next to a contact name is still a calendar that holds a summer attendance diary next to a child photograph. 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.

Season-pass and gate 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. Season-pass, child-name, birthday, pass-photo, or gate-visit fields are fields you add; they are not documented defaults. Completing the form can store a parent name next to a child name and birthday, a pass photo upload, a contact name, and optional waiver uploads — typed once so the gate does not have to re-key the pass, into the same tables as a water-park label. A pass photo is a file a parent uploaded, not a school ID. A season-pass booking is a membership row, not proof a child entered the park — and a staff login can open "Jordan Lee, child Maya DOB 2016-06-12, pass photo, gate visits 47" 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.

Season-pass and pass-photo answers stored in WordPress; optional 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 season-pass, child-name, birthday, pass-photo, or gate-visit field was sent. A page request from this script is not proof anyone bought a pass. The page URL can say water park even when no form is submitted. Consent timing has not been tested. Review which tags you enable on season-pass 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. Season-pass, child-name, birthday, pass-photo, or gate-visit fields often depend on the fields you configure. A season-pass booking is a calendar or membership row, not proof a child entered the park. A pass photo is a file a parent uploaded or staff stored, not a school ID or government photo. A gate stamp is a timestamped row staff logged, not proof of custody. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone bought a pass. The page URL can say water park even when no form is submitted. The season pass that keeps a photo diary of your child's summer — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that season-pass photo and gate-visit stack, not a trampoline-park kiosk waiver, a swim-school lesson roster, a summer-camp medical card, or a campground family-whereabouts form. Ask your web vendor who can open entries, whether a marketing tag loads on the season-pass page, and how long records and backups are kept. A "water park privacy" or "season-pass-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 minors law, COPPA, photo-ID retention law, or attendance-diary-as-consent. Review stored records, bookings, connected services, exports, notification emails, marketing tags on season-pass pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-water-park-plugin-privacy