Excavation plugin privacy

The dig quote that maps your property's underside before any permit is public

An excavation WordPress stack is not only a job calendar. It is often a map of the lot before any permit is public. Every dig quote can store site sketches, utility-locate results, where the pool or foundation is going, soil photos, and lot lines. Machines left on site overnight mean the intake also stores gate codes and the exact dates a property is torn open and unfenced. A page request is not proof anyone booked. A site sketch is a stored file, not a surveyed plan. A gate code is stored text, not proof anyone entered. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where sketches land, which inboxes receive copies, and how long past tickets, files, and backups are kept.

Documentation review only. This is not legal advice, a permit claim, a utility-locate claim, a landscaping claim, a GDPR or other compliance assessment, or a judgment about excavators.

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 site sketches, utility locates, and dig bookings go

Entries, bookings, and uploads on your WordPress site

Check which site-sketch, utility-locate, pool-location, soil-photo, lot-line, overnight-machine, gate-code, or unfenced-window fields you enable, who can open form entries and service bookings, where uploaded sketches live in the uploads folder, which inboxes receive copies, and how long past tickets, files, and backups are kept after a dig that never happened. Notification emails can also copy the same address, lot lines, and sketch links off-site.

Uploads or connected destinations off your WordPress site

Some upload tools can send files to FTP, SFTP, or cloud destinations you enable. Review which destinations you turn on, account access, and retention there. A browser scan cannot inspect stored form entries, bookings, or who opened the service calendar. A "licensed excavator" badge is not a verified storage path.

Excavation booking, site-sketch, and utility-locate 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 excavation 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 dig window or a "machines overnight — gate code 4412, lot unfenced Friday-Monday" access note is a booking you create; a service name such as excavation or pool dig is a label you configure. Neither is a documented default. Site-sketch, utility-locate, pool-location, soil-photo, lot-line, overnight-machine, gate-code, or unfenced-window questions are custom fields you add (textarea, select, input, checkbox, or file); they are not documented defaults. A booking is a calendar row, not proof of a dig — and a CSV export of "gate code 4412 + pool location + unfenced Friday-Monday" next to a named owner is still a calendar that answers when the lot sits open. 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.

Excavation service 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. Site-sketch, utility-locate, pool-location, soil-photo, lot-line, overnight-machine, gate-code, unfenced-window, property-address, owner-name, phone, or email questions are fields you add; they are not documented defaults. Optional sketch uploads are files you accept; that file type is not a documented default. A site sketch is a stored file, not a surveyed plan. A gate code is stored text, not proof anyone entered. An excavation form is not proof anyone dug. 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. How long a site sketch sits after a dig that never happened is not a documented default of the plugin.

Site-sketch and locate answers stored in WordPress; optional sketch uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
Iptanus File Upload

Documented frontend upload form (formerly WordPress File Upload). By default files land inside the wp-content directory of the site; the upload path is configurable. Uploaded files can be added to Media or attached to the current page. FTP and SFTP destinations are documented. The Professional version documents uploads to Google Drive, Dropbox, OneDrive, or Amazon S3. A site sketch or soil photo is a file you accept; that file type is not a documented default. An uploaded site sketch is a stored file, not a surveyed plan. Deleting a form entry later does not by itself prove the file was removed from the uploads path or from a cloud destination you enabled. The listing claims GDPR compliance without a tested EXIF-strip or retention length here. Review upload directory, Media attachment, and cloud destinations. Browser hosts for the visitor upload path were not verified for this snapshot. How long a sketch file sits after a dig that never happened is not a documented default of the plugin.

Site-sketch and soil-photo uploads stored under the site wp-content pathBrowser hosts not verifiedNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Site-sketch, utility-locate, pool-location, soil-photo, lot-line, overnight-machine, gate-code, or unfenced-window fields often depend on the fields you configure. A site sketch is a stored file, not a surveyed plan. A gate code is stored text, not proof anyone entered. An excavation booking is not proof anyone dug. A page request is not proof anyone booked. The page URL can say excavation even when no form is submitted. Ask your web vendor who can open entries and uploads, whether sketches remain reachable by direct URL, and how long records and backups are kept. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess teardown, septic records, well reports, or landscaping windows. Review stored records, uploaded photos, connected services, exports, notification emails, and backups.

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

Related pages

Scan your site for third-party requests

/wp-excavation-plugin-privacy