Surf school plugin privacy
The signup that records whether your child can actually swim
A surf school signup asks a parent to put in writing the thing they'd never admit at the beach: whether their child can actually swim in open water, and how far. That honesty — swim-ability level, age, medical flags, the cove and time where a minor will be dropped off — sits in a form plugin on a seasonal website that gets rebuilt every spring by whoever is cheapest. The lesson lasts an hour; the row that says "weak swimmer, meets at the north jetty, Saturdays 9am" has no expiry at all. Those fields are configured, not documented defaults. A lesson booking is a calendar row, not proof anyone paddled out. A swim-ability answer is what a parent typed, not a swim test. A medical flag is a parent's disclosure, not a chart. A cove and drop-off time is a logistics note, not a custody record. A page request is not proof anyone stood on a beach. The page URL can say surf school even when no form is submitted. Ask what happens to the swim-ability answer, the age, the medical flag, and the drop-off note after the lesson ends — the signup that records whether your child can actually swim outlives the hour in the water. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the signup page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a drowning-prevention or open-water-safety claim, a lifeguard or instructor-certification claim, a COPPA or child-privacy-law claim, a medical-fitness 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 swim-ability answers, lesson bookings, and page tags go
Intakes and bookings on your WordPress site
Check which swim-ability, child-age, medical-flag, or cove drop-off 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 the lesson ends — when the signup that records whether your child can actually swim still holds that row. Notification emails can also copy those fields off-site. One table can list a legal name next to a weak-swimmer answer, an age, a medical flag, and a north-jetty Saturday drop-off note. Ask your web vendor not to keep open-water honesty next to minor ages and beach logistics in one open submissions list longer than operations need, and to purge those fields when a season closes — especially on a site that gets rebuilt every spring. A privacy-policy page does not by itself limit who can open a submissions list. A stored lesson booking is not proof anyone paddled out. A swim-ability answer is not a swim test.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the surf-school signup page. That page request can reach a vendor host before anyone submits. The page URL can say surf school even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off signup pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "surf school privacy" badge is not a verified storage path.
Swim-ability signup, booking, and marketing-tag setups
Three plugins reviewed from public documentation. Specialty surf-school / camp 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.
| 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. A Saturday beginner lesson or a north-jetty group block is a booking you create; a service name such as surf school or open-water intro is a label you configure. Neither is a documented default. Swim-ability, child-age, medical-flag, or cove drop-off questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof anyone paddled out — and a CSV export of "Jordan Lee, swim: weak open water, age: 11, medical: asthma, drop-off: north jetty Sat 9am" next to a contact name is still a calendar that holds a child's open-water honesty next to a beach logistics note. 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. | Lesson and group 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. Swim-ability, child-age, medical-flag, or cove drop-off fields are fields you add; they are not documented defaults. Completing the form can store an open-water swim-ability answer next to a child age, a medical flag, a north-jetty Saturday drop-off note, a contact name, and optional waiver PDF uploads — typed once so the beach desk does not have to re-key the booking, into the same tables as a surf-school label on a seasonal site that gets rebuilt every spring. A swim-ability answer is what a parent typed, not a swim test. A lesson booking is a calendar row, not proof anyone paddled out — and a staff login can open "Jordan Lee, swim: weak open water, age: 11, medical: asthma, drop-off: north jetty Sat 9am" 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. | Swim-ability and drop-off answers stored in WordPress; optional waiver 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 swim-ability, age, medical-flag, or drop-off field was sent. A page request from this script is not proof anyone stood on a beach. The page URL can say surf school even when no form is submitted. Consent timing has not been tested. Review which tags you enable on signup 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. Swim-ability, child-age, medical-flag, or cove drop-off fields often depend on the fields you configure. A lesson booking is a calendar row, not proof anyone paddled out. A swim-ability answer is what a parent typed, not a swim test. A medical flag is a parent's disclosure, not a chart. A cove and drop-off time is a logistics note, not a custody record. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone stood on a beach. The page URL can say surf school even when no form is submitted. The signup that records whether your child can actually swim — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that open-water honesty and beach drop-off stack on a seasonal site, not a pool swim-school medical enrollment, a scuba dive-medical questionnaire, a ski-rental binding form, or a summer-camp emergency card. Ask your web vendor who can open entries, whether a marketing tag loads on the signup page, and how long records and backups are kept. A "surf school privacy" or "child water-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 law, open-water safety standards, lifeguard or instructor certification, COPPA or child-privacy law, or medical fitness. Review stored records, bookings, connected services, exports, notification emails, marketing tags on signup pages, and backups.
Documentation snapshot: Oct 15, 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-surf-school-plugin-privacy