Drywall plugin privacy

The repair quote that photographs the hole and asks what made it

A drywall WordPress stack is not only a patch calendar — it is often a dated incident file. Every confirmed quote can store a hole photo with a timestamp, a reason dropdown (water, doorknob, fist, break-in), room location, and the access window for the crew. Patch photos quietly date every incident in a home; the reason field turns a wall into a record of what happened in front of it. A page request is not proof anyone booked. A patch photo is a stored file, not a damage appraisal. A reason select is stored text, not a police report. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where patch 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 restoration claim, a foundation-repair claim, a handyman claim, a burglary-risk claim, a GDPR or other compliance assessment, or a judgment about drywall 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 patch photos, damage reasons, and drywall quotes go

Entries, bookings, and uploads on your WordPress site

Check which hole-photo, damage-reason, room-location, access-window, property-address, or quote fields you enable, who can open form entries and job bookings, where uploaded patch photos live in the uploads folder, which inboxes receive copies, and how long past quotes, files, and backups are kept after a patch that never happened. Notification emails can also copy the same address, reason 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 patch calendar. A "insured drywall crew" badge is not a verified storage path.

Drywall quote, patch-photo, and damage-reason 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 drywall 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 patch window or a "bedroom — water stain — owner home Tue 10-2" access note is a booking you create; a service name such as drywall or patch is a label you configure. Neither is a documented default. Hole-photo, damage-reason, room-location, or access-window questions are custom fields you add; they are not documented defaults. A booking is a calendar row, not proof of a patch — and a CSV export of "Tue patch + water + hole photo" next to a named homeowner is still a calendar that dates what happened to the wall. 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.

Drywall repair 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. Hole-photo, damage-reason, room-location, access-window, property-address, owner-name, phone, or email questions are fields you add; they are not documented defaults. Optional patch-photo uploads are files you accept; that file type is not a documented default. A patch photo is a stored file, not a damage appraisal. A reason select is stored text, not a police report. A drywall form is not proof anyone patched a wall. 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 patch that never happened is not a documented default of the plugin.

Damage-reason and access answers stored in WordPress; optional patch-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 patch photo is a file you accept; that file type is not a documented default. An uploaded patch photo is a stored file, not an incident 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 patch that never happened is not a documented default of the plugin.

Patch-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. Hole-photo, damage-reason, room-location, access-window fields often depend on the fields you configure. A patch photo is a stored file, not a damage appraisal. A reason select is stored text, not a police report. A drywall booking is not proof anyone patched a wall. A page request is not proof anyone booked. The page URL can say drywall 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 restoration, foundation-repair, handyman, 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-drywall-plugin-privacy