Sugar shack construction plugin privacy

Where your sugar-shack plans and property details go

If your sugar-shack quote form collects acreage, tap counts, equipment details, or property maps, check where those records 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 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 sugarbush maps, tap counts, and sugar-shack 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.

Sugar-shack-construction booking, sugarbush-map, and tap-count 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 maple-syrup / sugar-shack SaaS platforms without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
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.

Sugar shack 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. Property-address, wooded-acreage, tap-count, evaporator-specs, hobby-vs-commercial-intent, owner-name, phone, email, or appointment-date questions are fields you add; they are not documented defaults. Optional sugarbush-map uploads are files you accept; that file type is not a documented default. A tap count is stored text, not a survey of your sugarbush. An acreage note is stored text, not a deed extract. A sugar shack construction form is not proof of completed work. 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 sugarbush map sits after a call that never happened is not a documented default of the plugin.

Tap-count and acreage answers stored in WordPress; optional sugarbush-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 sugarbush-map PDF is a file you accept; that file type is not a documented default. An uploaded sugarbush-map PDF is a stored file, not proof of completed work. 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 sugarbush-map file sits after a call that never happened is not a documented default of the plugin.

Sugarbush-map and evaporator-plan uploads stored under the site wp-content pathBrowser hosts not verifiedNot assessedNot tested
  • None

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 27, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-sugar-shack-construction-plugin-privacy