Roofing plugin privacy

The quote form that announces whose house is open to the sky

A roofing company's quote page can look like a contact form and an estimate booking. The same form often asks name and phone, street address, whether a tarp is currently on the roof, an insurance claim number, the storm date, uploaded roof photos of the weakest spots, and a notes box for deductibles and whether they can afford the repair, and stores those answers next to a name for the life of the form table. Those fields are configured, not documented defaults. Before the crew arrives, the tarp checkbox is a dated, addressed statement that this house is open to the sky right now. The claim number sits next to the street address. The storm-date field timestamps the damage. Uploaded roof photos document exactly where the house is weakest. The notes box attaches a stranger's finances to a pin on a map. An estimate booking is a calendar row, not proof a roof needs repair. A tarp checkbox is the homeowner's disclosure, not a verified condition. A claim number is an identifier the homeowner typed, not a verified claim file. A storm-date answer is a date field, not a weather record. An uploaded roof photo is a client document, not proof of damage. A deductible or affordability note is the homeowner's account, not a financial statement. A page request is not proof anyone has storm damage. The page URL can say roofing even when no form is submitted. Ask what happens to the tarp answer and the roof photo after the estimate closes — the quote form that announces whose house is open to the sky outlives the first site visit. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the quote page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a storm-damage or insurance-claim or repair-outcome 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 estimate bookings, storm-damage quotes, and page tags go

Quotes and bookings on your WordPress site

Check which tarp, claim-number, storm-date, address, roof-photo, deductible, or affordability fields you enable, who can open form entries and estimate bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a booking closes — when the quote form announces whose house is open to the sky. Notification emails can also copy those fields off-site. One table can list every tarp checkbox a homeowner typed next to an estimate slot and a roof-photo upload. Ask your web vendor not to keep roof photos next to tarp answers and claim numbers in one open submissions list longer than operations need, and to purge booking rows when the quote is declined or closed. A privacy-policy page does not by itself limit who can open a submissions list. A stored estimate booking is not proof a roof needs repair. A roof-photo upload is not proof of damage.

Page tags handled by a vendor

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

Estimate booking, storm-damage quote, 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 roofing CRM SaaS platforms 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. An estimate or storm-damage inspect booking is a booking you create; a service name such as free estimate, storm inspection, or tarp install is a label you configure. Neither is a documented default. Street-address, tarp-currently-on-roof, insurance-claim-number, storm-date, or affordability questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof a roof needs repair — and a CSV export of estimate slots next to a tarp checkbox and a named street address is still a booking row after someone asked about a quote. 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.

Roof estimate and storm-damage inspect 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. Street-address, tarp-currently-on-roof, insurance-claim-number, storm-date, deductible, or affordability questions are fields you add; they are not documented defaults. Completing the form can store a tarp checkbox next to a street address, an insurance claim number, a storm date, an affordability note, and optional roof-photo uploads — typed once by a homeowner into the same tables as a newsletter signup. An estimate booking is a calendar row, not proof a roof needs repair. A tarp checkbox is the homeowner's disclosure, not a verified condition. A claim number is an identifier the homeowner typed, not a verified claim file. A storm-date answer is a date field, not a weather record. An uploaded roof photo is a client document in uploads/forminator, not proof of damage. A deductible or affordability note is the homeowner's account, not a financial statement. A staff login can open the tarp answer next to the Tuesday 10am estimate slot. 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.

Storm-damage quote entries stored in WordPress; optional roof-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 tarp, claim-number, storm-date, address, roof-photo, deductible, or affordability field was sent. A page request from this script is not proof anyone has storm damage. The page URL can say roofing even when no form is submitted. Consent timing has not been tested. Review which tags you enable on quote and estimate-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. Tarp, claim-number, storm-date, address, roof-photo, deductible, or affordability fields often depend on the fields you configure. An estimate booking is a calendar row, not proof a roof needs repair. A tarp checkbox is the homeowner's disclosure, not a verified condition. A claim number is an identifier the homeowner typed, not a verified claim file. A storm-date answer is a date field, not a weather record. An uploaded roof photo is a client document, not proof of damage. A deductible or affordability note is the homeowner's account, not a financial statement. A marketing-tag page request is not proof anyone has storm damage. The page URL can say roofing even when no form is submitted. The quote form that announces whose house is open to the sky — that is a storage path next to names and phones, not a feature these plugins claim. This page is about that storm-damage quote intake, not a public-adjuster claim advocacy form, a restoration mitigation form, a home-inspection property-condition form, or a solar-installer roof-adjacent install form. Ask your web vendor who can open entries, whether a marketing tag loads on the quote page, and how long records and backups are kept. An "approved claim" 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 storm damage, insurance claims, or repair outcomes. Review stored records, bookings, connected services, exports, notification emails, marketing tags on quote pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-roofing-plugin-privacy