House cleaning plugin privacy
The client notes that brief a rotating stranger on your house every week
A house-cleaning booking page can look like a calendar and a contact form. The same form often asks how to enter ("key under the planter", "garage code 4471", "alarm: disarm then rearm"), which pets are home, which rooms to skip, and what kind of clean it is — plus before-photo uploads for deep-clean quotes — and stores those answers next to the customer's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a weekly Tuesday slot chosen because the family is out, next to an alarm code and "don't go in the back bedroom" — standing instructions briefed to a rotating roster of workers, typed once into a vendor table next to a marketing pixel. A recurring slot is a plan, not proof the house stands empty. An entry-method field is a configured convenience, not evidence a key was ever left out. A move-out booking is a date on a calendar, not an eviction or a death. A do-not-enter note is an instruction the customer chose to write, not a finding about the room. A page request is not proof anyone hired a cleaner. The page URL can say house-cleaning even when no form is submitted. Ask what happens to the entry-method answer and the alarm-or-gate-code field after the visit — the client notes brief a rotating stranger on your house every week, and the row outlives the clean. 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 bonding or insurance-law claim, an employment or labor-classification claim, a lock or alarm security-standards claim, or a GDPR or other 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 cleaning bookings, house-access notes, and page tags go
Bookings and notes on your WordPress site
Check which entry-method, alarm-or-gate-code, pets, rooms-to-skip, or booking-type fields you enable, who can open form entries and recurring cleaning bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the client notes brief a rotating stranger on your house every week. Notification emails can also copy those fields off-site. One table can list every Tuesday slot next to an entry method and an alarm code. Ask your web vendor not to keep alarm-or-gate-code next to entry-method in one open submissions list longer than operations need, and to purge intake rows when the booking ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not proof the house stands empty. An uploaded before photo is not a finding about the home.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the house-cleaning booking page. That page request can reach a vendor host before anyone submits. The page URL can say house-cleaning even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and quote pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "bonded and insured" badge is not a verified storage path.
Recurring cleaning, house-access intake, 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 cleaning-dispatch 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 recurring cleaning slot is a booking you create; a service name such as weekly tidy, biweekly deep clean, or move-out clean is a label you configure. Neither is a documented default. Entry-method, alarm-or-gate-code, pets, rooms-to-skip, or booking-type questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof the house stands empty — and a CSV export of Tuesday 10am slots next to an entry-method answer and an alarm-or-gate-code field is still a standing instruction for a rotating roster after the week the family was out. 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. | Recurring cleaning 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. Entry-method, alarm-or-gate-code, pets, rooms-to-skip, or booking-type questions are fields you add; they are not documented defaults. Completing the form can store an entry-method answer next to an alarm-or-gate-code field, a pets answer, a rooms-to-skip note, a booking type, and optional before-photo uploads — typed once as client notes that brief a rotating stranger on your house every week into the same tables as a newsletter signup. A recurring slot is a plan, not proof the house stands empty. An entry-method field is a configured convenience, not evidence a key was ever left out. A move-out booking is a date on a calendar, not an eviction or a death. A do-not-enter note is an instruction the customer chose to write, not a finding about the room — and a staff login can open "garage code 4471, alarm: disarm then rearm, skip the back bedroom" next to a before photo. 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. | House-access intake entries stored in WordPress; optional before-photo uploads 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 entry-method, alarm-or-gate-code, pets, rooms-to-skip, or booking-type field was sent. A page request from this script is not proof anyone hired a cleaner. The page URL can say house-cleaning even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and quote 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
This is a documentation review, not a test of your site. Entry-method, alarm-or-gate-code, pets, rooms-to-skip, or booking-type fields often depend on the fields you configure. A recurring slot is a plan, not proof the house stands empty. An entry-method field is a configured convenience, not evidence a key was ever left out. A move-out booking is a date on a calendar, not an eviction or a death. A do-not-enter note is an instruction the customer chose to write, not a finding about the room. A marketing-tag page request is not proof anyone hired a cleaner. The page URL can say house-cleaning even when no form is submitted. The client notes that brief a rotating stranger on your house every week — that is a storage path next to an alarm-or-gate-code field, not a feature these plugins claim. This page is about that standing house-access instruction, not a pet-sitting empty-house schedule, an alarm-company code vault, a self-storage gate code, a hoarding or crime-scene cleanup intake, or a home-care roster. 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. A "bonded and insured" 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 bonding or insurance law, employment or labor classification, or lock and alarm security standards. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking pages, and backups.
Documentation snapshot: Oct 14, 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-house-cleaning-plugin-privacy