Septic service plugin privacy
The service history that travels with the house
A septic pump-out record is a map of your property that you don't control: tank location sketch, system age, inspection results — filed with the county health department because regulation requires it, and handed to the buyer at sale because disclosure law does. It's the rare service history that outlives the customer: the record is about the house, travels with the house, and the portal keeps the owner's name, well-water proximity, and failed-inspection history long after they've moved. Those fields are configured, not documented defaults. A pump-out booking is a calendar row, not proof a tank was pumped or that a county filing happened. An inspection or sketch answer is a form answer or uploaded file, not a verified health-department record. A page request is not proof anyone booked a pump-out. The page URL can say septic service even when no form is submitted. Ask what happens to the address, the tank sketch, the inspection result, and the county-bound ledger after a move or sale — the stack that mapped your property outlives the owner. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking or report page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a county-filing-legality claim, a disclosure-law-compliance claim, a well-water-safety claim, a septic-code-compliance 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 pump-out bookings, inspection ledgers, and page tags go
Bookings and ledgers on your WordPress site
Check which address, tank-sketch, system-age, well-proximity, inspection-result, county-filing, buyer-disclosure, or intake-upload fields you enable, who can open form entries and pump-out bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a move or sale — when the address-plus-sketch-plus-inspection row still holds a property map next to a failed-inspection note. Notification emails can also copy those fields off-site. One table can list every "14 Maple Rd · tank sketch: NE corner · age: 1998 · well 80ft · insp: FAILED baffle · filed → county health · disclosure → buyer" stack next to a customer name. Ask your web vendor not to keep tank sketches and inspection ledgers next to home addresses and owner names in one open submissions list longer than operations need, and to purge those fields when a property changes hands. A privacy-policy page does not by itself limit who can open a submissions list. A stored pump-out booking is not proof a tank was pumped or that a county filing happened. An inspection or sketch answer is not a verified health-department record.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the booking or report page. That page request can reach a vendor host before anyone submits. The page URL can say septic service even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and report pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "septic service privacy" badge is not a verified storage path.
Septic-service booking, inspection-ledger, 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 septic-service SaaS tools without a WordPress.org listing are 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A three-year pump-out slot or a pre-sale inspection window is a booking you create; a service name such as pump-out or septic inspection is a label you configure. Neither is a documented default. Address, tank-sketch, system-age, well-proximity, inspection-result, county-filing, or buyer-disclosure questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof a tank was pumped or that a county filing happened — and a CSV export of "14 Maple Rd · tank sketch: NE corner · age: 1998 · well 80ft · insp: FAILED baffle · filed → county health · disclosure → buyer" next to a customer name is still a calendar that pairs a property map with a failed-inspection note that outlives the owner. 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. | Septic-service bookings 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. Address, tank-sketch, system-age, well-proximity, inspection-result, county-filing, or buyer-disclosure fields are fields you add; they are not documented defaults. Completing the form can store an address-plus-sketch-plus-inspection stack ("14 Maple Rd · tank sketch: NE corner · age: 1998 · well 80ft · insp: FAILED baffle · filed → county health · disclosure → buyer") — typed once so a county or a buyer can read the ledger, into the same tables as a "septic service" label. An inspection or sketch answer is a form answer or uploaded file, not a verified health-department record. A pump-out booking is a calendar row, not proof a tank was pumped — and a staff login can open "Jordan, 14 Maple Rd, tank-ne.jpg, age 1998, well 80ft, FAILED baffle, filed → county" 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. | Address, tank-sketch, and inspection answers stored in WordPress; optional sketches 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 an address, tank-sketch, or inspection-result field was sent. A page request from this script is not proof anyone booked a pump-out. The page URL can say septic service even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and report 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. Address, tank-sketch, system-age, well-proximity, inspection-result, county-filing, or buyer-disclosure fields often depend on the fields you configure. A pump-out booking is a calendar row, not proof a tank was pumped or that a county filing happened. An inspection or sketch answer is a form answer or uploaded file, not a verified health-department record. A marketing-tag page request is not proof anyone booked a pump-out. The page URL can say septic service even when no form is submitted. The address-plus-sketch-plus-inspection row that mapped your property for a county and a buyer — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that pump-out ledger stack, not a mold-testing disclosable fact without regulator filing, a one-time home-inspection report, or a pest-control vendor-private condition note. Ask your web vendor who can open entries, whether a marketing tag loads on the booking or report page, and how long records and backups are kept. A "septic service privacy" or "county-ready ledger" 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 county filing legality, disclosure-law compliance, well-water safety, or septic-code compliance. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking and report 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-septic-service-plugin-privacy