Deck builder plugin privacy

The design quote that maps your backyard — and the crew's gate code

A deck-builder WordPress stack is not only a quote calendar — it is often a map of your backyard. Every confirmed design visit can store property lines, the gate code for the crew, and the sightline from the new deck into every neighbor's yard, next to a name and address in a forms table. A backyard photo can sit beside that map in the uploads folder. A page request is not proof anyone booked. A property-line answer is a stored measurement, not proof of a surveyed boundary. A gate-code note is stored text, not proof anyone entered. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where backyard photos land, which inboxes receive copies, and how long past quotes, files, and backups are kept.

Documentation review only. This is not legal advice, a trespass claim, a neighbor-dispute claim, a survey-outcome claim, a GDPR or other compliance assessment, or a judgment about deck 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 property lines, gate codes, and design bookings go

Entries, bookings, and uploads on your WordPress site

Check which property-line, gate-code, neighbor-sightline, backyard-photo, design-notes, or measurement fields you enable, who can open form entries and design bookings, where uploaded backyard photos live in the uploads folder, which inboxes receive copies, and how long past quotes, files, and backups are kept after a design visit that never happened. Notification emails can also copy the same address, gate-code 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 design calendar. A "deck builder" badge is not a verified storage path.

Deck-builder design, quote-form, and backyard-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 deck-builder 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 "design consult Sat 9am — gate code 4412" window or a "sightline into the Miller yard from the NW corner" note is a booking you create; a service name such as deck design or patio build is a label you configure. Neither is a documented default. Property-line, gate-code, neighbor-sightline, or backyard-photo 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 entry — and a CSV export of "gate 4412 + NW sightline + backyard photo" next to a named homeowner is still a calendar that answers how to enter the yard for a design visit. 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.

Deck design 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-line, gate-code, neighbor-sightline, design-notes, property-address, contact-name, phone, or email questions are fields you add; they are not documented defaults. Optional backyard-photo uploads are files you accept; that file type is not a documented default. A property-line answer is a stored measurement, not proof of a surveyed boundary. A gate-code note is stored text, not proof anyone entered. A deck-builder form is not proof anyone designed or built. 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 property-line row sits after a quote that never happened is not a documented default of the plugin.

Property-line and gate-code answers stored in WordPress; optional backyard-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 backyard photo or site sketch is a file you accept; that file type is not a documented default. An uploaded backyard photo is a stored file, not a trespass 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 backyard-photo file sits after a quote that never happened is not a documented default of the plugin.

Backyard-photo 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. Property-line, gate-code, neighbor-sightline, backyard-photo, or design-notes fields often depend on the fields you configure. A property-line answer is a stored measurement, not proof of a surveyed boundary. A gate-code note is stored text, not proof anyone entered. A deck-builder booking is not proof anyone designed or built. A page request is not proof anyone booked. The page URL can say deck builder even when no form is submitted. Ask your web vendor who can open entries and uploads, whether backyard 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 trespass risk, neighbor disputes, or survey outcomes. Review stored records, uploaded photos, connected services, exports, notification emails, and backups.

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

Related pages

Scan your site for third-party requests

/wp-deck-builder-plugin-privacy