Dialysis clinic plugin privacy
A dialysis booking calendar is itself a diagnosis
A dialysis clinic booking calendar can store a three-times-a-week chair slot. That recurring pattern can disclose dialysis treatment even before anyone reads a health-history field. Custom fields can add transport needs, insurance, or Medicare IDs. File fields can store insurance-card scans in the site uploads folder. A marketing tag on the same booking page can send a page request to a vendor host before anyone submits. A page request is not proof that a diagnosis or insurance ID was collected. A booking is not a medical record. This sample reviews three plugins' documentation. Check which fields you collect, who can open bookings and 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 or medical advice, a HIPAA review, a dialysis-outcome or treatment claim, a nephrology assessment, 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 bookings, form entries, uploaded insurance-card scans, email inboxes, staff permissions, vendor accounts, or backups.
Where chair bookings, intake files, and page tags go
Bookings and files handled on your WordPress site
Check which transport, insurance, or Medicare fields you enable, who can open bookings and form entries, where uploaded insurance-card scans live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept. Notification emails can also copy the same answers off-site. Ask your web vendor not to collect insurance-card scans on the first public form, not to mix transport questions with a public calendar, and to purge bookings that never became patients. A privacy-policy page does not by itself limit who can open a repeating chair calendar.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the dialysis 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 bookings. A "secure patient forms" badge is not a verified storage path.
Dialysis-clinic booking, form-upload, 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 dialysis clinic software without a WordPress.org listing is 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 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. The v4.0.3 readme changelog records a repeat-appointment feature (3.12.13). A three-times-a-week chair slot is a repeating booking you create; a service name such as dialysis is a label you configure. Neither is a documented default. Transport-needs, insurance, or Medicare questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booking is not a medical record. The appointments list can show a repeating cadence even when no health-history field exists. 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. | Recurring chair bookings and custom intake fields 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. Transport-needs, insurance, or Medicare questions are fields you add; they are not documented defaults. Insurance-card scans are files you accept; they are not documented defaults. A form entry is not a medical record. 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 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 diagnosis or insurance ID was sent. A page request from this script is not proof that a dialysis booking or insurance ID was collected. Consent timing has not been tested. Review which tags you enable on dialysis 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. Recurring chair slots, transport needs, insurance IDs, Medicare IDs, or insurance-card files often depend on the fields you configure. A three-times-a-week chair booking can disclose dialysis treatment even without a health-history field. A booking is not a medical record. A form entry is not a finished treatment plan. A marketing-tag page request is not proof that a diagnosis or insurance ID was collected. Ask your web vendor who can open bookings and entries, where uploaded files live, whether a marketing tag loads on the booking page, and how long records and backups are kept. A "secure" or "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 HIPAA, dialysis outcomes, treatment results, or nephrology. 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
- WordPress pharmacy plugin privacy
- WordPress therapy plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-dialysis-clinic-plugin-privacy