Land surveyor plugin privacy
The survey order that files the neighbor war before anyone has sued
The request form asks why you need the survey, and people answer honestly: "neighbor's new fence is over my line." It stores both addresses, the deed and plat uploads, and your legal theory in your own words — the first document of a lawsuit that doesn't exist yet. The lateral truth: a survey order is a dispute with coordinates. Leak it and you've told the neighbor exactly what you suspect, handed them your evidence list, and told the whole street which two houses are at war. Those fields are configured, not documented defaults. A land-surveyor booking is a calendar row, not proof a boundary dispute exists or that a fence crossed a line. A why, address, deed, or plat answer is a form answer or uploaded file, not a verified boundary. A page request is not proof anyone ordered a survey. The page URL can say land surveyor even when no form is submitted. Ask what happens to the name, both addresses, the why answer, and the deed and plat uploads after a survey finishes — the stack that filed the neighbor war outlives the appointment. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking or quote page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a lawsuit claim, a boundary-proof claim, a surveyor-licensing claim, a trespass claim, a title-defect claim, an adverse-possession 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 land-surveyor bookings, survey orders, and page tags go
Bookings and survey orders on your WordPress site
Check which why, both-address, deed, plat, legal-theory, name, or service-address fields you enable, who can open form entries and land-surveyor bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a survey finishes — when the name-plus-both-addresses-plus-why row still holds a dispute-with-coordinates answer next to both houses. Notification emails can also copy those fields off-site. One table can list every "Alex · 12 Oak St · neighbor: 14 Oak St · reason: fence over line · deed.pdf · plat.pdf" stack next to a customer name. Ask your web vendor not to keep why, both-address, deed, and plat answers next to names in one open submissions list longer than operations need, and to purge those fields when a survey order ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored land-surveyor booking is not proof a boundary dispute exists or that a fence crossed a line. A why, address, deed, or plat answer is not a verified boundary.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the booking or quote page. That page request can reach a vendor host before anyone submits. The page URL can say land surveyor even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and quote pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "land surveyor privacy" badge is not a verified storage path.
Land-surveyor booking, survey-order, 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 land-surveyor 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 boundary survey or a stakeout slot is a booking you create; a service name such as residential boundary or ALTA is a label you configure. Neither is a documented default. Why, both-address, deed, plat, or legal-theory 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 boundary dispute exists or that a fence crossed a line — and a CSV export of "Alex · 12 Oak St · neighbor: 14 Oak St · reason: fence over line · deed.pdf · plat.pdf" next to a customer name is still a calendar that pairs a dispute-with-coordinates answer with both houses. 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. | Land-surveyor 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. Why, both-address, deed, plat, or legal-theory fields are fields you add; they are not documented defaults. Completing the form can store a name-plus-both-addresses-plus-why stack ("Alex · 12 Oak St · neighbor: 14 Oak St · reason: fence over line · deed.pdf · plat.pdf") — typed or uploaded once so a shop can schedule a survey, into the same tables as a "land surveyor" label. A why, address, deed, or plat answer is a form answer or uploaded file, not a verified boundary. A land-surveyor booking is a calendar row, not proof a boundary dispute exists or that a fence crossed a line — and a staff login can open "Alex, 12 Oak St, neighbor 14 Oak St, fence over line, deed.pdf, plat.pdf" 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. | Name, both addresses, and survey-order answers stored in WordPress; optional deed or plat 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 why, both-address, deed, or plat field was sent. A page request from this script is not proof anyone ordered a survey. The page URL can say land surveyor even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and quote 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. Why, both-address, deed, plat, or legal-theory fields often depend on the fields you configure. A land-surveyor booking is a calendar row, not proof a boundary dispute exists or that a fence crossed a line. A why, address, deed, or plat answer is a form answer or uploaded file, not a verified boundary. A marketing-tag page request is not proof anyone ordered a survey. The page URL can say land surveyor even when no form is submitted. The name-plus-both-addresses-plus-why row that filed the neighbor war for a shop — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that survey-order stack, not an HOA violation complaint naming a neighbor, a mediation both-sides database, a court-reporting pre-docket party list, or a dog-behaviorist bite-history log. Ask your web vendor who can open entries, whether a marketing tag loads on the booking or quote page, and how long records and backups are kept. A "land surveyor privacy" or "survey order 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 lawsuits, boundary proof, or surveyor licensing. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking and quote 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-land-surveyor-plugin-privacy