Flooring plugin privacy
The room-by-room measurement that books the week you sleep elsewhere
A flooring WordPress stack is not only a quote calendar — it is often a whole-house plan with dates attached. Every confirmed measurement can store room-by-room furniture notes and the week your family sleeps somewhere else, next to a name and address in a forms table. A floor-plan photo can sit beside that schedule in the uploads folder. A page request is not proof anyone booked. A furniture-inventory answer is a stored list, not proof rooms were emptied. A sleep-elsewhere week is a stored schedule, not proof anyone left. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where floor-plan 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 vacancy-risk claim, an insurance claim, a tile-installation claim, a GDPR or other compliance assessment, or a judgment about flooring companies.
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 furniture inventories, sleep-elsewhere weeks, and measurement bookings go
Entries, bookings, and uploads on your WordPress site
Check which room-by-room, furniture-inventory, sleep-elsewhere-week, floor-plan-photo, measurement-notes, or measurement fields you enable, who can open form entries and measurement bookings, where uploaded floor-plan photos live in the uploads folder, which inboxes receive copies, and how long past quotes, files, and backups are kept after a measurement that never happened. Notification emails can also copy the same address, schedule 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 measurement calendar. A "flooring installer" badge is not a verified storage path.
Flooring measurement, quote-form, and floor-plan-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 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 "measure whole house — family out Jun 12–16" window or a "living room: sofa + piano stay; bedrooms cleared" inventory note is a booking you create; a service name such as hardwood install or vinyl measure is a label you configure. Neither is a documented default. Room-by-room, furniture-inventory, sleep-elsewhere-week, or floor-plan-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 "out Jun 12–16 + piano stays + floor plan photo" next to a named homeowner is still a calendar that answers when the house will be empty enough for a whole-house measure. 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. | Flooring measurement 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. Room-by-room, furniture-inventory, sleep-elsewhere-week, measurement-notes, property-address, contact-name, phone, or email questions are fields you add; they are not documented defaults. Optional floor-plan-photo uploads are files you accept; that file type is not a documented default. A furniture-inventory answer is a stored list, not proof rooms were emptied. A sleep-elsewhere week is a stored schedule, not proof anyone left. A flooring form is not proof anyone measured or installed. 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 furniture-inventory row sits after a quote that never happened is not a documented default of the plugin. | Furniture-inventory and sleep-elsewhere answers stored in WordPress; optional floor-plan-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 floor-plan photo or room sketch is a file you accept; that file type is not a documented default. An uploaded floor-plan photo is a stored file, not a vacancy 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 floor-plan-photo file sits after a quote that never happened is not a documented default of the plugin. | Floor-plan-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. Room-by-room, furniture-inventory, sleep-elsewhere-week, floor-plan-photo, or measurement-notes fields often depend on the fields you configure. A furniture-inventory answer is a stored list, not proof rooms were emptied. A sleep-elsewhere week is a stored schedule, not proof anyone left. A flooring booking is not proof anyone measured or installed. A page request is not proof anyone booked. The page URL can say flooring even when no form is submitted. Ask your web vendor who can open entries and uploads, whether floor-plan 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 vacancy risk, insurance coverage, or install 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
- WordPress booking plugin privacy
- WordPress forms privacy
- WordPress payment gateway privacy
- All privacy guides
/wp-flooring-plugin-privacy