TRT clinic plugin privacy
The intake where your bloodwork answers before you do
A TRT-clinic intake can look like a booking and a contact form. The same form often asks for the lab report itself — a total/free testosterone PDF authored by a laboratory — then ADAM-style symptom scores for libido, mood, energy, and erection quality, current medications, prior TRT history, and a pharmacy preference — and stores those answers next to a name for the life of the form table. Those fields are configured, not documented defaults. The lab authored the number; the patient uploaded it. One WordPress row can hold a signed clinical measurement the patient cannot soften, a stigmatized symptom self-assessment, and the marketing pixel on the page that brought him there — before any clinician reviews the labs. A consult booking is not a diagnosis. A symptom score is a self-rating, not a clinical finding. An uploaded lab PDF is a stored document, not proof the clinic read or verified it. A page request is not proof anyone sought treatment. The page URL can say TRT clinic even when no form is submitted. Ask what happens to the lab PDF and the symptom scores after the visit — the bloodwork answers before you do, and the row outlives the consult. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the intake page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a telehealth-prescribing-law claim, a controlled-substance or Schedule-III claim, an anti-aging-efficacy claim, a lab-accuracy claim, a standard-of-care 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 consult bookings, diagnostic-document intakes, and page tags go
Intakes and bookings on your WordPress site
Check which symptom-score, medication-list, prior-TRT-history, pharmacy-preference, or lab-upload fields you enable, who can open form entries and consult bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the bloodwork answers before the patient does. Notification emails can also copy those fields off-site. One table can list every person who uploaded a testosterone PDF next to a symptom score. Ask your web vendor not to keep lab reports next to erection-quality scores in one open submissions list longer than operations need, and to purge intake rows when the visit is closed. A privacy-policy page does not by itself limit who can open a submissions list. A stored appointment is not a diagnosis. An uploaded lab PDF is not proof the clinic read or verified it.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the TRT-clinic intake page. That page request can reach a vendor host before anyone submits. The page URL can say TRT clinic even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off intake and booking pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "confidential hormone intake" badge is not a verified storage path.
Consult, diagnostic-document 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 hormone-clinic or EHR SaaS platforms without a WordPress.org listing are 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A consult or lab-review booking is a booking you create; a service name such as TRT consult or hormone lab review is a label you configure. Neither is a documented default. Symptom-score, medication-list, prior-TRT-history, or pharmacy-preference questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not a diagnosis — and a CSV export of visits next to a name and a lab-review label is still a diagnostic-document row waiting for a PDF. 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. | TRT-clinic consult and lab-review bookings stored 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. Symptom-score, medication-list, prior-TRT-history, or pharmacy-preference questions are fields you add; they are not documented defaults. Completing the form can store a laboratory's total/free testosterone PDF next to ADAM-style symptom scores, a medication list, a prior-TRT history, and a pharmacy preference — before any clinician reviews the labs. A consult booking is not a diagnosis. A symptom score is a self-rating, not a clinical finding. An uploaded lab PDF is a stored document, not proof the clinic read or verified it — and a lab number next to a name can sit in the same row as a stigmatized erection-quality score. A staff login can open the uploaded lab next to the symptom answers. 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. | Diagnostic-document intake entries stored in WordPress; optional lab-report and prior-prescription 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 symptom-score, medication-list, prior-TRT-history, pharmacy-preference, or lab-upload field was sent. A page request from this script is not proof anyone sought treatment. The page URL can say TRT clinic even when no form is submitted. Consent timing has not been tested. Review which tags you enable on intake and booking pages. | 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. Symptom-score, medication-list, prior-TRT-history, pharmacy-preference, or lab-upload fields often depend on the fields you configure. A consult booking is not a diagnosis. A symptom score is a self-rating, not a clinical finding. An uploaded lab PDF is a stored document, not proof the clinic read or verified it. A marketing-tag page request is not proof anyone sought treatment. The page URL can say TRT clinic even when no form is submitted. The bloodwork answers before the patient does — that is a storage path next to a name, not a feature these plugins claim. This page is about that diagnostic-document intake, not a hair-restoration consultation, a weight-loss weigh-in, a ketamine eligibility form, a medical-marijuana-card application, or a sleep-clinic intake. Ask your web vendor who can open entries, whether a marketing tag loads on the intake page, and how long records and backups are kept. A "confidential hormone intake" 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 telehealth-prescribing law, controlled-substance or Schedule-III rules, anti-aging efficacy, lab accuracy, or standard of care. Review stored records, bookings, connected services, exports, notification emails, marketing tags on intake pages, and backups.
Documentation snapshot: Oct 14, 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-trt-clinic-plugin-privacy