Ice rink plugin privacy

The lesson roster that schedules where your child stands at 6am Saturday

Learn-to-skate enrollment publishes the most precise child-location schedule a form plugin can hold: which rink, which entrance, 6:00am every Saturday, for a named, aged child whose skill level ("Snowplow Sam 2") tells a stranger exactly which patch of ice to find them on. Season after season the roster accretes — level progressions, coach assignments, competition travel — a longitudinal record of one child's weekly whereabouts kept by a municipal rink running last year's WordPress. Those fields are configured, not documented defaults. A lesson booking is a calendar row, not proof a child skates anywhere. A skill-level answer is a parent or coach label, not a placement exam. A page request is not proof anyone enrolled. The page URL can say ice rink even when no form is submitted. Ask what happens to the rink, entrance, Saturday slot, child name, and skill level after the season ends — the roster that mapped which patch of ice holds which child 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 skating-safety claim, a coaching-certification claim, a rink-operations claim, a COPPA or child-privacy-law 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, bookings, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.

Where learn-to-skate roster answers, lesson bookings, and page tags go

Intakes and bookings on your WordPress site

Check which rink/entrance, Saturday-slot, child-name-and-age, skill-level, coach, competition-travel, or emergency-contact fields you enable, who can open form entries and ice-rink lesson bookings, which inboxes receive copies, and how long records, emails, and backups are kept after the season ends — when the roster that mapped which patch of ice holds which child still holds that row. Notification emails can also copy those fields off-site. One table can list every Saturday 6:00am slot next to a named aged child, a Snowplow Sam 2 skill level, a coach assignment, and a competition-travel note. Ask your web vendor not to keep child-location schedules next to names and skill levels in one open submissions list longer than operations need, and to purge those fields when a season closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored ice-rink lesson booking is not proof a child skates anywhere. A skill-level answer is not a placement exam.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the ice-rink enrollment page. That page request can reach a vendor host before anyone submits. The page URL can say ice rink even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off enrollment pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. An "ice rink privacy" badge is not a verified storage path.

Ice-rink lesson-booking, learn-to-skate enrollment, and marketing-tag setups

Three plugins reviewed from public documentation. Specialty rink / learn-to-skate 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.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
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 6:00am learn-to-skate slot or a rink-entrance access note is a booking you create; a service name such as ice rink or learn-to-skate is a label you configure. Neither is a documented default. Rink/entrance, Saturday-slot, child-name-and-age, skill-level, coach, competition-travel, or emergency-contact questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof a child skates anywhere — and a CSV export of "North entrance / Sat 6:00am — Snowplow Sam 2 + named aged child" next to a coach assignment is still a calendar that holds which patch of ice holds which child under one ice-rink reservation. 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.

Ice-rink lesson bookings stored on your WordPress siteBrowser 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. Rink/entrance, Saturday-slot, child-name-and-age, skill-level, coach, competition-travel, or emergency-contact fields are fields you add; they are not documented defaults. Completing the form can store which rink and entrance next to a 6:00am Saturday slot, a named aged child, a Snowplow Sam 2 skill level, a coach assignment, a competition-travel note, and a progress-report upload — typed once so the rink does not have to re-ask which patch of ice holds which child, into the same tables as an ice-rink label. A skill-level answer is a parent or coach label, not a placement exam. A lesson booking is a calendar row, not proof a child skates anywhere — and a staff login can open "North entrance / Sat 6:00am — Snowplow Sam 2 + named aged child" next to every other Saturday roster row season after season. 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.

Learn-to-skate roster answers stored in WordPress; optional progress-report uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
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 rink/entrance, Saturday-slot, child-name-and-age, skill-level, coach, or competition-travel field was sent. A page request from this script is not proof anyone enrolled. The page URL can say ice rink even when no form is submitted. Consent timing has not been tested. Review which tags you enable on ice-rink enrollment pages.

Marketing tags handled through Meta, Google, or other configured platformsconnect.facebook.netNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Rink/entrance, Saturday-slot, child-name-and-age, skill-level, coach, competition-travel, or emergency-contact fields often depend on the fields you configure. A lesson booking is a calendar row, not proof a child skates anywhere. A skill-level answer is a parent or coach label, not a placement exam. A marketing-tag page request is not proof anyone enrolled. The page URL can say ice rink even when no form is submitted. The roster that mapped which patch of ice holds which child — that is a storage path next to names and skill levels, not a feature these plugins claim. This page is about that learn-to-skate child-location schedule, not a swim-school enrollment, a dance-studio measurement chart, a water-park season-pass diary, or a youth-sports-league season roster. 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. An "ice rink privacy" or "rink-safe" 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 skating safety, coaching certification, rink operations, COPPA, or child-privacy law. Review stored records, bookings, connected services, exports, notification emails, marketing tags on enrollment pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-ice-rink-plugin-privacy