Foundation repair plugin privacy
The crack photos that date what you knew before the disclosure form asked
A foundation-repair quote can date what you knew. A form can collect photos of the crack, your own words that it has been getting wider since spring, crawlspace access notes, the three bids you collected, and the cheap patch you chose instead of the real fix. That quote row can sit in a form plugin entries table any staffer can open. Crack-photo, crack-history, crawlspace-access, competing-bid, cheap-patch, declined-fix, property-address, owner-name, phone, and quote-date fields are configured, not documented defaults. Optional crack photos and bid files go in the site uploads folder. A quote request is not proof a structural defect exists. A crack photo is an upload, not proof of a structural defect. A crack-history note is a stored note, not proof the crack widened. A crawlspace-access field is a stored note, not proof of access. A competing-bid file is an upload, not proof of another quote. A cheap-patch or declined-fix note is a stored note, not proof they chose a cheaper patch. A property address is a stored location, not a verified residence. A quote date is a stored date, not proof of seller knowledge. A page request is not proof anyone booked. The page URL can say foundation repair even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on booking and quote pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a disclosure-law claim, a seller-fraud claim, a structural-engineering claim, a waterproofing-effectiveness claim, a mold claim, a tree-root-damage claim, a home-inspection claim, a public-adjuster 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 foundation-repair quotes, crack photos, and page tags go
Repair quotes and forms handled on your WordPress site
Check which crack-photo, crack-history, crawlspace-access, competing-bid, cheap-patch, declined-fix, property-address, owner-name, phone, or quote-date fields you enable, who can open form entries and bookings, where uploaded crack photos and bid files live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a request that never became a repair job. Notification emails can also copy the same crack photos, crack-history notes, crawlspace-access notes, competing-bid files, cheap-patch notes, property addresses, and owner names off-site. One table can name the house, the crack, and the cheap patch next to a phone, even when the repair is never sold. Ask your web vendor not to collect a crack photo next to a crack-history note and a property address on the first public form, not to store those competing bids next to the cheap-patch choice in one open submissions list, and to purge unused quotes after the date passes. A privacy-policy page does not by itself limit who can export a quote list or republish an upload. A stored quote is not proof a structural defect exists.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the foundation-repair booking or quote page. That page request can reach a vendor host before anyone submits. The page URL can say foundation repair even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and quote pages if you do not want that page request. A browser scan cannot inspect stored crack photos, crack-history notes, or competing-bid files. A "piering certified" badge is not a verified storage path.
Foundation-repair booking, 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 foundation-repair or structural-engineering software without a WordPress.org listing is 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). The listing documents automatic email notifications: customers get instant booking confirmations; staff get notified; templates can include booking information and custom fields; customers can confirm or cancel via a link in the email. WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A foundation-repair quote is a booking you create; a service name such as foundation repair, basement waterproofing, piering, or crack injection is a label you configure. Neither is a documented default. Crack-photo, crack-history, crawlspace-access, competing-bid, cheap-patch, declined-fix, property-address, owner-name, phone, or quote-date questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked quote is not proof a structural defect exists, and is not proof a repair was sold. Cancelling or missing the slot later does not erase the crack-history note, crawlspace-access note, competing-bid note, cheap-patch note, or property address already stored next to a name, and does not unsend a confirmation email already delivered. How long that row sits after a booking that never became a repair job is not a documented default of the plugin. 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. | Foundation-repair bookings, custom intake fields, and automatic confirmation emails 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. Crack-photo, crack-history, crawlspace-access, competing-bid, cheap-patch, declined-fix, property-address, owner-name, phone, or quote-date questions are fields you add; they are not documented defaults. A crack photo or competing-bid file is a file you accept; those file types are not documented defaults. A quote request is not proof a structural defect exists. A crack photo is an upload, not proof of a structural defect. A crack-history note is a stored note, not proof the crack widened. A crawlspace-access field is a stored note, not proof of access. A competing-bid file is an upload, not proof of another quote. A cheap-patch or declined-fix note is a stored note, not proof they chose a cheaper patch. A property address is a stored location, not a verified residence. A quote date is a stored date, not proof of seller knowledge. 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 quote sits after a request that never became a repair job is not a documented default of the plugin. | Quote and crack-photo entries stored in WordPress; file 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 crack-photo, crack-history, or competing-bid field was sent. A page request from this script is not proof anyone booked. The page URL can say foundation repair even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and quote pages. Keep marketing tags off those pages if you do not want that page request. A tagged quote page can re-confirm foundation-repair interest next to a stored address and files; this row does not claim a repair job from that request. | 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. Crack-photo, crack-history, crawlspace-access, competing-bid, cheap-patch, declined-fix, property-address, owner-name, phone, or quote-date fields often depend on the fields you configure. A quote request is not proof a structural defect exists. A crack photo is an upload, not proof of a structural defect. A crack-history note is a stored note, not proof the crack widened. A crawlspace-access field is a stored note, not proof of access. A competing-bid file is an upload, not proof of another quote. A cheap-patch or declined-fix note is a stored note, not proof they chose a cheaper patch. A property address is a stored location, not a verified residence. A quote date is a stored date, not proof of seller knowledge. A marketing-tag page request is not proof anyone booked. The page URL can say foundation repair even when no form is submitted. The crack photo, the history note, and the competing bids can sit after the quote never becomes a repair job. This page is about the crack photos that date what you knew before the disclosure form asked, not a mold-testing booking that creates the fact, not a tree-service hazard quote, not a home-inspection defect list, and not a public-adjuster loss inventory. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or quote page, and how long records and backups are kept. A portfolio 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 disclosure-law, seller-fraud, structural-engineering, waterproofing-effectiveness, mold, tree-root-damage, home-inspection, or public-adjuster claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and quote 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-foundation-repair-plugin-privacy