Swim school plugin privacy
The enrollment that asks about seizures, because the stakes are the pool
A swim school's enrollment page can look like a lesson booking and a registration form. The same form often asks child name and age, swim level, medical conditions, anything we should know, emergency contact, and photo release — plus progress-report uploads — and stores those answers next to a name for the life of the form table. Those fields are configured, not documented defaults. Most kids' activity forms ask for an emergency contact; a swim school's asks the harder questions — epilepsy, heart conditions, ear tubes — because the water makes every medical answer load-bearing. The quietest field is the anything-we-should-know box, where parents write the near-miss: "pulled from a pool last July, still scared of putting his face in." That is a trauma narrative about a named child, typed by the parent, stored in a WordPress table next to the Tuesday 4pm lesson slot. And the level-progression records chart something tender in the aggregate — which kids still can't swim, by name and age, season after season. A lesson booking is a calendar row, not proof a child can or cannot swim. A medical-conditions answer is the parent's disclosure, not a chart. An anything-we-should-know story is a parent's account, not an incident report. The child described never touched the form. A photo-release checkbox is a stored preference, not a deletion mechanism. An uploaded progress report is a client document in a site uploads folder. A page request is not proof any child swims anywhere. The page URL can say swim school even when no form is submitted. Ask what happens to the medical answer and the progress-report upload after the season — the enrollment asks about seizures because the stakes are the pool, and the row outlives the lesson. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the enrollment page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a drowning-prevention or swim-safety claim, a lifeguard or instructor-certification claim, a COPPA or child-privacy-law 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 files, email inboxes, staff permissions, vendor accounts, or backups.
Where lesson bookings, enrollment intakes, and page tags go
Intakes and bookings on your WordPress site
Check which child-name-and-age, swim-level, medical-conditions, anything-we-should-know, emergency-contact, or photo-release fields you enable, who can open form entries and lesson bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a booking closes — when the enrollment asks about seizures because the stakes are the pool. Notification emails can also copy those fields off-site. One table can list every medical answer a parent typed next to a lesson slot and a swim level. Ask your web vendor not to keep progress reports next to medical answers in one open submissions list longer than operations need, and to purge booking rows when the enrollment is declined or closed. A privacy-policy page does not by itself limit who can open a submissions list. A stored lesson booking is not proof a child can or cannot swim. An uploaded progress report is not a verified skill chart.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the swim enrollment page. That page request can reach a vendor host before anyone submits. The page URL can say swim school even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off enrollment and lesson-booking pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "child swim safety" badge is not a verified storage path.
Lesson booking, swim enrollment intake, 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 swim-school CRM SaaS platforms 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. An evaluation or recurring lesson booking is a booking you create; a service name such as level evaluation, private lesson, or group class is a label you configure. Neither is a documented default. Child-name-and-age, swim-level, medical-conditions, anything-we-should-know, emergency-contact, or photo-release questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof a child can or cannot swim — and a CSV export of lesson slots next to a medical-conditions answer and a named child is still a booking row after someone asked about a class. 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. | Swim evaluation and recurring lesson bookings stored 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. Child-name-and-age, swim-level, medical-conditions, anything-we-should-know, emergency-contact, or photo-release questions are fields you add; they are not documented defaults. Completing the form can store a medical-conditions answer next to an anything-we-should-know story, a swim level, a child name and age, and optional progress-report uploads — typed once by a parent into the same tables as a newsletter signup. A lesson booking is a calendar row, not proof a child can or cannot swim. A medical-conditions answer is the parent's disclosure, not a chart. An anything-we-should-know story is a parent's account, not an incident report. The child described never touched the form. A photo-release checkbox is a stored preference, not a deletion mechanism. An uploaded progress report is a client document in uploads/forminator. A staff login can open the seizure answer next to the Tuesday 4pm lesson slot. 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. | Swim enrollment intake entries stored in WordPress; optional progress-report 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 medical-conditions, anything-we-should-know, swim-level, child-name-and-age, emergency-contact, or photo-release field was sent. A page request from this script is not proof any child swims anywhere. The page URL can say swim school even when no form is submitted. Consent timing has not been tested. Review which tags you enable on enrollment and lesson-booking 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. Child-name-and-age, swim-level, medical-conditions, anything-we-should-know, emergency-contact, or photo-release fields often depend on the fields you configure. A lesson booking is a calendar row, not proof a child can or cannot swim. A medical-conditions answer is the parent's disclosure, not a chart. An anything-we-should-know story is a parent's account, not an incident report. The child described never touched the form. A photo-release checkbox is a stored preference, not a deletion mechanism. An uploaded progress report is a client document in a site uploads folder. A marketing-tag page request is not proof any child swims anywhere. The page URL can say swim school even when no form is submitted. The enrollment asks about seizures because the stakes are the pool — that is a storage path next to child names, not a feature these plugins claim. This page is about that swim enrollment intake, not a summer-camp EpiPen card, a dance-studio measured-body form, a martial-arts stated-reason intake, or a daycare allergy note. Ask your web vendor who can open entries, whether a marketing tag loads on the enrollment page, and how long records and backups are kept. A "child swim 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 drowning prevention, swim-safety outcomes, lifeguard or instructor certification, or COPPA. Review stored records, bookings, connected services, exports, notification emails, marketing tags on enrollment 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-swim-school-plugin-privacy