Pageant coach plugin privacy
The application that files a child's photos, measurements, and travel calendar in one row
A pageant-coaching application can be a dossier on a minor: headshots and full-body photos, height, weight, and measurements, age division, school schedule, and a competition travel calendar — typed by a parent into one entries table. The child named in those fields is a data subject who never opened the form. An areas-to-improve coach-notes field can store a ranked critique of the child's appearance next to that same row. Headshot, full-body-photo, height, weight, measurements, age-division, school-schedule, competition-travel-calendar, areas-to-improve, child-name, parent-name, phone, email, and appointment-date fields are configured, not documented defaults. A photo upload is a stored file, not proof of a competition. A measurement answer is a stored number or note, not a fitting record. An areas-to-improve note is a stored textarea, not a verified ranking. A school schedule is a stored calendar note, not proof of attendance. A travel calendar is a stored itinerary field, not proof anyone traveled. A pageant-coach application is not proof anyone competed. A page request is not proof anyone applied. The page URL can say pageant coach even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open applications, bookings, and photo files, and how long records, photos, emails, and backups are kept.
Documentation review only. This is not legal advice, a COPPA or child-privacy-law claim, a child-safeguarding claim, a pageant-outcome claim, a coaching-quality 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, bookings, uploaded photos, email inboxes, staff permissions, vendor accounts, or backups.
Where photos, measurements, and travel calendars go
Pageant applications and bookings handled on your WordPress site
Check which height, weight, measurements, age-division, school-schedule, competition-travel-calendar, areas-to-improve, child-name, parent-name, phone, email, or appointment-date fields you enable, who can open form entries and bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a coaching season that never started. Notification emails can also copy the same measurement answers, travel calendars, and areas-to-improve notes off-site. One table can name the child, the measurements, the school schedule, and an areas-to-improve note next to a parent phone, even when no coaching begins. Ask your web vendor not to collect photos, measurements, and a travel calendar next to an areas-to-improve textarea on the first public form, not to store those fields next to child names in one open submissions list, and to purge unused application rows after the coaching window closes. A privacy-policy page does not by itself limit who can export an application list. A stored photo is not proof of a competition.
Headshots and full-body photos on your WordPress site
Some upload tools store headshot and full-body-photo originals under your WordPress uploads folder and can keep files reachable by direct URL after the season. A photo tied to a child name can sit after a coaching season that never started. Review who can open uploads, whether image files remain reachable without a form login, and how long originals are kept. A browser scan cannot inspect stored applications or photo files that never load in the visitor browser. A "private coaching dossier" badge is not a verified storage path.
Pageant-coach application, booking, and photo-upload 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 pageant-management SaaS tools without a WordPress.org listing are outside this sample.
| 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). The listing documents automatic email notifications: customers get instant booking confirmations; staff get notified; templates can include booking information and custom fields; customers can confirm or cancel via a link in the email. WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A pageant coaching consult is a booking you create; a service name such as pageant coach intake, competition prep session, or travel-week consult is a label you configure. Neither is a documented default. The stored service name can say pageant coach in plain text before anyone arrives. Height, weight, measurements, age-division, school-schedule, competition-travel-calendar, areas-to-improve, child-name, parent-name, phone, email, or appointment-date questions are custom fields you add (textarea, select, or input); they are not documented defaults. A measurement answer is a stored number or note, not a fitting record. An areas-to-improve note is a stored textarea, not a verified ranking. A school schedule is a stored calendar note, not proof of attendance. A travel calendar is a stored itinerary field, not proof anyone traveled. A booked slot is not proof anyone competed. Cancelling or missing the slot later does not erase the measurement answers, travel calendar, or areas-to-improve note already stored next to a child name, and does not unsend a confirmation email already delivered. How long that pairing sits after a booking that never became a coaching season is not a documented default of the plugin. The appointments list can show who is booked this week next to configured custom fields. 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. | Pageant-coach bookings, custom application fields, and automatic confirmation emails 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. Height, weight, measurements, age-division, school-schedule, competition-travel-calendar, areas-to-improve, child-name, parent-name, phone, or email questions are fields you add; they are not documented defaults. Optional headshot or full-body-photo uploads are files you accept; those file types are not documented defaults. A photo upload is a stored file, not proof of a competition. A measurement answer is a stored number or note, not a fitting record. An areas-to-improve note is a stored textarea, not a verified ranking. A school schedule is a stored calendar note, not proof of attendance. A travel calendar is a stored itinerary field, not proof anyone traveled. A pageant-coach form is not proof anyone competed. Completing the form can store a child name next to photos, measurements, an age division, a school schedule, a travel calendar, and an areas-to-improve note — typed by a parent into one entries table for a data subject who never opened the form. 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 pairing sits after a coaching season that never started is not a documented default of the plugin. | Pageant application entries stored in WordPress; optional photo uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| Iptanus File Upload Documented frontend upload form (formerly WordPress File Upload). By default files land inside the wp-content directory of the site; the upload path is configurable. Uploaded files can be added to Media or attached to the current page. FTP and SFTP destinations are documented. The Professional version documents uploads to Google Drive, Dropbox, OneDrive, or Amazon S3. A headshot or full-body photo is a file you accept; that file type is not a documented default. An uploaded photo is a stored file, not proof of a competition. Deleting a form entry later does not by itself prove the file was removed from the uploads path or from a cloud destination you enabled. The listing claims GDPR compliance without a tested EXIF-strip or retention length here. Review upload directory, Media attachment, and cloud destinations. Browser hosts for the visitor upload path were not verified for this snapshot. | Headshot and full-body-photo uploads stored under the site wp-content path | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Headshot, full-body-photo, height, weight, measurements, age-division, school-schedule, competition-travel-calendar, areas-to-improve, child-name, parent-name, phone, email, or appointment-date fields often depend on the fields you configure. A photo upload is a stored file, not proof of a competition. A measurement answer is a stored number or note, not a fitting record. An areas-to-improve note is a stored textarea, not a verified ranking. A school schedule is a stored calendar note, not proof of attendance. A travel calendar is a stored itinerary field, not proof anyone traveled. A pageant-coach application is not proof anyone competed. A page request is not proof anyone applied. The page URL can say pageant coach even when no form is submitted. The photos, the measurements, and the travel calendar can sit after a coaching season that never started. This page is about the application that files a child's photos, measurements, and travel calendar in one row, not a dance-studio costume intake, not a school-carpool schedule, not a water-park waiver, and not an orthodontist child image. Ask your web vendor who can open entries and uploads, whether photo files remain reachable by direct URL, and how long records and backups are kept. A "private coaching dossier" 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 or child-privacy law, child-safeguarding standards, pageant outcomes, or coaching quality. Review stored records, uploaded photos, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 19, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress forms privacy
- WordPress file upload plugin privacy
- WordPress booking plugin privacy
- All privacy guides
/wp-pageant-coach-plugin-privacy