HVAC repair plugin privacy
The maintenance plan that knows which rooms you sleep in and when the house is empty
An HVAC WordPress stack is not only a filter calendar — it is often an occupancy study. Every confirmed booking can store smart-thermostat schedules pasted into the problem description, which rooms stay at 72, snowbird dates that empty the house for a season, the autopay card on the maintenance plan, and the lockbox code for twice-a-year access. Filter-subscription forms can keep that pattern current forever. A page request is not proof anyone booked. A thermostat schedule is a stored note, not proof anyone was home. A lockbox code is stored text, not proof anyone entered. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where uploaded photos land, which inboxes receive copies, and how long past tickets, files, and backups are kept.
Documentation review only. This is not legal advice, an HVAC-performance claim, a burglary-risk claim, a payment-security assessment, a GDPR or other compliance assessment, or a judgment about HVAC 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 thermostat schedules, lockbox codes, and maintenance bookings go
Entries, bookings, and uploads on your WordPress site
Check which thermostat-schedule, room-setpoint, snowbird-date, lockbox, autopay, or filter-subscription fields you enable, who can open form entries and maintenance bookings, where uploaded equipment photos live in the uploads folder, which inboxes receive copies, and how long past tickets, files, and backups are kept after a visit that never happened. Notification emails can also copy the same address, schedules, and access notes 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 maintenance calendar. A "NATE-certified" badge is not a verified storage path.
HVAC maintenance booking, thermostat-note, and lockbox 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 HVAC 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 twice-yearly filter visit or a "lockbox 9921 — snowbirds Nov-Mar" access note is a booking you create; a service name such as HVAC repair or maintenance plan is a label you configure. Neither is a documented default. Thermostat-schedule, room-setpoint, snowbird-date, lockbox, or filter-subscription questions are custom fields you add; they are not documented defaults. A booking is a calendar row, not proof of entry — and a CSV export of "lockbox 9921 + nursery at 72 + empty Nov-Mar" next to a named homeowner is still a calendar that answers when the house is empty for planned access. 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. | HVAC maintenance 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. Thermostat-schedule, room-setpoint, snowbird-date, lockbox, autopay, filter-subscription, property-address, owner-name, phone, or email questions are fields you add; they are not documented defaults. Optional equipment-photo uploads are files you accept; that file type is not a documented default. A thermostat schedule is a stored note, not proof anyone was home. A lockbox code is stored text, not proof anyone entered. An HVAC form is not proof anyone serviced the system. 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 lockbox note sits after a visit that never happened is not a documented default of the plugin. | Thermostat and lockbox answers stored in WordPress; optional equipment-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. An equipment photo or thermostat screenshot is a file you accept; that file type is not a documented default. An uploaded photo is a stored file, not proof of occupancy. 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 an equipment-photo file sits after a visit that never happened is not a documented default of the plugin. | Equipment-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. Thermostat-schedule, room-setpoint, snowbird-date, lockbox, autopay, or filter-subscription fields often depend on the fields you configure. A thermostat schedule is a stored note, not proof anyone was home. A lockbox code is stored text, not proof anyone entered. An HVAC booking is not proof anyone serviced the system. A page request is not proof anyone booked. The page URL can say HVAC even when no form is submitted. Ask your web vendor who can open entries and uploads, whether equipment 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 HVAC performance, payment security, or 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
- WordPress booking plugin privacy
- WordPress forms privacy
- WordPress payment gateway privacy
- All privacy guides
/wp-hvac-repair-plugin-privacy