Solar installer plugin privacy
The quote request that uploads a year of your life, one kilowatt-hour at a time
A solar installer's site can look like a calendar and a short quote form. The same form often asks for twelve months of usage, the utility provider, whether you own or rent, whether you want financing, and how old the roof is — and asks for a utility-bill PDF or roof photos — and stores those answers next to the owner's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a site-survey booking next to a year of kilowatt-hour readings, a utility account number on an uploaded bill, an own-or-rent answer paired with a financing-interest checkbox, and a marketing pixel — the quote request that uploads a year of your life, one kilowatt-hour at a time, typed once into a vendor table next to a newsletter signup. A quote request is an inquiry, not a contract or a credit application. A usage history is a record of the meter, not of who did what — but its pattern is readable either way. An uploaded bill is a stored client document carrying a live account number, not proof the installer reviewed it. An own-or-rent answer is the requester's statement, not a title record. A financing-interest checkbox is curiosity, not a credit pull. A page request is not proof anyone owns a roof. The page URL can say solar-installer even when no form is submitted. Ask what happens to the utility-bill PDFs and usage rows after the quote closes — the quietest field is the own-or-rent / financing-interest pair, a financing disclosure attached to a home's floor-level photographs. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the intake page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a claim about solar savings or payback, a net-metering or utility-law claim, a tax-credit-eligibility claim, an installer-licensing claim, a financing-terms claim, a claim about the firm's data-security practices, a provider-quality 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 site-survey bookings, utility-bill uploads, and page tags go
Bookings and notes on your WordPress site
Check which monthly-usage-or-bill, utility-provider, own-or-rent, financing-interest, or roof-age fields you enable, who can open form entries and site-survey or consultation bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a quote closes — when the quote request that uploads a year of your life, one kilowatt-hour at a time. Notification emails can also copy those fields off-site. One table can list every Saturday survey next to a utility-bill PDF and a roof-photo ZIP. Ask your web vendor not to keep utility-bill or roof-photo uploads next to plaintext usage and financing-interest rows in one open submissions list longer than operations need, and to purge intake rows when the quote closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not a contract. A usage history in a form table is not a behavioral profile the plugin claims to build.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the solar-installer site-survey or quote-intake page. That page request can reach a vendor host before anyone submits. The page URL can say solar-installer even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off site-survey, consultation, and solar-installer quote-intake pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "trusted solar partner" badge is not a verified storage path.
Site-survey / consultation booking, solar-installer quote 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 solar-quoting 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 Saturday site survey or a consultation slot is a booking you create; a service name such as site survey or solar consultation is a label you configure. Neither is a documented default. Monthly-usage-or-bill, utility-provider, own-or-rent, financing-interest, or roof-age questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is an inquiry, not a contract — and a CSV export of a site-survey row next to a utility-provider and a monthly-usage note is still a calendar that holds a year of meter readings beside a contact name. 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. | Site-survey and consultation 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. Monthly-usage-or-bill, utility-provider, own-or-rent, financing-interest, or roof-age fields are fields you add; they are not documented defaults. Completing the form can store twelve months of kilowatt-hour readings next to a utility provider, an own-or-rent answer, a financing-interest checkbox, a roof-age note, and optional utility-bill or roof-photo uploads — typed once as the quote request that uploads a year of your life, one kilowatt-hour at a time, into the same tables as a newsletter signup. A quote request is an inquiry, not a contract or a credit application. A usage history is a record of the meter, not of who did what — but its pattern is readable either way. An uploaded bill is a client document carrying a live account number, not proof the installer reviewed it — and a staff login can open "12-month usage PDF, Acme Power acct 774291, own, financing interest yes, roof ~18yr, south-facing photos.zip" next to everyone else's resume. An own-or-rent answer is the requester's statement, not a title record. A financing-interest checkbox is curiosity, not a credit pull. 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. | Solar-installer quote intake stored in WordPress; optional utility-bill and roof-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 a monthly-usage-or-bill, utility-provider, own-or-rent, financing-interest, or roof-age field was sent. A page request from this script is not proof anyone owns a roof. The page URL can say solar-installer even when no form is submitted. Consent timing has not been tested. Review which tags you enable on site-survey, consultation, and solar-installer quote-intake 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. Monthly-usage-or-bill, utility-provider, own-or-rent, financing-interest, or roof-age fields often depend on the fields you configure. A quote request is an inquiry, not a contract or a credit application. A usage history is a record of the meter, not of who did what — but its pattern is readable either way. An uploaded bill is a stored client document carrying a live account number, not proof the installer reviewed it. An own-or-rent answer is the requester's statement, not a title record. A financing-interest checkbox is curiosity, not a credit pull. A marketing-tag page request is not proof anyone owns a roof. The page URL can say solar-installer even when no form is submitted. The quote request that uploads a year of your life, one kilowatt-hour at a time — that is a storage path next to a utility-bill PDF, not a feature these plugins claim. This page is about that solar-installer quote intake, not an alarm-company home layout, a home-inspection defect list, or a reverse-mortgage equity form. Ask your web vendor who can open entries, whether a marketing tag loads on the intake page, and how long usage rows and backups are kept after the quote closes. A "trusted solar partner" 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 solar savings or payback, net-metering or utility law, tax-credit eligibility, installer licensing, financing terms, the firm's data-security practices, or provider quality. Review stored records, bookings, connected services, exports, notification emails, marketing tags on intake 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-solar-installer-plugin-privacy