Appliance repair plugin privacy

The booking that asks when you'll be home — and writes down the garage code

An appliance-repair booking's central question is the one burglars ask: "when will you be home?" The form stores your answer as a confirmed four-hour window, then adds the access note for when you're not — "garage code 4471, washer's in the basement" — typed into a free-text field nobody audits. Model and serial numbers quietly date your purchases and your kitchen's worth. It's the most routine form on this site, which is exactly why no one has ever asked where those access notes go. The shop's WordPress keeps the when-home window, the access note, and the model/serial inventory long after the repair closes. Those fields are configured, not documented defaults. A booking is a service appointment, not proof of entry. An access note is a stored service instruction, not proof anyone used a code. A model/serial answer is an inventory field, not a valuation. A page request is not proof anyone booked a repair. The page URL can say appliance repair even when no form is submitted. Ask what happens to the when-home window, the access note, the model and serial numbers, and any photo of the unit after the repair closes — the when-home-plus-access row that answered when someone will be home outlives the ticket. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a home-security-advice claim, a burglary-prevention claim, an appliance-safety-standards claim, a repair-licensing claim, a warranty-law claim, a technician-background-check claim, or a GDPR or other compliance assessment.

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 booking intakes, service appointments, and page tags go

Intakes and bookings on your WordPress site

Check which when-home-window, access-note, model, serial-number, or photo-of-the-unit fields you enable, who can open form entries and service bookings, which inboxes receive copies, and how long records, emails, and backups are kept after the repair closes — when the when-home-plus-access row still holds when someone will be home and how to get in. Notification emails can also copy those fields off-site. One table can list every four-hour window next to a garage-code note, a model/serial inventory, and a photo of the unit. Ask your web vendor not to keep access notes next to when-home windows and address rows in one open submissions list longer than operations need, and to purge those fields when a ticket closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not proof of entry. An access note is not proof anyone used a code.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the appliance-repair booking page. That page request can reach a vendor host before anyone submits. The page URL can say appliance repair even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. An "appliance repair privacy" badge is not a verified storage path.

Appliance-repair-booking, service-appointment, 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 appliance-dealer / field-service SaaS tools 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. A when-home four-hour window or a "washer repair — home 9-1, garage code 4471" access note is a booking you create; a service name such as appliance repair or washer service is a label you configure. Neither is a documented default. When-home-window, access-note, model, serial-number, or photo-of-the-unit questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof of entry — and a CSV export of "home 9-1 + garage code 4471 + washer SN… + basement" next to a named homeowner is still a calendar that answers when someone will be home under one service visit. 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.

Appliance-repair service 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. When-home-window, access-note, model, serial-number, or photo-of-the-unit fields are fields you add; they are not documented defaults. Completing the form can store a confirmed four-hour when-home window next to an access note ("garage code 4471, washer's in the basement"), a model and serial inventory that dates the kitchen's worth, and a photo of the unit — typed once so the tech does not have to re-ask when someone will be home, into the same tables as an appliance-repair label. An access note is a stored service instruction, not proof anyone used a code. A booking request is a service appointment, not proof of entry — and a staff login can open "home 9-1 + garage code 4471 + washer SN…" next to every other access-note booking long after the repair closes. 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.

When-home and access answers stored in WordPress; optional unit-photo uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
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 a when-home-window, access-note, model, serial-number, or photo-of-the-unit field was sent. A page request from this script is not proof anyone booked a repair. The page URL can say appliance repair even when no form is submitted. Consent timing has not been tested. Review which tags you enable on appliance-repair booking pages.

Marketing tags handled through Meta, Google, or other configured platformsconnect.facebook.netNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. When-home-window, access-note, model, serial-number, or photo-of-the-unit fields often depend on the fields you configure. A booking is a service appointment, not proof of entry. An access note is a stored service instruction, not proof anyone used a code. A model/serial answer is an inventory field, not a valuation. A marketing-tag page request is not proof anyone booked a repair. The page URL can say appliance repair even when no form is submitted. The when-home-plus-access row that holds when someone will be home and how to get in — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that when-home-and-access stack, not an auto-repair vehicle path, a computer-repair device drop-off, a house-cleaning recurring-access path, a pool-service standing gate-code path, or a home-inspection one-time buyer-access intake. Ask your web vendor who can open entries, whether a marketing tag loads on the booking page, and how long records and backups are kept. An "appliance repair privacy" or "field-service compliant" badge is not a verified storage path. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess home-security advice, burglary prevention, appliance safety standards, repair licensing, warranty law, or technician background checks. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking pages, and backups.

Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-appliance-repair-plugin-privacy