Electrician plugin privacy
The panel photo that maps every circuit in the house to what it powers
An electrician WordPress stack is not only a service calendar — it is often a wiring map of the home. Every confirmed booking can store panel photos, which circuit feeds the safe or the server closet, what trips when, and the access notes to reach it all (garage code, crawlspace entry). Unusual-load questions can quietly document what draws power in which room, and insurance or permit follow-ups can staple an electrical history to a name and address in a forms table. A page request is not proof anyone booked. A panel photo is a stored file, not a utility diagram claim. An access note is stored text, not proof anyone entered. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where panel 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 electrical-code claim, a utility claim, a burglary-risk claim, a GDPR or other compliance assessment, or a judgment about electricians.
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 panel photos, circuit notes, and service bookings go
Entries, bookings, and uploads on your WordPress site
Check which panel-photo, circuit-label, trip-history, unusual-load, garage-code, crawlspace, or permit fields you enable, who can open form entries and service bookings, where uploaded panel photos live in the uploads folder, which inboxes receive copies, and how long past tickets, files, and backups are kept after a call that never happened. Notification emails can also copy the same address, circuit notes, and photo links 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 service calendar. A "licensed electrician" badge is not a verified storage path.
Electrician booking, panel-photo, and circuit-note 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 electrician 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 panel-service window or a "safe circuit / server closet — garage code 4412" access note is a booking you create; a service name such as electrician or panel upgrade is a label you configure. Neither is a documented default. Panel-photo, circuit-label, trip-history, unusual-load, garage-code, or crawlspace questions are custom fields you add (textarea, select, input, checkbox, or file); they are not documented defaults. A booking is a calendar row, not proof of entry — and a CSV export of "garage code 4412 + panel photo + circuit that feeds the safe" next to a named homeowner is still a calendar that answers when someone will be home for an electrical 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. | Electrician service 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. Panel-photo, circuit-label, trip-history, unusual-load, garage-code, crawlspace, permit, property-address, owner-name, phone, or email questions are fields you add; they are not documented defaults. Optional panel-photo uploads are files you accept; that file type is not a documented default. A panel photo is a stored file, not a utility diagram claim. An access note is stored text, not proof anyone entered. An electrician form is not proof anyone worked the panel. 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 panel photo sits after a call that never happened is not a documented default of the plugin. | Panel and circuit answers stored in WordPress; optional panel-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. A panel photo or permit PDF is a file you accept; that file type is not a documented default. An uploaded panel photo is a stored file, not a utility diagram claim. 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 a panel-photo file sits after a call that never happened is not a documented default of the plugin. | Panel-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. Panel-photo, circuit-label, trip-history, unusual-load, garage-code, crawlspace, or permit fields often depend on the fields you configure. A panel photo is a stored file, not a utility diagram claim. An access note is stored text, not proof anyone entered. An electrician booking is not proof anyone worked on the panel. A page request is not proof anyone booked. The page URL can say electrician even when no form is submitted. Ask your web vendor who can open entries and uploads, whether panel 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 electrical code, utility records, 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-electrician-plugin-privacy