Bariatric clinic plugin privacy
The intake where you type the number you have never said out loud
A bariatric clinic booking page can look like a calendar and a short intake. The same form often asks for highest-ever weight, current weight, a comorbidity checklist, prior diet attempts, and supervised-diet history — the number you have never said out loud, typed before any doctor-patient relationship exists — and stores those answers next to the patient's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a highest-weight answer next to a failed-attempts essay and a marketing pixel — the intake where you type the number you have never said out loud, typed once into a vendor table next to a newsletter signup. A consult request is not surgical candidacy. A highest-weight field is the patient's recollection, not a chart vital. A comorbidity checkbox is self-report, not a diagnosis. An uploaded diet log is a client document in a site uploads folder, not an insurance determination. A page request is not proof anyone had surgery. The page URL can say bariatric clinic even when no form is submitted. Ask what happens to the highest-weight answer and the diet-log upload after the visit — the intake is where you type the number you have never said out loud, and the row outlives the appointment. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a surgical-outcomes claim, a BMI or candidacy-threshold claim, an insurance-coverage eligibility claim, a GLP-1 or program-efficacy claim, a HIPAA coverage 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, weight notes, and page tags go
Bookings and notes on your WordPress site
Check which highest-weight, current-weight, comorbidity-checklist, prior-attempts, or supervised-diet-history fields you enable, who can open form entries and consult or seminar bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the intake is where you type the number you have never said out loud. Notification emails can also copy those fields off-site. One table can list every seminar RSVP next to a highest-weight field and a failed-attempts essay. Ask your web vendor not to keep highest weight next to comorbidities in one open submissions list longer than operations need, and to purge intake rows when the booking ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not surgical candidacy. A comorbidity checkbox is not a diagnosis.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the bariatric clinic booking page. That page request can reach a vendor host before anyone submits. The page URL can say bariatric clinic even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and intake pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "weight-loss surgery ready" badge is not a verified storage path.
Consult / seminar booking, bariatric 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 bariatric EHR and surgery-scheduling 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 slot or an information seminar is a booking you create; a service name such as surgical consult, seminar RSVP, or follow-up visit is a label you configure. Neither is a documented default. Highest-weight, current-weight, comorbidity-checklist, prior-attempts, or supervised-diet-history questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not surgical candidacy — and a CSV export of a seminar RSVP next to a highest-weight field is still a calendar that holds the number the patient has never said out loud. 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. | Consult and seminar 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. Highest-weight, current-weight, comorbidity-checklist, prior-attempts, or supervised-diet-history questions are fields you add; they are not documented defaults. Completing the form can store a highest-weight answer next to a current-weight field, a comorbidity checklist, a prior-attempts essay, a supervised-diet history, and optional diet-log or referral-letter uploads — typed once as the intake where you type the number you have never said out loud into the same tables as a newsletter signup. A consult request is not surgical candidacy. A highest-weight field is the patient's recollection, not a chart vital. A comorbidity checkbox is self-report, not a diagnosis. An uploaded diet log is a client document in a site uploads folder, not an insurance determination — and a staff login can open "highest 312, now 278, diabetes + sleep apnea, Atkins 2019 / keto 2021 / Weight Watchers 2023" next to a diet-log PDF. 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. | Bariatric intake entries stored in WordPress; optional diet-log and referral-letter 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 highest-weight, current-weight, comorbidity-checklist, prior-attempts, or supervised-diet-history field was sent. A page request from this script is not proof anyone had surgery. The page URL can say bariatric clinic even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and intake 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. Highest-weight, current-weight, comorbidity-checklist, prior-attempts, or supervised-diet-history fields often depend on the fields you configure. A consult request is not surgical candidacy. A highest-weight field is the patient's recollection, not a chart vital. A comorbidity checkbox is self-report, not a diagnosis. An uploaded diet log is a client document in a site uploads folder, not an insurance determination. A marketing-tag page request is not proof anyone had surgery. The page URL can say bariatric clinic even when no form is submitted. The intake where you type the number you have never said out loud — that is a storage path next to a failed-attempts field, not a feature these plugins claim. This page is about that surgery-funnel intake, not a weight-loss program weigh-in log, a sleep clinic, a dialysis calendar, or an allergy clinic intake. Ask your web vendor who can open entries, whether a marketing tag loads on the booking page, and how long records and backups are kept. A "weight-loss surgery ready" 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 surgical outcomes, BMI or candidacy thresholds, insurance-coverage eligibility, GLP-1 or program efficacy, or HIPAA coverage status. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking 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-bariatric-clinic-plugin-privacy