Well drilling plugin privacy
The site survey that maps the single pipe your household depends on
The site-survey form maps a household's physical dependency — parcel location or GPS pin, acreage, whether the property is off-grid, pump and power details, uploaded plat maps and permits. It records not just where you live but that your water arrives through one private pipe you maintain yourself: a dossier of rural isolation tied to coordinates, sitting in a public WordPress upload form. Those fields are configured, not documented defaults. A well-survey booking is a calendar row, not proof a well was drilled. A GPS, plat, or permit answer is a form answer or uploaded file, not a verified county record. A page request is not proof anyone booked a survey. The page URL can say well drilling even when no form is submitted. Ask what happens to the address, the GPS pin, the off-grid note, and the plat map after a survey closes — the stack that mapped your water source outlives the quote. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking or survey page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a well-permit-legality claim, an off-grid-water-safety claim, a drilling-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 site-survey bookings, plat maps, and page tags go
Bookings and surveys on your WordPress site
Check which address, GPS, acreage, off-grid, pump-power, plat-map, permit, or intake-upload fields you enable, who can open form entries and site-survey bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a survey closes — when the address-plus-GPS-plus-plat row still holds rural coordinates next to an off-grid dependency note. Notification emails can also copy those fields off-site. One table can list every "44 Rural Rd · GPS 41.2,-95.1 · 5 acres · off-grid · pump: 1.5HP · power: solar · plat.pdf · permit: pending" stack next to a customer name. Ask your web vendor not to keep GPS pins and plat maps next to home addresses and off-grid notes in one open submissions list longer than operations need, and to purge those fields when a survey closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored well-survey booking is not proof a well was drilled. A GPS, plat, or permit answer is not a verified county record.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the booking or survey page. That page request can reach a vendor host before anyone submits. The page URL can say well drilling even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and survey pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "well drilling privacy" badge is not a verified storage path.
Well-drilling site-survey, plat-map, 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 well-drilling 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 Thursday site-survey window or a pre-drill visit slot is a booking you create; a service name such as well drill or pump install is a label you configure. Neither is a documented default. Address, GPS, acreage, off-grid, pump-power, plat-map, or permit 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 well was drilled — and a CSV export of "44 Rural Rd · GPS 41.2,-95.1 · 5 acres · off-grid · pump: 1.5HP · power: solar · plat.pdf · permit: pending" next to a customer name is still a calendar that pairs rural coordinates with an off-grid dependency note. 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. | Well-drilling site-survey 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, GPS, acreage, off-grid, pump-power, plat-map, or permit fields are fields you add; they are not documented defaults. Completing the form can store an address-plus-GPS-plus-plat stack ("44 Rural Rd · GPS 41.2,-95.1 · 5 acres · off-grid · pump: 1.5HP · power: solar · plat.pdf · permit: pending") — typed once so a driller can quote a site survey, into the same tables as a "well drilling" label. A GPS, plat, or permit answer is a form answer or uploaded file, not a verified county record. A well-survey booking is a calendar row, not proof a well was drilled — and a staff login can open "Jordan, 44 Rural Rd, GPS 41.2,-95.1, off-grid, plat.pdf, permit pending" 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, GPS, and plat answers stored in WordPress; optional plat maps 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, GPS, or plat-map field was sent. A page request from this script is not proof anyone booked a survey. The page URL can say well drilling even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and survey 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, GPS, acreage, off-grid, pump-power, plat-map, or permit fields often depend on the fields you configure. A well-survey booking is a calendar row, not proof a well was drilled. A GPS, plat, or permit answer is a form answer or uploaded file, not a verified county record. A marketing-tag page request is not proof anyone booked a survey. The page URL can say well drilling even when no form is submitted. The address-plus-GPS-plus-plat row that mapped your water source for a driller — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that infrastructure-dependency stack, not a water-testing lab result, a septic waste-side ledger, or a mold indoor-contamination note. Ask your web vendor who can open entries, whether a marketing tag loads on the booking or survey page, and how long records and backups are kept. A "well drilling privacy" or "site-survey ready" 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 well-permit legality, off-grid-water-safety, or drilling-code compliance. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking and survey 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-well-drilling-plugin-privacy