Horseback riding plugin privacy

The booking form that must ask your exact weight — and keeps it forever

The one booking form in recreation that must ask your exact weight — not a range, the number — because the horse assignment depends on it. Most people won't say that number out loud to their own family; the stable's form plugin stores it next to their name, their kid's age and skill claims, and the emergency contact for a sport with real injury rates. A weigh-in is clinical data everywhere else on this site; here it's a prerequisite for a trail ride, kept indefinitely by default. Those fields are configured, not documented defaults. A trail or lesson booking is a calendar row, not proof anyone rode. An exact-weight answer is what a guest typed, not a clinical weigh-in. A skill claim is a self-report, not a riding-school credential. An intake upload is a client document in a site uploads folder. A page request is not proof anyone mounted. The page URL can say horseback riding even when no form is submitted. Ask what happens to the exact weight, rider age, skill claim, and emergency contact after the ride ends — the booking form that must ask your exact weight outlives the trail. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a HIPAA claim, a veterinary or equine liability-law claim, a weight-limit-standard claim, a trail-ride-safety claim, a clinical weigh-in 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 exact-weight answers, trail bookings, and page tags go

Intakes and bookings on your WordPress site

Check which exact-weight, rider-age, skill-claim, or emergency-contact fields you enable, who can open form entries and trail bookings, which inboxes receive copies, and how long records, emails, and backups are kept after the ride ends — when the booking form that must ask your exact weight still holds that row. Notification emails can also copy those fields off-site. One table can list a legal name next to an exact weight in pounds, a kid's age, a beginner skill claim, and an emergency contact. Ask your web vendor not to keep weigh-in numbers next to minor ages and emergency contacts in one open submissions list longer than operations need, and to purge those fields when a booking season closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored trail booking is not proof anyone rode. An exact-weight answer is not a clinical weigh-in.

Page tags handled by a vendor

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

Weight-intake, booking, and marketing-tag setups

Three plugins reviewed from public documentation. Specialty stable / equine 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 trail slot or a lesson block is a booking you create; a service name such as horseback riding or beginner trail is a label you configure. Neither is a documented default. Exact-weight, rider-age, skill-claim, 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 anyone rode — and a CSV export of "Sam Rivera, weight: 185 lb, age: 12, skill: beginner, ICE: Morgan Rivera" next to a contact name is still a calendar that holds a weigh-in number next to a minor's age for horse assignment. 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.

Trail and 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. Exact-weight, rider-age, skill-claim, or emergency-contact fields are fields you add; they are not documented defaults. Completing the form can store an exact weight in pounds next to a kid's age, a beginner skill claim, an emergency contact for a sport with real injury rates, a contact name, and optional waiver or liability uploads — typed once so the barn desk does not have to re-key the booking, into the same tables as a horseback-riding label. An exact-weight answer is what a guest typed, not a clinical weigh-in. A trail booking is a calendar row, not proof anyone rode — and a staff login can open "Sam Rivera, weight: 185 lb, age: 12, skill: beginner, ICE: Morgan Rivera, waiver PDF" 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.

Exact-weight and emergency-contact 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 an exact-weight, rider-age, skill-claim, or emergency-contact field was sent. A page request from this script is not proof anyone mounted. The page URL can say horseback riding even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking 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. Exact-weight, rider-age, skill-claim, or emergency-contact fields often depend on the fields you configure. A trail or lesson booking is a calendar row, not proof anyone rode. An exact-weight answer is what a guest typed, not a clinical weigh-in. A skill claim is a self-report, not a riding-school credential. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone mounted. The page URL can say horseback riding even when no form is submitted. The booking form that must ask your exact weight — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that stable weigh-in and horse-assignment stack, not a weight-loss clinical program, a dance-studio child measurement chart, a boat-rental float-plan waiver, or a summer-camp minor medical card. Ask your web vendor who can open entries, whether a marketing tag loads on the booking page, and how long records and backups are kept. A "horseback riding privacy" or "barn-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 HIPAA, veterinary or equine liability law, weight-limit standards, trail-ride safety rules, or clinical weigh-in practice. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking 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-horseback-riding-plugin-privacy