Wine cellar construction plugin privacy

The build-out quote that inventories a five-figure collection and maps the hidden room

A wine-cellar construction WordPress stack is not only a climate-room calendar. It is often a collection inventory plus a hidden-room map. Every quote can store bottle photos, racking layouts, and the room that is not on the public floor plan, dated for the week the crew said they would start cooling. A page request is not proof anyone booked. A collection photo is a stored file, not an appraisal. A room plan is stored text, not a survey. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where cellar photos land, which inboxes receive copies, and how long past tickets, files, and backups are kept.

Documentation review only. This is not legal advice, a wine-club claim, a subscription claim, a GDPR or other compliance assessment, or a judgment about cellar builders.

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 collection photos, room plans, and cellar bookings go

Entries, bookings, and uploads on your WordPress site

Check which collection-photo, bottle-list, room-plan, humidity-note, property-address, owner-name, phone, email, or appointment-date fields you enable, who can open form entries and service bookings, where uploaded cellar photos live in the uploads folder, which inboxes receive copies, and how long past tickets, files, and backups are kept after a call that never happened. Notification emails can also copy the same address, dates, 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 service calendar. A licensed-contractor badge is not a verified storage path.

Wine-cellar construction booking, collection-photo, and room-plan 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 cellar-CAD 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 window such as "climate-room week, collection photo, room plan" is a booking you create; a service name such as wine cellar or climate room is a label you configure. Neither is a documented default. Collection-photo, bottle-list, room-plan, humidity-note, property-address, owner-name, phone, email, or appointment-date 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 work - and a CSV export of "climate-room week + collection photo + room plan" next to a named owner is still a calendar that answers when the crew is expected. 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.

Wine-cellar construction 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. Collection-photo, bottle-list, room-plan, humidity-note, property-address, owner-name, phone, email, or appointment-date questions are fields you add; they are not documented defaults. Optional cellar collection photo uploads are files you accept; that file type is not a documented default. A collection photo is a stored file, not an appraisal. A room plan is stored text, not a survey. A cellar-construction form is not proof anyone started cooling. 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 cellar collection photo sits after a call that never happened is not a documented default of the plugin.

Collection and room-plan answers stored in WordPress; optional cellar-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. A cellar photo or room-plan PDF is a file you accept; that file type is not a documented default. An uploaded collection photo is a stored file, not an appraisal. 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 cellar collection photo file sits after a call that never happened is not a documented default of the plugin.

Cellar-photo and room-plan 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. Collection-photo, bottle-list, room-plan, or humidity-note fields often depend on the fields you configure. A collection photo is a stored file, not an appraisal. A room plan is stored text, not a survey. A cellar-construction booking is not proof anyone started cooling. A page request is not proof anyone booked. The page URL can say wine cellar construction even when no form is submitted. Ask your web vendor who can open entries and uploads, whether cellar 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 wine clubs or subscriptions. Review stored records, uploaded photos, connected services, exports, notification emails, and backups.

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

Related pages

Scan your site for third-party requests

/wp-wine-cellar-construction-plugin-privacy