Sexual health clinic plugin privacy

Where does the booking where the reason-for-visit field is the disclosure go?

A confidential-testing clinic promises privacy; the WordPress booking form is where that promise breaks first. Reason-for-visit, exposure date, symptoms, and sometimes a partner to notify are typed before anyone has seen a doctor, then sit in a local-first booking or form plugin behind one admin login. The visit may produce a clean result; the row that says why you booked never updates. A marketing tag on the same page can send a page request to a vendor host before anyone submits. A page request is not proof that anyone sought testing. A booking is not a diagnosis or a lab result. This sample reviews three plugins' documentation. Check which reason-for-visit fields you collect, who can open entries, where uploaded files land, which tags load on the booking page, and how long records, files, and backups are kept.

Documentation review only. This is not legal advice, a medical-outcome claim, a HIPAA review, a public-health-reporting assessment, a partner-notification-law 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 booking answers, disclosures, and page tags go

Entries and bookings handled on your WordPress site

Check which reason-for-visit, exposure-date, symptom, or partner-to-notify fields you enable, who can open form entries and bookings, where uploaded insurance or referral files live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after a booking that never became a completed visit — including after a clean result that never updates the row. Notification emails can also copy the same answers off-site. Ask your web vendor not to collect a free-text reason-for-visit narrative on the first public form when a short service label would do, and not to store a partner name next to exposure fields in one open submissions list.

Page tags handled by a vendor

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

Sexual-health booking, 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 clinic EMR 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 clinics and health practices (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 confidential-testing or consult slot is a booking you create; a service name such as STI testing is a label you configure. Neither is a documented default. Reason-for-visit, exposure-date, symptom, or partner-to-notify questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booking is not a diagnosis or a lab result. A clean result later does not update or erase the reason-for-visit text already stored. Emails can include those custom fields. 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.

Testing or consult slot bookings and custom intake fields 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. Reason-for-visit, exposure-date, symptom, or partner-to-notify questions are fields you add; they are not documented defaults. Insurance cards or referral PDFs are files you accept; they are not documented defaults. One intake entry can store a free-text reason-for-visit that reads like a diagnosis the patient wrote themselves. A booking or intake entry is not a diagnosis or a lab result. Notification emails can copy field values off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified.

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 reason-for-visit answer, exposure date, or partner name was sent. A page request from this script is not proof that anyone sought confidential testing. Consent timing has not been tested. Review which tags you enable on sexual-health 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. Reason-for-visit answers, exposure dates, symptom notes, or partner-to-notify fields often depend on the fields you configure. A booking is not a diagnosis or a lab result. A marketing-tag page request is not proof that anyone sought testing. A clean lab result later does not update or erase the reason-for-visit text already stored. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking page, and how long records and backups are kept. A "confidential" or "secure patient forms" 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 medical outcomes, HIPAA, public-health reporting, or partner-notification law. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-sexual-health-clinic-plugin-privacy