Masonry plugin privacy

The repair estimate that photographs every crack in your foundation

A masonry WordPress stack is not only a repair calendar. It is often a photo log of every crack in the foundation. Every quote can store photos of the loose brick by the back door, the chimney base, and the retaining wall that hides the yard, each one dated for a week the homeowner said they would be at work. A page request is not proof anyone booked. A crack photo is a stored file, not a structural claim. A work-week window is stored text, not proof anyone entered. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where crack 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 structural-damage claim, a property-survey claim, a burglary-risk claim, a GDPR or other compliance assessment, or a judgment about masons.

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 crack photos, work-week windows, and masonry bookings go

Entries, bookings, and uploads on your WordPress site

Check which crack-photo, loose-brick, chimney-base, retaining-wall, work-week, property-address, owner-name, phone, email, or appointment-date fields you enable, who can open form entries and service bookings, where uploaded crack 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-mason badge is not a verified storage path.

Masonry booking, crack-photo, and work-week 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 masonry 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 "work week Tue-Thu, homeowner at work, back-door brick photo" is a booking you create; a service name such as masonry or brick repair is a label you configure. Neither is a documented default. Crack-photo, loose-brick, chimney-base, retaining-wall, work-week, 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 "Tue-Thu empty + back-door brick photo + retaining-wall crack" 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.

Masonry 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. Crack-photo, loose-brick, chimney-base, retaining-wall, work-week, property-address, owner-name, phone, email, or appointment-date questions are fields you add; they are not documented defaults. Optional crack photo uploads are files you accept; that file type is not a documented default. A crack photo is a stored file, not a structural claim. A work-week window is stored text, not proof anyone entered. A masonry form is not proof anyone repaired 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 crack photo sits after a call that never happened is not a documented default of the plugin.

Crack-photo answers stored in WordPress; optional crack-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 crack photo or estimate PDF is a file you accept; that file type is not a documented default. An uploaded crack photo is a stored file, not a structural 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 crack photo file sits after a call that never happened is not a documented default of the plugin.

Crack-photo and estimate 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. Crack-photo, loose-brick, chimney-base, retaining-wall, or work-week fields often depend on the fields you configure. A crack photo is a stored file, not a structural claim. A work-week window is stored text, not proof anyone entered. A masonry booking is not proof anyone repaired a wall. A page request is not proof anyone booked. The page URL can say masonry even when no form is submitted. Ask your web vendor who can open entries and uploads, whether crack 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 foundation damage, chimney flues, or driveway pours. 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-masonry-plugin-privacy