Dog boarding plugin privacy
The reservation that documents exactly when your house stands empty
A boarding reservation is the cleanest written proof of an empty house on the internet: drop-off the 12th, pick-up the 26th, owner's cell "while traveling," and an emergency contact chosen precisely because they are NOT going with you — the form quietly maps who's away and who's left behind. Vet records and medication schedules ride along, so a pet's seizure meds and your two-week vacancy share one row in a kennel's WordPress install. Burglars case houses for less reliable information than this form requires. Those fields are configured, not documented defaults. A boarding reservation is a calendar row, not proof anyone boarded a dog or that a house was empty. A vet-record upload is a client document in a site uploads folder, not a veterinary diagnosis. A page request is not proof anyone booked a stay. The page URL can say dog boarding even when no form is submitted. Ask what happens to the travel window, traveling-owner cell, emergency contact, and vet records after the stay ends — the reservation that mapped when the house stands empty outlives the boarding. 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 veterinary-medicine claim, an animal-welfare-licensing claim, a travel-insurance claim, a home-security 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 travel-window answers, boarding reservations, and page tags go
Intakes and bookings on your WordPress site
Check which drop-off/pick-up, traveling-owner-cell, emergency-contact, vet-record, or medication-schedule fields you enable, who can open form entries and dog-boarding reservations, which inboxes receive copies, and how long records, emails, and backups are kept after the stay ends — when the reservation that mapped when the house stands empty still holds that row. Notification emails can also copy those fields off-site. One table can list every holiday vacancy next to a traveling-owner cell, a homebound emergency contact, a street address, and a medication schedule. Ask your web vendor not to keep travel windows next to addresses and emergency contacts in one open submissions list longer than operations need, and to purge those fields when a boarding stay closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored dog-boarding reservation is not proof anyone boarded a dog or that a house was empty. A vet-record upload is not a veterinary diagnosis.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the dog-boarding reservation page. That page request can reach a vendor host before anyone submits. The page URL can say dog boarding even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off reservation pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "dog boarding privacy" badge is not a verified storage path.
Dog-boarding reservation, intake-upload, and marketing-tag setups
Three plugins reviewed from public documentation. Specialty kennel / pet-boarding 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 two-week boarding window or a "call while traveling" access note is a booking you create; a service name such as dog boarding or kennel stay is a label you configure. Neither is a documented default. Drop-off/pick-up, traveling-owner-cell, emergency-contact, vet-record, or medication-schedule 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 boarded a dog or that a house was empty — and a CSV export of "drop-off Dec 12 / pick-up Dec 26 — cell while traveling + neighbor emergency contact" next to a home address is still a calendar that holds when the house stands empty next to who is left behind under one dog-boarding 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. | Dog-boarding reservations 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. Drop-off/pick-up, traveling-owner-cell, emergency-contact, vet-record, or medication-schedule fields are fields you add; they are not documented defaults. Completing the form can store drop-off and pick-up dates next to a traveling-owner cell, an emergency contact who is not going with you, a street address, a vet-record PDF, and a medication schedule — typed once so the kennel does not have to re-ask when you leave and who can be reached, into the same tables as a dog-boarding label. A vet-record upload is a client document in a site uploads folder, not a veterinary diagnosis. A boarding reservation is a calendar row, not proof anyone boarded a dog or that a house was empty — and a staff login can open "drop-off Dec 12 / pick-up Dec 26 — cell while traveling + neighbor emergency contact" next to every other vacant house on the holiday roster long after the stay ends. 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. | Travel-window and emergency-contact answers stored in WordPress; optional vet-record 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 drop-off/pick-up, traveling-owner-cell, emergency-contact, vet-record, or medication-schedule field was sent. A page request from this script is not proof anyone booked a stay. The page URL can say dog boarding even when no form is submitted. Consent timing has not been tested. Review which tags you enable on dog-boarding reservation 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. Drop-off/pick-up, traveling-owner-cell, emergency-contact, vet-record, or medication-schedule fields often depend on the fields you configure. A boarding reservation is a calendar row, not proof anyone boarded a dog or that a house was empty. A vet-record upload is a client document in a site uploads folder, not a veterinary diagnosis. A marketing-tag page request is not proof anyone booked a stay. The page URL can say dog boarding even when no form is submitted. The reservation that mapped when the house stands empty — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that travel-window-indexed dog-boarding reservation, not an in-home pet-sitting intake, a bite-history behaviorist form, a travel-agency custody record, or a pool-service standing-access calendar. 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 "dog boarding privacy" or "kennel-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 veterinary medicine, animal-welfare licensing, travel insurance, or home-security advice. Review stored records, bookings, connected services, exports, notification emails, marketing tags on reservation 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-dog-boarding-plugin-privacy