Pet sitting plugin privacy

The booking calendar that lists every night nobody is home

A pet-sitting WordPress stack is not only a database of pets — it is a calendar of vacancies. Every confirmed trip dates the nights nobody is home, and the same row often holds the key location, lockbox and alarm codes, gate codes, access notes, and pet meds that make that schedule useful. No breach required: the booking is the product and the leak. Last year's trip calendar is still a pattern-of-life record. A marketing tag on the same booking page can send a page request to a vendor host before anyone submits — and that page request alone can treat pet-sitting booking intent as an audience segment from the URL. A page request is not proof anyone booked. A booking is not proof a house was empty. An access note is a field you configure, not a default. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where uploaded files land, which sitters sync the calendar, which tags load on the booking page, and how long past bookings, files, and backups are kept.

Documentation review only. This is not legal advice, a burglary-risk claim, an insurance claim, a home-security or crime-statistics assessment, a GDPR or other compliance assessment, or a judgment about sitters.

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, sitter calendar syncs, email inboxes, staff permissions, vendor accounts, or backups.

Where trip bookings, access notes, and page tags go

Entries, bookings, and the trip calendar on your WordPress site

Check which key-location, alarm-code, gate-code, access-note, or pet-medical fields you enable, who can open form entries and trip bookings, where uploaded key photos or vet records live in the uploads folder, which inboxes receive copies, which sitters sync the calendar that lists every night nobody is home, and how long past bookings, files, and backups are kept after the visit ends. Notification emails and phone syncs can also copy the same household identity and access notes off-site. Ask your web vendor not to put every access detail next to a trip date on one open calendar when a short booking ID would do — and ask how long last year's trip rows are kept.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the pet-sitting booking page. That page request can reach a vendor host before anyone submits. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and intake pages if you do not want that page request. A browser scan cannot inspect stored form entries, bookings, or who synced the calendar. A "trusted sitter only" badge is not a verified storage or visibility path.

Pet-sitting booking, access-note 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 pet-sitting SaaS platforms 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 vacation pet-sit or recurring morning walk is a booking you create; a service name such as overnight sit or midday walk is a label you configure. Neither is a documented default. Key-location, alarm-code, gate-code, access-note, or pet-medical questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof a house was empty — and a calendar that lists every night nobody is home is the pattern-of-life record that outlasts the trip. Emails can include those custom fields. 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.

Trip dates and recurring walk windows 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. Key-location, alarm-code, gate-code, access-note, pet-medical, emergency-contact, or trip-date questions are fields you add; they are not documented defaults. A key-photo or vet-record upload is a file you accept; it is not a documented default. One client-authored entry can store every access detail next to a household identity — and the same row that holds "under the planter" also holds the dates nobody is home. An access note is a configured field, not a default. A submitted form is not proof a house was empty. 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.

Form entries stored in WordPress; file 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 key location, alarm code, or trip date was sent. A page request from this script on a pet-sitting booking page is not proof anyone booked — and a pre-consent tag on that page can still treat pet-sitting booking intent as an audience segment from the URL alone. The page URL can say pet sitting even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and 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. Key-location notes, alarm codes, gate codes, access instructions, or pet medical details often depend on the fields you configure. A booking is not proof a house was empty. An access note is a configured field, not a default. A marketing-tag page request is not proof anyone booked. Ending the visit later does not erase the trip dates already stored next to a household name — and last year's calendar may still show the pattern. Ask your web vendor who can open entries, who syncs the booking calendar, where uploaded files live, whether a marketing tag loads on the booking page, and how long past bookings and backups are kept. A "trusted sitter only" badge is not a verified storage or visibility path. Consent timing, access controls, and retention have not been tested. This page describes storage and booking-calendar visibility paths only and does not assess burglary risk, insurance coverage, home-security efficacy, or crime statistics. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-pet-sitting-plugin-privacy