Gymnastics plugin privacy

The meet roster that posts which hotel the ten-year-olds sleep in

A competitive gymnastics club site can look like class schedules and a meet calendar. It also runs travel-meet logistics through the same form plugin as the contact page — rosters pairing minors' full names and birth dates with meet dates, hotel blocks, and room assignments. Add skill-progression video uploads and leotard-sizing or growth records and one plugin's entries table holds a longitudinal file on a child that the family never sees assembled in one place. Minor-name, birth-date, meet-date, hotel-block, room-assignment, skill-video, leotard-size, and growth-record fields are configured, not documented defaults. Optional skill videos go in the site uploads folder. A meet booking is not proof a child traveled. A hotel-block answer is a stored note, not a verified reservation. A page request is not proof anyone enrolled. The page URL can say gymnastics even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and attendance lists, which checkout scripts load on membership pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a COPPA claim, a custody claim, an abuse-reporting 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, event bookings, uploaded files, email inboxes, staff permissions, membership accounts, or backups.

Where meet rosters, travel bookings, and membership checkouts go

Forms and meet bookings handled on your WordPress site

Check which minor-name, birth-date, meet-date, hotel-block, room-assignment, skill-video, leotard-size, or growth-record fields you enable, who can open form entries and event bookings, where uploaded skill videos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after the meet ends. Notification emails can also copy the same minor name and hotel block off-site. One table can name every ten-year-old, their birth date, and which hotel room they sleep in next to a parent contact, even when the meet is over. Ask your web vendor not to collect hotel room assignments next to birth dates on the first public form, not to store skill videos next to growth records in one open submissions list, and to purge travel rosters after the meet date. A privacy-policy page does not by itself limit who can export an attendance list. A stored booking is not proof a child traveled.

Membership checkout handled by a vendor

Some membership tools load a payment vendor script when a visitor opens the club registration or checkout page. That page request can reach a vendor host before anyone finishes paying. The page URL can say gymnastics even when no form is submitted. Review which gateways you enable, account access, and retention there. Keep travel-roster fields off membership checkout pages if you do not want that path mixed with payment. A browser scan cannot inspect stored hotel blocks, birth dates, or skill videos. A "team member" badge is not a verified storage path.

Gymnastics meet-roster, events, and membership 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 gym-management or meet-scoring SaaS without a WordPress.org listing is outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Events Manager (local bookings)

Documented Events Manager privacy docs: booking and event submissions are collected and stored on your site for reservations and attendance records. A travel meet is an event you create; custom booking fields for minor name, birth date, hotel block, or room assignment are fields you configure. Neither is a documented default. A booked meet is not proof a child traveled. A room-assignment answer is a stored note, not a verified hotel reservation. Optional Pro payment gateways (PayPal, Stripe, and others), Google Maps, and location autocomplete are outside this local-bookings row. Cancelling attendance later does not by itself prove roster fields were purged from bookings, exports, or notification emails already delivered. Review which booking fields you collect for travel meets and who can open attendance lists.

Meet and travel bookings stored on your WordPress site for reservations and attendanceBrowser 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, birth-date, meet-date, hotel-block, room-assignment, skill-video, leotard-size, or growth-record questions are fields you add; they are not documented defaults. A skill-progression video is a file you accept; that file type is not a documented default. A travel form is not proof a child traveled. A hotel-block answer is a stored note, not a verified reservation. A past meet still leaves the minor name, birth date, and room assignment in the submissions list. Notification emails can copy field values and file links off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. How long a roster row sits after the meet ends is not a documented default of the plugin.

Meet-roster and travel form entries stored in WordPress; skill-video uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
Paid Memberships Pro

Documented Paid Memberships Pro when a Stripe gateway is active: checkout loads Stripe payment scripts on the public registration or payment page (stripe.com / stripe.network). Membership levels for competitive teams are labels you configure; they are not documented defaults. A membership checkout is not proof a child is on a travel roster. Minor-name, birth-date, hotel-block, or growth-record fields collected on a separate intake form are outside this checkout row. A page request from Stripe scripts is not proof anyone enrolled. Consent timing has not been tested. Review which membership fields you collect, who can open member lists, and how long member records sit after a child leaves the club.

Club membership checkout handled through Stripe on the public registration or payment pagestripe.com, stripe.networkNot assessedNot tested

What this table does and does not prove

This is a documentation review, not a test of your site. Minor-name, birth-date, meet-date, hotel-block, room-assignment, skill-video, leotard-size, or growth-record fields often depend on the fields you configure. A meet booking is not proof a child traveled. A hotel-block answer is a stored note, not a verified reservation. A membership page request is not proof anyone enrolled. The page URL can say gymnastics even when no form is submitted. The roster and the hotel block can sit after the meet ends. This page is about a travel-meet roster pairing minors with hotel rooms, not a trampoline kiosk waiver, not a laser-tag birthday party roster, not a surf-school swim disclosure, not a summer-camp medical card, and not a gym body-measurement membership file. Ask your web vendor who can open entries and attendance lists, where uploaded skill videos live, whether checkout scripts load on membership pages, and how long records and backups are kept. A "team member" 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, custody, or abuse reporting. Review stored records, uploaded files, connected services, exports, notification emails, membership checkouts, and backups.

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

Related pages

Scan your site for third-party requests

/wp-gymnastics-plugin-privacy