Central vacuum plugin privacy

The whole-house install quote that keeps a map of every room you live in

A central-vacuum WordPress stack is not only an install calendar — it is often a room-by-room map of every inlet you plan to put in the walls. Every confirmed whole-house quote can store room counts, inlet locations, and a floor-plan sketch, next to a name and address in a forms table. A floor-plan upload can sit beside those notes in the uploads folder. A page request is not proof anyone booked. A room-map note is stored text, not proof anyone vacuumed. A install 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 cleaning-outcome claim, an insurance claim, an HVAC claim, a flooring claim, a GDPR or other compliance assessment, or a judgment about central-vacuum installers.

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 room maps, install bookings, and floor plans go

Entries, bookings, and uploads on your WordPress site

Check which room-map, inlet-location, floor-plan, install-window, or access-notes fields you enable, who can open form entries and install bookings, where uploaded floor plans live in the uploads folder, which inboxes receive copies, and how long past quotes, files, and backups are kept after an install that never happened. Notification emails can also copy the same address, room map, and plan 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 install calendar. A "central vacuum" badge is not a verified storage path.

Central-vacuum quote, install-booking, and floor-plan 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 central vacuum 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. An "install window Mon–Tue — 8 inlets; unit in garage" window or a "prefer hide hose in pantry" note is a booking you create; a service name such as new-build rough-in or retrofit is a label you configure. Neither is a documented default. Room-map, inlet-location, floor-plan, or install-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 an install — and a CSV export of "8 inlets + garage unit + floor plan" next to a named homeowner is still a calendar that maps every room you live in. 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.

Central-vacuum install and quote 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. room-map, inlet-location, floor-plan, install-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 install window is a stored schedule, not proof the crew arrived. A room-map note is stored text, not proof anyone vacuumed. A central vacuum form is not proof anyone 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 row sits after an install that never happened is not a documented default of the plugin.

Room-map and inlet answers stored in WordPress; optional floor-plan 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 floor-plan sketch is a file you accept; that file type is not a documented default. An uploaded file is a stored file, not a home-layout 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 an install that never happened is not a documented default of the plugin.

Floor-plan 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. room-map, inlet-location, floor-plan, install-window fields often depend on the fields you configure. A room-map note is stored text, not proof anyone vacuumed. A install window is a stored schedule, not proof the crew arrived. A central vacuum booking is not proof anyone installed. A page request is not proof anyone booked. The page URL can say central vacuum 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 cleaning outcomes, insurance coverage, HVAC work, or flooring installs. 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

Scan your site for third-party requests

/wp-central-vacuum-plugin-privacy