Handyman plugin privacy
The job list that inventories everything broken in your house
The request form is a self-reported defect dossier — the loose railing, the water stain, the outlet that sparks — dated, photographed, and tied to your address. That list is exactly what a landlord dispute, an insurance adjuster, or a slip-and-fall lawyer wants, and the customer wrote it themselves. Those fields are configured, not documented defaults. A handyman booking is a calendar row, not proof anyone has a defective house or that a defect is accurate. A defect or photo answer is a form answer or uploaded file, not a verified hazard. A page request is not proof anyone booked a handyman. The page URL can say handyman even when no form is submitted. Ask what happens to the service address, the defect list, the photos, and the access notes after a job closes — the stack that inventoried everything broken outlives the punch list. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the quote or booking page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a contractor-licensing-law claim, a landlord-tenant-dispute-discovery claim, an insurer-underwriting claim, a premises-liability-advice 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 job quotes, bookings, and page tags go
Quotes and bookings on your WordPress site
Check which address, defect-description, photo, access-note, preferred-date, or intake-upload fields you enable, who can open form entries and job bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a job closes — when the address-plus-defect-plus-photo row still holds the self-reported defect dossier. Notification emails can also copy those fields off-site. One table can list every "12 Oak St · loose railing photo · water stain ceiling · outlet sparks · dated 3/12" stack next to a customer name. Ask your web vendor not to keep defect lists and photos next to home addresses in one open submissions list longer than operations need, and to purge those fields when a job closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored handyman booking is not proof anyone has a defective house or that a defect is accurate. A defect or photo answer is not a verified hazard.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the quote or booking page. That page request can reach a vendor host before anyone submits. The page URL can say handyman even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off quote and booking pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "handyman privacy" badge is not a verified storage path.
Handyman quote, booking, 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 handyman 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 Tuesday railing-fix window or an outlet-check slot is a booking you create; a service name such as odd jobs or punch-list is a label you configure. Neither is a documented default. Address, defect-description, photo, access-note, or preferred-date 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 has a defective house or that a defect is accurate — and a CSV export of "12 Oak St · loose railing photo · water stain ceiling · outlet sparks · dated 3/12" next to a customer name is still a calendar that pairs a self-reported defect dossier with a home address. 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. | Handyman job 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, defect-description, photo, access-note, or preferred-date fields are fields you add; they are not documented defaults. Completing the form can store an address-plus-defect-plus-photo stack ("12 Oak St · loose railing photo · water stain ceiling · outlet sparks · dated 3/12") — typed once so a handyman can quote and schedule, into the same tables as a "handyman" label. A defect or photo answer is a form answer or uploaded file, not a verified hazard. A handyman booking is a calendar row, not proof anyone has a defective house — and a staff login can open "Jordan, 12 Oak St, railing.jpg, water-stain.jpg, outlet sparks, 3/12" next to everyone else's resume. 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, defect, and photo 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, defect-description, or photo field was sent. A page request from this script is not proof anyone booked a handyman. The page URL can say handyman even when no form is submitted. Consent timing has not been tested. Review which tags you enable on quote and booking 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. Address, defect-description, photo, access-note, or preferred-date fields often depend on the fields you configure. A handyman booking is a calendar row, not proof anyone has a defective house or that a defect is accurate. A defect or photo answer is a form answer or uploaded file, not a verified hazard. A marketing-tag page request is not proof anyone booked a handyman. The page URL can say handyman even when no form is submitted. The address-plus-defect-plus-photo row that inventories everything broken — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that self-reported defect dossier, not an appliance-repair access-code visit, a roofing open-to-the-sky file, a junk-removal shame-photo haul, a chimney-sweep living-room photo set, or a reputation-management self-compiled oppo file. Ask your web vendor who can open entries, whether a marketing tag loads on the quote or booking page, and how long records and backups are kept. A "handyman privacy" or "contractor 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 contractor-licensing law, landlord-tenant dispute discovery, insurer underwriting, or premises-liability advice. Review stored records, bookings, connected services, exports, notification emails, marketing tags on quote and booking pages, and backups.
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-handyman-plugin-privacy