Landscaping plugin privacy
The mowing schedule that broadcasts exactly when nobody is home
A landscaping WordPress stack is not only a mowing calendar — it is often a standing-access grant. Every confirmed contract can store the gate code, the dog's name and whether it bites, vacation holds that mark the house empty, and property photos that inventory the yard and everything visible through the windows. The weekly crew window is a published pattern of absence, renewed every season by the same form. A page request is not proof anyone booked. A gate code is stored text, not proof anyone entered. A vacation hold is a stored calendar slot, not proof the house stood empty. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where yard photos land, which inboxes receive copies, and how long past contracts, files, and backups are kept.
Documentation review only. This is not legal advice, a burglary-risk claim, a pet-behavior claim, a GDPR or other compliance assessment, or a judgment about landscapers.
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 gate codes, vacation holds, and mowing schedules go
Entries, bookings, and uploads on your WordPress site
Check which gate-code, dog-note, vacation-hold, yard-photo, or weekly-crew-window fields you enable, who can open form entries and recurring bookings, where uploaded yard photos live in the uploads folder, which inboxes receive copies, and how long past contracts, files, and backups are kept after a season that never started. 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 crew calendar. A "fully insured crew" badge is not a verified storage path.
Landscaping booking, gate-code, and yard-photo 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 landscaping SaaS platforms 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 weekly mow window or a "gate 3310 — dog bites — vacation Jul 1-15" access note is a booking you create; a service name such as landscaping or lawn care is a label you configure. Neither is a documented default. Gate-code, dog-note, vacation-hold, yard-photo, or weekly-crew-window 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 "Tue 9am crew + gate 3310 + vacation Jul 1-15" next to a named homeowner is still a calendar that publishes when nobody is home. 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. | Landscaping crew 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. Gate-code, dog-note, vacation-hold, yard-photo, weekly-crew-window, property-address, owner-name, phone, or email questions are fields you add; they are not documented defaults. Optional yard-photo uploads are files you accept; that file type is not a documented default. A gate code is stored text, not proof anyone entered. A vacation hold is a stored select, not proof the house stood empty. A landscaping form is not proof anyone mowed. 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 gate code sits after a season that never started is not a documented default of the plugin. | Gate-code and vacation answers stored in WordPress; optional yard-photo uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| 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 yard photo is a file you accept; that file type is not a documented default. An uploaded yard photo is a stored file, not a burglary 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 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 yard-photo file sits after a season that never started is not a documented default of the plugin. | Yard-photo and document uploads stored under the site wp-content path | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Gate-code, dog-note, vacation-hold, yard-photo, or weekly-crew-window fields often depend on the fields you configure. A gate code is stored text, not proof anyone entered. A vacation hold is a stored calendar slot, not proof the house stood empty. A landscaping booking is not proof anyone mowed. A page request is not proof anyone booked. The page URL can say landscaping even when no form is submitted. Ask your web vendor who can open entries and uploads, whether yard 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 burglary risk or pet behavior. 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
- WordPress booking plugin privacy
- WordPress forms privacy
- WordPress payment gateway privacy
- All privacy guides
/wp-landscaping-plugin-privacy