Radon testing plugin privacy

The result that stigmatizes the parcel and dates what you knew before the disclosure form asked

A radon test can look like a kit and a number. It is also a parcel record: every reading and retest date sits next to the address, showing what the owner knew and when — before any disclosure form asked. A mitigation quote maps the sub-slab, the sump, and the foundation's weak points. The house gets a stigma score that can outlive every owner who tested. Reading, retest-date, sub-slab-map, sump-note, foundation-note, and mitigation-quote fields are configured, not documented defaults. Optional lab PDFs or foundation photos go in the site uploads folder. A test booking is not proof a reading was taken. A stored pCi/L figure is a form answer, not a verified lab result. A page request is not proof anyone ordered a test. The page URL can say radon testing 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 account pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a disclosure-law claim, a health-risk claim, a real-estate-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 test bookings, result intakes, and page tags go

Test bookings and result forms handled on your WordPress site

Check which reading, retest-date, sub-slab-map, sump-note, foundation-note, or mitigation-quote fields you enable, who can open form entries and bookings, where uploaded lab PDFs 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 test. Notification emails can also copy the same reading and retest date off-site. One table can name the parcel, the pCi/L figure, the retest history, and the mitigation map next to an address, even when the kit never ships. Ask your web vendor not to collect a numeric result next to an address on the first public form, not to store retest dates next to mitigation quotes in one open submissions list, and to purge unused test bookings after the date passes. A privacy-policy page does not by itself limit who can export a customer list. A stored booking is not proof a reading was taken.

Page tags handled by a vendor

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

Radon-testing booking, result-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 radon-lab or mitigation CAD 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 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 radon test or mitigation visit is a booking you create; a service name such as short-term test, continuous monitor, or mitigation quote is a label you configure. Neither is a documented default. Reading, retest-date, sub-slab-map, sump-note, foundation-note, or mitigation-quote questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked test is not proof a reading was taken, and a stored pCi/L figure is not a verified lab result. Cancelling or missing the slot later does not erase the reading, retest date, sump note, or mitigation quote already stored next to an address, and does not unsend a confirmation email already delivered. How long that row sits after a booking that never became a test 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.

Test bookings, custom intake fields, and automatic confirmation emails 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. Reading, retest-date, sub-slab-map, sump-note, foundation-note, or mitigation-quote questions are fields you add; they are not documented defaults. A lab PDF or foundation photo is a file you accept; that file type is not a documented default. A test request is not proof a reading was taken. A stored pCi/L figure is a form answer, not a verified lab result. A mitigation quote is a stored number, not proof work was done. 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 an account row sits after a request that never became a test is not a documented default of the plugin.

Account and result-intake 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 reading, retest-date, sub-slab-map, or mitigation-quote field was sent. A page request from this script is not proof anyone ordered a test. The page URL can say radon testing even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and account pages. Keep marketing tags off those pages if you do not want that page request. A tagged radon page can re-confirm testing interest next to a stored address and reading; this row does not claim a test from that request.

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. Reading, retest-date, sub-slab-map, sump-note, foundation-note, or mitigation-quote fields often depend on the fields you configure. A test booking is not proof a reading was taken. A stored pCi/L figure is a form answer, not a verified lab result. A marketing-tag page request is not proof anyone ordered a test. The page URL can say radon testing even when no form is submitted. The reading and the retest date can sit after the kit never ships. This page is about a parcel result that dates what you knew, not a mold-testing discloseable booking fact and not a well-drilling site survey. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or account page, and how long records and backups are kept. A "tested home" 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 duties, health-risk claims, or real-estate outcomes. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and account pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-radon-testing-plugin-privacy