Horse boarding plugin privacy
The stall contract that appraises the animal and logs how often you really visit
A boarding intake can look like a stall assignment and a monthly fee. It is also an insurance appraisal with a barn address attached: the horse's value, its vet and medication history, and the trailer it arrives in — all in one row. The quieter record is the visit log. The barn often knows a rider's schedule better than neighbors know a car, and a gap in visits can be the first dated evidence of injury, divorce, or money trouble — because a boarded horse is often the first luxury a struggling family stops visiting. Horse-value, vet-history, medication-list, trailer-note, visit-log, and boarding-cadence fields are configured, not documented defaults. Optional Coggins PDFs or horse photos go in the site uploads folder. A stall booking is not proof a horse arrived. A visit gap is a calendar pattern, not proof of distress. A page request is not proof anyone boarded a horse. The page URL can say horse boarding even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on booking and account pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, an animal-neglect claim, a divorce claim, a financial-distress 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 stall bookings, appraisal intakes, and page tags go
Stall bookings and boarding forms handled on your WordPress site
Check which horse-value, vet-history, medication-list, trailer-note, visit-log, or boarding-cadence fields you enable, who can open form entries and bookings, where uploaded Coggins files live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a request that never became a boarding. Notification emails can also copy the same valuation and vet history off-site. One table can name the horse, the insured value, the visit cadence, and the gap next to a boarder name, even when the stall stays empty. Ask your web vendor not to collect a horse valuation next to a visit log on the first public form, not to store medication lists next to addresses in one open submissions list, and to purge unused stall bookings after the date passes. A privacy-policy page does not by itself limit who can export a customer list. A stored booking is not proof a horse arrived.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the horse-boarding booking or account page. That page request can reach a vendor host before anyone submits. The page URL can say horse boarding even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and account pages if you do not want that page request. A browser scan cannot inspect stored valuations, vet histories, or visit gaps. A "boarded horse" badge is not a verified storage path.
Horse-boarding booking, appraisal-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 barn-management or equine-insurance software without a WordPress.org listing is 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). The listing documents automatic email notifications: customers get instant booking confirmations; staff get notified; templates can include booking information and custom fields; customers can confirm or cancel via a link in the email. WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A stall boarding is a booking you create; a service name such as full care, pasture board, or training board is a label you configure. Neither is a documented default. Horse-value, vet-history, medication-list, trailer-note, visit-log, or boarding-cadence questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked stall is not proof a horse arrived, and a visit gap is not proof of distress. Cancelling or missing the slot later does not erase the valuation, vet history, or visit cadence already stored next to a name, and does not unsend a confirmation email already delivered. How long that row sits after a booking that never became a boarding is not a documented default of the plugin. 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. | Stall bookings, custom intake fields, and automatic confirmation emails 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. Horse-value, vet-history, medication-list, trailer-note, visit-log, or boarding-cadence questions are fields you add; they are not documented defaults. A Coggins PDF or horse photo is a file you accept; that file type is not a documented default. A boarding request is not proof a horse arrived. A valuation answer is a stored number, not a verified appraisal. A visit gap in later bookings is not proof of injury, divorce, or money trouble. Notification emails can copy field values and file links off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. How long an account row sits after a request that never became a boarding is not a documented default of the plugin. | Account and boarding-intake form entries stored in WordPress; file 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 horse-value, vet-history, visit-log, or boarding-cadence field was sent. A page request from this script is not proof anyone boarded a horse. The page URL can say horse boarding even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and account pages. Keep marketing tags off those pages if you do not want that page request. A tagged boarding page can re-confirm stall interest next to a stored horse appraisal; this row does not claim a boarding from that request. | 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. Horse-value, vet-history, medication-list, trailer-note, visit-log, or boarding-cadence fields often depend on the fields you configure. A stall booking is not proof a horse arrived. A visit gap is a calendar pattern, not proof of injury, divorce, or money trouble. A marketing-tag page request is not proof anyone boarded a horse. The page URL can say horse boarding even when no form is submitted. The appraisal and the visit log can sit after the stall stays empty. This page is about a stall contract that appraises the animal and logs visits, not a horseback-riding rider-weight booking, not a dog-boarding empty-house reservation, not a marina slip ledger, and not a meal-train stage signup. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or account page, and how long records and backups are kept. A "boarded horse" 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 animal neglect, divorce proceedings, or financial distress. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and account 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-horse-boarding-plugin-privacy