Restoration plugin privacy

Where does the quote form with photos of everything you lost go?

A restoration company's quote or estimate form is often filled out on the worst day of someone's year. It can collect the property address, the insurance claim number and policy details, photo uploads of the damaged interior — which double as a room-by-room inventory of what survived and is worth taking — and the fact that the house is uninhabitable and will sit vacant through the rebuild, typed into a local-first form or service-slot booking plugin. File fields can store those damage photos in the site uploads folder. The row can quietly outlive the rebuild. A marketing tag on the same estimate page can send a page request to a vendor host before anyone submits. A page request is not proof that photos or a claim number were collected. This sample reviews three plugins' documentation. Check which fields you collect, who can open bookings and entries, where uploaded files land, which tags load on the estimate page, and how long records, files, and backups are kept.

Documentation review only. This is not legal advice, an insurance-claim-outcome review, an adjuster-process assessment, a building-code review, 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 bookings, form entries, uploaded damage photos, email inboxes, staff permissions, vendor accounts, or backups.

Where estimate bookings, quote answers, and page tags go

Bookings and files handled on your WordPress site

Check which address, claim-number, policy, vacancy-window, or damage-photo fields you enable, who can open bookings and form entries, where uploaded damage photos live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after the rebuild. Notification emails can also copy the same answers off-site. Ask your web vendor not to keep claim numbers and room inventories after the job ends, and to purge quotes that never became paid work.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the restoration estimate or quote page. That page request can reach a vendor host before anyone submits. Review which tags you enable, account access, and retention there. Keep marketing tags off estimate pages if you do not want that page request. A browser scan cannot inspect stored form entries. A "secure client forms" badge is not a verified storage path.

Restoration 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 field-service software without a WordPress.org listing is outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Easy Appointments

Documented self-hosted appointment plugin marketed for clinics and service bookings (plugin version 4.0.3). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. Property address, insurance claim number, policy details, or vacancy / uninhabitable-window notes are custom fields you add (textarea, select, or input); they are not documented defaults. A service booking is not an insurance claim. Emails can include those custom fields. An optional GDPR setting can auto-remove customer data older than six months; that is not a default purge and does not guarantee job-length retention limits. Google Calendar, SMS, and payments are Pro. Google reCAPTCHA is optional. Public booking-form browser hosts are unverified.

Service-slot bookings and custom intake fields 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. Property address, claim-number, policy, or vacancy questions are fields you add; they are not documented defaults. Damage photos that inventory room contents are files you accept; they are not documented defaults. A quote entry is not an insurance claim. An uploaded damage photo is not an adjuster report. Entries can quietly outlive the rebuild in plugin tables. Notification emails can copy field values off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified.

Form entries stored in WordPress; file 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 claim number or damage photo was sent. A page request from this script on a restoration estimate or quote page is not proof that photos or a claim number were collected — and a pre-consent tag on that page can still treat restoration intent as an audience segment from the URL alone. Consent timing has not been tested. Review which tags you enable on estimate and quote 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. Property address, claim numbers, policy details, vacancy windows, or damage photos that inventory room contents often depend on the fields you configure. A quote request is not an insurance claim. An uploaded damage photo is not an adjuster report. A marketing-tag page request is not proof that photos or a claim number were collected. Ask your web vendor who can open bookings and entries, where uploaded files live, whether a marketing tag loads on the estimate page, and how long records and backups are kept. A "secure" or "client forms" 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 insurance-claim outcomes, adjuster processes, or building codes. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on estimate pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-restoration-plugin-privacy