Pool service plugin privacy

The route sheet that stores your gate code, your dog's name, and the day nobody's home

A weekly pool route turns a customer record into a standing access credential: the gate code, the dog's name, the side-yard latch trick, and exactly which weekday a stranger is authorized to walk into your backyard unchallenged — all so the tech doesn't have to knock. Skip a service note ("owners away until the 20th, service as usual") and the plugin now holds a signed statement of when the house stands empty, renewed every seven days. It's the only service record whose core fields are instructions for entering a home. Those fields are configured, not documented defaults. A route booking is a calendar row, not proof anyone entered a backyard. A gate-code answer is what a customer typed, not a key vault. An intake upload is a client document in a site uploads folder. A page request is not proof anyone serviced a pool. The page URL can say pool service even when no form is submitted. Ask what happens to the gate code, dog name, latch note, service weekday, and owners-away note after a weekly route ends — the route sheet that stores your gate code, your dog's name, and the day nobody's home outlives the visit. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the route-intake page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a premises-access-law claim, an empty-home-law claim, a home-security-law claim, a service-route-law 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 route-intake answers, weekly bookings, and page tags go

Intakes and bookings on your WordPress site

Check which gate-code, dog-name, side-yard latch-trick, service-weekday, or owners-away fields you enable, who can open form entries and weekly route bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a weekly route ends — when the route sheet stores your gate code, your dog's name, and the day nobody's home. Notification emails can also copy those fields off-site. One table can list every gate code a customer typed next to a dog name, a side-latch note, a Tuesday slot, and an "owners away until the 20th" service note. Ask your web vendor not to keep gate codes next to dog names and empty-home notes in one open submissions list longer than operations need, and to purge access fields when a route stops. A privacy-policy page does not by itself limit who can open a submissions list. A stored route booking is not proof anyone entered a backyard. A gate-code answer is not a key vault.

Page tags handled by a vendor

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

Route-intake, weekly-booking, and marketing-tag setups

Three plugins reviewed from public documentation. Specialty pool-route / field-service 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 Tuesday chemical-balance slot or a weekly route package is a booking you create; a service name such as pool service or pool cleaning is a label you configure. Neither is a documented default. Gate-code, dog-name, side-yard latch-trick, service-weekday, or owners-away 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 entered a backyard — and a CSV export of "gate 4821, dog Buddy, side latch, owners away until the 20th" next to a contact name is still a calendar that holds standing access instructions beside a customer row. 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.

Weekly route 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. Gate-code, dog-name, side-yard latch-trick, service-weekday, or owners-away fields are fields you add; they are not documented defaults. Completing the form can store a gate code next to a dog name, a latch note, a Tuesday route, a contact name, optional access-instruction or waiver uploads, and an "owners away until the 20th" service note — typed once so the tech does not have to knock, into the same tables as a chemical-balance package name. A gate-code answer is what a customer typed, not a key vault. A route booking is a calendar row, not proof anyone entered a backyard — and a staff login can open "gate 4821, Buddy, side latch, Tue, away until the 20th" 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.

Gate-code, dog-name, and access-note answers stored in WordPress; optional access-instruction or 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 gate-code, dog-name, latch-trick, service-weekday, or owners-away field was sent. A page request from this script is not proof anyone serviced a pool. The page URL can say pool service even when no form is submitted. Consent timing has not been tested. Review which tags you enable on route-intake and weekly-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. Gate-code, dog-name, latch-trick, service-weekday, or owners-away fields often depend on the fields you configure. A route booking is a calendar row, not proof anyone entered a backyard. A gate-code answer is what a customer typed, not a key vault. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone serviced a pool. The page URL can say pool service even when no form is submitted. The route sheet that stores your gate code, your dog's name, and the day nobody's home — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that standing-access and empty-home stack, not a self-storage gate code on different premises, a pet-sitting empty-home schedule without a standing code, a house-cleaning indoor access log, an alarm-company security infrastructure file, or a swim-school lesson enrollment. Ask your web vendor who can open entries, whether a marketing tag loads on the route-intake page, and how long records and backups are kept. A "pool service privacy" or "field-service 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 premises-access law, empty-home law, home-security law, or service-route law. Review stored records, bookings, connected services, exports, notification emails, marketing tags on route-intake and weekly-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-pool-service-plugin-privacy