Ski rental plugin privacy

The binding form that stores the whole family's weight, by name

DIN binding settings are calculated from height, weight, age, and ability level — so a ski rental's online reservation form collects, by name, the one number most adults won't say out loud, for every member of the family, kids included. It sits in a WordPress booking plugin year after year as a dated series ("what Mom weighed each December"), kept because the shop's lawyer wants proof the release setting was right if a knee blows out. A liability record that doubles as a longitudinal weight log nobody consented to. Those fields are configured, not documented defaults. A rental booking is a calendar row, not proof anyone skied. A weight answer is what a renter typed, not a clinic chart. An intake upload is a client document in a site uploads folder. A page request is not proof anyone left the lodge. The page URL can say ski rental even when no form is submitted. Ask what happens to the named weight rows after a ski week ends — the binding form that stores the whole family's weight, by name, outlives the lift ticket. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the reservation page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a DIN/ISO-binding-standards claim, a ski-liability-law claim, a medical-privacy-law claim, a rental-shop-compliance 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 DIN-intake reservations, rental bookings, and page tags go

Intakes and bookings on your WordPress site

Check which height, weight, age, ability-level, DIN, or waiver-upload fields you enable, who can open form entries and ski-rental bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a ski week ends — when the binding form stores the whole family's weight, by name. Notification emails can also copy those fields off-site. One table can list every named weight a family typed next to a Saturday ski-week slot and a boot size. Ask your web vendor not to keep waiver uploads next to family weight rows in one open submissions list longer than operations need, and to purge booking rows when a rental ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored rental booking is not proof anyone skied. A weight answer is not a clinic chart.

Page tags handled by a vendor

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

DIN-intake reservation, rental-booking, 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 ski-rental SaaS tools without a WordPress.org listing are outside this sample.

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 ski-week slot or a weekend demo-ski package is a booking you create; a service name such as ski rental or DIN binding intake is a label you configure. Neither is a documented default. Height, weight, age, ability-level, DIN, or waiver-upload 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 skied — and a CSV export of a Saturday 9am ski-week slot next to Mom's weight and a waiver PDF filename is still a calendar that holds a family weight log beside a contact name. 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.

Ski-rental 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. Height, weight, age, ability-level, DIN, or waiver-upload fields are fields you add; they are not documented defaults. Completing the form can store a named weight next to a rental booking, a contact name, kids' rows, and optional waiver uploads — typed once so the shop can set bindings, into the same tables as a boot size. A weight answer is what a renter typed, not a clinic chart. A rental booking is a calendar row, not proof anyone skied — and a staff login can open "Mom, 165 lb, age 42, intermediate, waiver.pdf, Saturday ski week" 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.

Height, weight, age, and ability answers stored in WordPress; optional waiver 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 height, weight, age, ability-level, DIN, or waiver-upload field was sent. A page request from this script is not proof anyone left the lodge. The page URL can say ski rental even when no form is submitted. Consent timing has not been tested. Review which tags you enable on reservation and DIN-intake 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. Height, weight, age, ability-level, DIN, or waiver-upload fields often depend on the fields you configure. A rental booking is a calendar row, not proof anyone skied. A weight answer is what a renter typed, not a clinic chart. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone left the lodge. The page URL can say ski rental even when no form is submitted. The binding form that stores the whole family's weight, by name — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that equipment-liability weight log, not a kids' swim-school medical question, a race-registration waiver, or a personal-trainer fitness measurement. Ask your web vendor who can open entries, whether a marketing tag loads on the reservation page, and how long records and backups are kept. A "ski privacy" or "DIN compliant" 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 DIN/ISO binding standards, ski-liability law, or medical privacy law. Review stored records, bookings, connected services, exports, notification emails, marketing tags on reservation and DIN-intake 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-ski-rental-plugin-privacy