Mold testing plugin privacy

The booking that creates the fact you may have to disclose

A mold-testing appointment can look like a booking and a contact form. The same form often asks property address, reason-for-test, symptom-or-smell, rooms affected, occupancy, and prior-test history — plus photo and prior-report uploads — and stores those answers next to a name for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can record that an owner went looking for mold, radon, or meth residue at an address before any lab result exists, typed by the owner into a vendor table next to a marketing pixel. Before the form, the owner can honestly not know; after the row exists, knew or should have known has a timestamp. A test booking is not a result. A reason-for-test answer is the owner's worry, not a finding about the property. A meth-residue test request implies nothing proven about previous occupants — they are third parties who never consented to being the reason. A page request is not proof any property has a problem. The page URL can say mold testing even when no form is submitted. Ask what happens to the reason-for-test field and the photo upload after the visit — the booking creates the fact you may have to disclose, and the row outlives the sample. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the appointment page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a disclosure-law claim, a seller-obligation claim, a lab-accuracy claim, a remediation-efficacy claim, a health-effects claim, a property-value 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 inspection bookings, disclosure-liability intakes, and page tags go

Intakes and bookings on your WordPress site

Check which property-address, reason-for-test, symptom-or-smell, rooms-affected, occupancy, or prior-test-history fields you enable, who can open form entries and inspection bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the booking creates the fact the owner may have to disclose. Notification emails can also copy those fields off-site. One table can list every address whose reason-for-test was typed next to a symptom note. Ask your web vendor not to keep photos next to reason-for-test answers in one open submissions list longer than operations need, and to purge intake rows when the sample is closed. A privacy-policy page does not by itself limit who can open a submissions list. A stored appointment is not a result. An uploaded prior report is not a finding about the property.

Page tags handled by a vendor

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

Inspection, disclosure-liability 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 environmental-lab 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 inspection or sampling booking is a booking you create; a service name such as mold inspection, radon test, or meth-residue sampling is a label you configure. Neither is a documented default. Property-address, reason-for-test, symptom-or-smell, rooms-affected, occupancy, or prior-test-history questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not a result — and a CSV export of visits next to a property address and a musty-smell reason is still a disclosure-liability row after the owner went looking. 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.

Mold-testing inspection 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. Property-address, reason-for-test, symptom-or-smell, rooms-affected, occupancy, or prior-test-history questions are fields you add; they are not documented defaults. Completing the form can store a property address next to a reason-for-test label, a symptom-or-smell answer, rooms affected, occupancy, prior-test history, and optional photo or prior-report uploads — typed by the owner who went looking. A test booking is not a result. A reason-for-test answer is the owner's worry, not a finding about the property. A meth-residue test request implies nothing proven about previous occupants — they never consented to being the reason — and a staff login can open the uploaded photo next to the address field. 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.

Disclosure-liability intake entries stored in WordPress; optional photo and prior-report 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 property-address, reason-for-test, symptom-or-smell, rooms-affected, occupancy, or prior-test-history field was sent. A page request from this script is not proof any property has a problem. The page URL can say mold testing even when no form is submitted. Consent timing has not been tested. Review which tags you enable on appointment and 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. Property-address, reason-for-test, symptom-or-smell, rooms-affected, occupancy, or prior-test-history fields often depend on the fields you configure. A test booking is not a result. A reason-for-test answer is the owner's worry, not a finding about the property. A meth-residue test request implies nothing proven about previous occupants — they never consented to being the reason. A marketing-tag page request is not proof any property has a problem. The page URL can say mold testing even when no form is submitted. The booking creates the fact you may have to disclose — that is a storage path next to an address, not a feature these plugins claim. This page is about that disclosure-liability intake, not a home-inspection defect list, a pest-control infestation mark, a restoration post-loss photo set, a biohazard-cleanup intake, or a hoarding-cleanup form. Ask your web vendor who can open entries, whether a marketing tag loads on the appointment page, and how long records and backups are kept. A "confidential inspection" 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 obligation, lab accuracy, remediation efficacy, health effects, or property value. Review stored records, bookings, connected services, exports, notification emails, marketing tags on appointment 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-mold-testing-plugin-privacy