Chimney sweep plugin privacy
Where your chimney photos and service records go
If your chimney-sweep form collects home addresses, access notes, photos, or condition reports, check where those records go and who can open them. This guide compares three plugins using public documentation. Review email copies, exports, and backups as well as WordPress entries.
Documentation review only. Consent timing, access controls, and retention have not been tested. This is not a legal or compliance assessment.
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 sweep bookings, condition reports, and page tags go
Bookings and reports on your WordPress site
Check which address, access-note, photo, or condition-report fields you enable, who can open form entries and sweep bookings, which inboxes receive copies, and how long records, emails, and backups are kept. Notification emails can also copy those fields off-site. A stored sweep booking is not proof anyone was home or that a flue was inspected. A photo or condition answer is not a verified certification.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the booking or report page. That page request can reach a vendor host before anyone submits. The page URL can say chimney sweep even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and report pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "chimney sweep privacy" badge is not a verified storage path.
Chimney-sweep booking, condition-report, and marketing-tag 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 chimney-sweep SaaS tools 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 service window or annual recert slot is a booking you create; a service name such as flue inspection or creosote sweep is a label you configure. Neither is a documented default. Address, access-note, home-window, interior-photo, or condition-report questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof anyone was home or that a flue was inspected. 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. | Chimney-sweep 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. Address, access-note, home-window, interior-photo, or condition-report fields are fields you add; they are not documented defaults. A photo or condition answer is a form answer or uploaded file, not a verified certification. A sweep booking is a calendar row, not proof anyone was home. Notification emails can copy field values and files off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | Address, access, photo, and condition answers stored in WordPress; optional photos in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| PixelYourSite – Your smart PIXEL (TAG) & API Manager Documented pixel and tag manager (plugin version 11.4.2.1). When a Meta Pixel ID is saved, version 11.4.2.1 dist/scripts/public.js loads https://connect.facebook.net/en_US/fbevents.js. A noscript image uses https://www.facebook.com/tr. Google Analytics 4, Google Tag Manager, and Head and Footer scripts load only when you enable them. Automated events include form submissions; those events do not by themselves prove that an address, interior-photo, or condition-report field was sent. A page request from this script is not proof anyone booked a sweep. The page URL can say chimney sweep even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and report pages. | Marketing tags handled through Meta, Google, or other configured platforms | connect.facebook.net | Not assessed | Not tested |
|
What this table does and does not prove
These examples depend on the fields and integrations you enable. Review who can open entries and files, which inboxes receive copies, and how long records and backups remain. This guide summarizes plugin documentation; it does not test your site's storage or access controls.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-chimney-sweep-plugin-privacy