Epoxy flooring plugin privacy
The garage-floor quote whose photos inventory everything you park and shelve
An epoxy-flooring WordPress stack is not only a pour calendar — it is often a photo inventory of everything you park and shelve in the garage. Every confirmed floor quote can store vehicle-and-shelf notes, square-footage measurements, and garage photos, next to a name and address in a forms table. A garage photo can sit beside those notes in the uploads folder. A page request is not proof anyone booked. A parked-vehicle note is stored text, not proof anyone parked. A pour window is a stored schedule, not proof the crew arrived. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where uploads land, which inboxes receive copies, and how long past quotes, files, and backups are kept.
Documentation review only. This is not legal advice, a flooring-outcome claim, an insurance claim, a concrete claim, a garage-organization claim, a GDPR or other compliance assessment, or a judgment about epoxy flooring contractors.
Scan your site for third-party requestsThe 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 garage inventories, pour bookings, and floor photos go
Entries, bookings, and uploads on your WordPress site
Check which garage-photo, parked-vehicle, shelf-inventory, square-footage, pour-window, or access-notes fields you enable, who can open form entries and pour bookings, where uploaded garage photos live in the uploads folder, which inboxes receive copies, and how long past quotes, files, and backups are kept after a pour that never happened. Notification emails can also copy the same address, inventory 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 pour calendar. An "epoxy flooring" badge is not a verified storage path.
Epoxy-flooring quote, pour-booking, and garage-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 epoxy flooring SaaS platforms without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| 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 "pour window Sat AM — 2-car garage; move bikes to side" window or a "flake color: gunmetal" note is a booking you create; a service name such as garage coat or commercial epoxy is a label you configure. Neither is a documented default. Garage-photo, parked-vehicle, shelf-inventory, or pour-window 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 a pour — and a CSV export of "2-car garage + flake gunmetal + garage photo" next to a named homeowner is still a calendar that inventories what is parked and shelved. 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. | Epoxy pour and quote bookings stored on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| 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. garage-photo, parked-vehicle, shelf-inventory, square-footage, pour-window, property-address, contact-name, phone, or email questions are fields you add; they are not documented defaults. Optional uploads are files you accept; that file type is not a documented default. A pour window is a stored schedule, not proof the crew arrived. A parked-vehicle note is stored text, not proof anyone parked. A epoxy flooring form is not proof anyone coated. 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 row sits after a pour that never happened is not a documented default of the plugin. | Garage-inventory and square-footage answers stored in WordPress; optional garage-photo uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| 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 garage photo is a file you accept; that file type is not a documented default. An uploaded file is a stored file, not an inventory claim beyond the file itself. 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 file sits after a pour that never happened is not a documented default of the plugin. | Garage-photo and document uploads stored under the site wp-content path | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. garage-photo, parked-vehicle, shelf-inventory, square-footage, pour-window fields often depend on the fields you configure. A parked-vehicle note is stored text, not proof anyone parked. A pour window is a stored schedule, not proof the crew arrived. A epoxy flooring booking is not proof anyone coated. A page request is not proof anyone booked. The page URL can say epoxy flooring even when no form is submitted. Ask your web vendor who can open entries and uploads, whether uploads 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 flooring outcomes, insurance coverage, concrete slabs, or garage organization. Review stored records, uploaded files, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 22, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress forms privacy
- WordPress payment gateway privacy
- All privacy guides
/wp-epoxy-flooring-plugin-privacy