Vineyard installation plugin privacy
Where your vineyard plans and property details go
If your vineyard enquiry form collects acreage, irrigation notes, water-rights answers, or site plans, check where those details go and who can open them. This guide compares three plugins using public documentation. Review email copies, uploads, exports, and backups as well as WordPress entries.
Documentation review only. Consent timing, access controls, and retention have not been tested. This is not a legal or 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 site plans, water-rights answers, and planting bookings go
Entries, bookings, and uploads on your WordPress site
Check which fields you collect, who can open entries and uploaded plans, and which inboxes receive copies. Review how long bookings, files, exports, and backups remain. Email notifications and connected services can create copies outside WordPress.
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-contractor badge is not a verified storage path.
Vineyard-installation booking, site-plan, and water-rights 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 vineyard-installer 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 Easy Appointments v4.0.3 is a self-hosted booking plugin. Its admin screens provide appointment and customer lists and CSV export. You choose the service labels and custom questions; the cited readme lists textarea, select, and input fields. Property and project details are configured examples, not defaults. Notification emails can copy booking details off-site. Customer-data deletion and external integrations are optional. Visitor-browser hosts were not verified. | Vineyard-installation service 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. Property-address, acreage, soil-detail, irrigation-detail, water-rights-status, hobby-vs-commercial-intent, budget, owner-name, phone, email, or appointment-date questions are fields you add; they are not documented defaults. Optional site-plan uploads are files you accept; that file type is not a documented default. A soil note is stored text, not a lab assay. A water-rights answer is stored text, not a deed abstract. A planting form is not proof anyone set a trellis. 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 plan sits after a call that never happened is not a documented default of the plugin. | Water-rights and hobby-vs-commercial answers stored in WordPress; optional site-plan 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 site-plan or soil-map PDF is a file you accept; that file type is not a documented default. An uploaded site-plan PDF is a stored file, not a survey of your farm. 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 site-plan file sits after a call that never happened is not a documented default of the plugin. | Site-plan and soil-map uploads stored under the site wp-content path | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
These examples depend on the fields and integrations you enable. Review who can open entries and files, which inboxes receive copies, and how long records and backups remain. This guide summarizes plugin documentation; it does not test your site's storage or access controls.
Documentation snapshot: Oct 25, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress forms privacy
- WordPress gallery plugin privacy
- All privacy guides
/wp-vineyard-installation-plugin-privacy