Youth sports league plugin privacy
The registration row behind the game schedule the whole town can read
A youth sports registration can look like a name and a jersey size. It also stores a child's date of birth, medical and allergy notes, a photo-consent answer, and a parent's phone. The league site publishes the other half on purpose: team rosters, game schedules, and field assignments so families can show up. The private row and the public schedule describe the same child. The schedule says which field, which Saturday, which jersey number. The form table says the rest. The photo-consent checkbox is the quiet star: the one field whose answer is a parent saying no, stored next to everything the no was protecting. Date-of-birth, medical-note, photo-consent, and birth-certificate-upload fields are configured, not documented defaults. The public schedule cannot be unpublished by deleting the form row. Ask which half outlives the season, and who can still open last season's registrations. A registration row is not proof a child played. A page request is not proof anyone registered. A published schedule is the league's choice, not the plugin's. A photo-consent answer is a stored preference, not an enforced control. The page URL can say youth sports even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on registration pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a child-safety-law claim, a COPPA claim, a SafeSport claim, a background-check-law claim, a league-governance 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, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where registrations, child files, and page tags go
Registrations and child files handled on your WordPress site
Check which date-of-birth, medical-note, photo-consent, or birth-certificate-upload fields you enable, who can open form entries and the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a season that never became a roster. Notification emails can also copy the same child row off-site. One table can list every registered child even when only a parent typed. Ask your web vendor not to collect a medical note or a photo-consent answer on the first public form, not to store that row next to a public schedule in one open submissions list, and to purge registrations after the season. A privacy-policy page does not by itself limit who can open an uploads folder. A stored registration is not proof a child played. Deleting a form row does not unpublish last season's schedule.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the youth sports registration page. That page request can reach a vendor host before anyone submits. The page URL can say youth sports even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off registration pages if you do not want that page request. A browser scan cannot inspect stored child rows. A "secure registration" badge is not a verified storage path.
Youth sports registration, child-file-upload, 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 league-ops or sports-management software without a WordPress.org listing is outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Drag and Drop Multiple File Upload for Contact Form 7 Documented Contact Form 7 upload extension (plugin version 1.4.0). Version 1.4.0 drag-n-drop-upload-cf7.php defines wpcf7_dnd_dir as wp_dndcf7_uploads. The listing states the free version moves files to wp-content/uploads/wp_dndcf7_uploads, attaches them to mail, then removes them from that temporary folder about one hour after submission. That cleanup does not remove copies already sent as email attachments. A birth-certificate, signed-waiver, or medical-clearance file is a file you accept; it is not a documented default. The uploads folder can hold those files next to the registration list. A declined registration can still leave the file until the documented cleanup, and the email copy can remain. An uploaded birth certificate is not proof a child played. Pro documents saving to the Media Library, changing the upload directory, auto-delete timers, and remote storage to OneDrive, Google Drive, Amazon S3, Dropbox, or FTP. Public upload-page browser hosts are unverified. | Visitor files stored under wp-content/uploads/wp_dndcf7_uploads | 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. Child-name, date-of-birth, medical-note, allergy, photo-consent, or parent-contact questions are fields you add; they are not documented defaults. Completing the form can record a registration. A submitted registration is not proof a child played. A photo-consent answer is a stored preference, not an enforced control. A staff login can open the child row next to contact details and other configured fields. Last season's registrations can still be opened after the public schedule is taken down. 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. | Registration entries stored in WordPress; child-file 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 child-name, date-of-birth, medical-note, or photo-consent field was sent. A page request from this script is not proof anyone registered. The page URL can say youth sports even when no form is submitted. Consent timing has not been tested. Review which tags you enable on registration 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. Date-of-birth, medical-note, photo-consent, or birth-certificate-upload fields often depend on the fields you configure. A registration row is not proof a child played. A page request is not proof anyone registered. A published schedule is the league's choice, not the plugin's. A photo-consent answer is a stored preference, not an enforced control. A marketing-tag page request is not proof anyone registered. The page URL can say youth sports even when no form is submitted. The public schedule cannot be unpublished by deleting the form row. Last season's registrations can still be opened. This page is about a child registration next to a public schedule, not an adult race-registration results page, a school-carpool member roster, a summer-camp signup, a daycare intake, or a tutoring form. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the registration page, and how long records and backups are kept. A "secure" or "confidential registration" 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 child-safety law, COPPA, SafeSport, background-check law, or league governance. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on registration pages, and backups.
Documentation snapshot: Oct 14, 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-youth-sports-league-plugin-privacy