Stump grinding plugin privacy

The quote that measures your gate and asks about the dog

A stump-grinding WordPress stack is not only a one-visit trade calendar — it is often a backyard entry checklist. Every confirmed quote can store gate width for the grinder, whether a dog is loose in the yard, where the sprinkler lines and septic lids are, and side-yard access photos. One quote request documents every way into the backyard and every reason the crew (or anyone who reads the entry) will not be surprised once they are in. A page request is not proof anyone booked. A gate-width note is stored text, not proof anyone entered. A dog note is stored text, not a pet-behavior claim. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where access photos land, which inboxes receive copies, and how long past quotes, files, and backups are kept.

Documentation review only. This is not legal advice, a tree-service claim, an excavation claim, a pet-behavior claim, a burglary-risk claim, a GDPR or other compliance assessment, or a judgment about stump-grinding crews.

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 gate-width notes, dog notes, and access photos go

Entries, bookings, and uploads on your WordPress site

Check which gate-width, dog-loose, sprinkler-line, septic-lid, side-yard-access, stump-photo, property-address, or quote fields you enable, who can open form entries and job bookings, where uploaded access photos live in the uploads folder, which inboxes receive copies, and how long past quotes, files, and backups are kept after a grind that never happened. Notification emails can also copy the same address, access notes, and photo 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 grind calendar. A "insured stump crew" badge is not a verified storage path.

Stump-grinding quote, access-photo, and dog-note 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 stump grinding 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 grind window or a "gate 42in — dog loose — septic left side" access note is a booking you create; a service name such as stump grinding is a label you configure. Neither is a documented default. Gate-width, dog-loose, sprinkler-line, septic-lid, side-yard-access, or stump-photo questions are custom fields you add; they are not documented defaults. A booking is a calendar row, not proof of entry — and a CSV export of "Thu grind + gate 42in + dog loose" next to a named homeowner is still a calendar that publishes how to get into the yard. 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.

Stump-grinding job 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-width, dog-loose, sprinkler-line, septic-lid, side-yard-access, stump-photo, property-address, owner-name, phone, or email questions are fields you add; they are not documented defaults. Optional access-photo uploads are files you accept; that file type is not a documented default. A gate-width note is stored text, not proof anyone entered. A dog note is stored text, not a pet-behavior claim. A stump-grinding form is not proof anyone ground a stump. 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 record sits after a grind that never happened is not a documented default of the plugin.

Gate-width and dog answers stored in WordPress; optional access-photo 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. An access photo is a file you accept; that file type is not a documented default. An uploaded access photo is a stored file, not a break-in map claim. Deleting a form entry later does not by itself prove the file was removed from the uploads path or from a cloud destination you enable. 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 file sits after a grind that never happened is not a documented default of the plugin.

Access-photo and document 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. Gate-width, dog-loose, sprinkler-line, septic-lid, side-yard-access fields often depend on the fields you configure. A gate-width note is stored text, not proof anyone entered. A dog note is stored text, not a pet-behavior claim. A stump-grinding booking is not proof anyone ground a stump. A page request is not proof anyone booked. The page URL can say stump grinding even when no form is submitted. Ask your web vendor who can open entries and uploads, whether photos 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 tree-service, excavation, pet-behavior, burglary-risk. 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-stump-grinding-plugin-privacy