Irrigation plugin privacy

The controller login that knows when your lawn — and you — are away

An irrigation WordPress stack is not only a sprinkler service calendar — it is often a yard-and-absence dossier. Every confirmed quote can store a smart-controller login shared with the crew, a zone map that diagrams the whole yard, and a vacation-mode schedule that is a written record of the weeks the house stands empty. The controller account knows when the lawn — and you — are away. A page request is not proof anyone booked. A zone map is a stored file, not a survey claim. A vacation-mode window 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 zone maps land, which inboxes receive copies, and how long past quotes, files, and backups are kept.

Documentation review only. This is not legal advice, a landscaping claim, a well-drilling claim, a stump-grinding claim, a burglary-risk claim, a GDPR or other compliance assessment, or a judgment about irrigation contractors.

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 controller logins, zone maps, and vacation schedules go

Entries, bookings, and uploads on your WordPress site

Check which controller-login, zone-map, vacation-mode, access-code, property-address, or quote fields you enable, who can open form entries and service bookings, where uploaded zone maps live in the uploads folder, which inboxes receive copies, and how long past quotes, files, and backups are kept after a service that never happened. Notification emails can also copy the same login notes, vacation windows, and map 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 "smart irrigation pro" badge is not a verified storage path.

Irrigation quote, zone-map, and vacation-mode 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 irrigation 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 service window or a "vacation mode Jul 1-21 — controller login shared — zone map attached" access note is a booking you create; a service name such as irrigation or sprinkler repair is a label you configure. Neither is a documented default. Controller-login, zone-map, vacation-mode, or access-code questions are custom fields you add; they are not documented defaults. A booking is a calendar row, not proof of a valve turn — and a CSV export of "Jul vacation + controller login + zone map" 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.

Irrigation 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. Controller-login, zone-map, vacation-mode, access-code, property-address, owner-name, phone, or email questions are fields you add; they are not documented defaults. Optional zone-map uploads are files you accept; that file type is not a documented default. A zone map is a stored file, not a survey claim. A vacation-mode window is a stored select, not proof the house stood empty. An irrigation form is not proof anyone adjusted a valve. 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 service that never happened is not a documented default of the plugin.

Vacation-mode and controller answers stored in WordPress; optional zone-map 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 zone map is a file you accept; that file type is not a documented default. An uploaded zone map is a stored file, not a yard inventory 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 service that never happened is not a documented default of the plugin.

Zone-map 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. Controller-login, zone-map, vacation-mode, access-code fields often depend on the fields you configure. A zone map is a stored file, not a survey claim. A vacation-mode window is a stored calendar slot, not proof the house stood empty. An irrigation booking is not proof anyone adjusted a valve. A page request is not proof anyone booked. The page URL can say irrigation 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 landscaping, well-drilling, stump-grinding, 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-irrigation-plugin-privacy