Drug testing plugin privacy

The appointment that records the suspicion before the specimen exists

A drug-testing appointment can look like a booking and a contact form. The same form often asks employer account, reason-for-test (pre-employment, random, post-accident, reasonable-suspicion, return-to-duty), donor name and ID, panel type, results recipient, and deadline — plus chain-of-custody and authorization-form 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 employer suspected an employee before any specimen exists, typed by the donor under instruction, with the job as the price of declining. A booking is not a result. A reason-for-test answer is the orderer's label, not a finding about the donor. A post-accident test slot is a schedule entry, not fault. A page request is not proof anyone was tested. The page URL can say drug testing even when no form is submitted. Ask what happens to the reason-for-test field and the custody upload after the visit — the appointment records the suspicion before the specimen, and the row outlives the panel. 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 drug-testing-law claim, a DOT-regulation claim, an employment-law claim, a chain-of-custody-validity claim, a test-accuracy 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-slot bookings, compelled-appointment intakes, and page tags go

Intakes and bookings on your WordPress site

Check which employer-account, reason-for-test, donor-name-and-ID, panel-type, results-recipient, or deadline fields you enable, who can open form entries and test-slot bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the booking row is an accusation with a timestamp before any specimen exists. Notification emails can also copy those fields off-site. One table can list every donor whose reason-for-test was typed next to an employer name. Ask your web vendor not to keep custody forms next to reason-for-test answers in one open submissions list longer than operations need, and to purge intake rows when the panel 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 authorization form is not a finding about the donor.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the drug-testing appointment page. That page request can reach a vendor host before anyone submits. The page URL can say drug 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 screening" badge is not a verified storage path.

Test-slot, compelled-appointment 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 lab or employer-compliance 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. A test-slot booking is a booking you create; a service name such as drug-test panel or employer screening is a label you configure. Neither is a documented default. Employer-account, reason-for-test, donor-name-and-ID, panel-type, results-recipient, or deadline 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 donor name and a reasonable-suspicion reason is still a compelled-appointment row before any specimen exists. 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.

Drug-testing test-slot 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. Employer-account, reason-for-test, donor-name-and-ID, panel-type, results-recipient, or deadline questions are fields you add; they are not documented defaults. Completing the form can store an employer name next to a reason-for-test label such as reasonable-suspicion or post-accident, a donor ID, a panel type, a results recipient, a deadline, and optional chain-of-custody or authorization-form uploads — typed by the donor under instruction, ordered by someone else. A booking is not a result. A reason-for-test answer is the orderer's label, not a finding about the donor. A post-accident test slot is a schedule entry, not fault — and a staff login can open the uploaded authorization form next to the reason 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.

Compelled-appointment intake entries stored in WordPress; optional chain-of-custody and authorization-form 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 an employer-account, reason-for-test, donor-name-and-ID, panel-type, results-recipient, or deadline field was sent. A page request from this script is not proof anyone was tested. The page URL can say drug 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. Employer-account, reason-for-test, donor-name-and-ID, panel-type, results-recipient, or deadline fields often depend on the fields you configure. A booking is not a result. A reason-for-test answer is the orderer's label, not a finding about the donor. A post-accident test slot is a schedule entry, not fault. A marketing-tag page request is not proof anyone was tested. The page URL can say drug testing even when no form is submitted. The booking row is an accusation with a timestamp before any specimen exists — that is a storage path next to a name, not a feature these plugins claim. This page is about that compelled-appointment intake, not a workers-comp attorney intake, a sober-living signup, a DUI-school enrollment, an addiction-treatment form, an ignition-interlock order, or a security-guard background check. 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 screening" 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 drug-testing law, DOT regulation, employment law, chain-of-custody validity, or test accuracy. 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-drug-testing-plugin-privacy