Prosthetics clinic plugin privacy

The fitting request that describes the body part you lost and how

A prosthetics fitting can look like a booking and a contact form. The same intake often asks amputation level and side, cause, date of loss, residual-limb measurements and photos, insurance carrier, and daily-activity goals — and stores those answers next to a name for the life of the form table. Those fields are configured, not documented defaults. The cause field is a one-word biography: it can imply a chronic disease, an employer's accident, or military service. The photos are of the body itself. A fitting request is not a medical record or proof of any diagnosis. A cause answer is the client's phrasing, not a clinical or legal finding. An uploaded prescription is a client document, not a chart entry. A page request is not proof anyone lost a limb. The page URL can say prosthetics clinic even when no form is submitted. Ask what happens to the cause field and the limb photos after the fitting — 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 intake page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a medical claim, a prosthetic-fitment-outcome claim, an ADA or disability-law claim, a workers-comp claim, a VA-benefits 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 fittings, body-history intakes, and page tags go

Intakes and bookings on your WordPress site

Check which amputation-level, cause, date-of-loss, measurement, photo, or insurance-carrier fields you enable, who can open form entries and fitting bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a fitting closes — when the row still describes the body part that was lost and how. Notification emails can also copy those fields off-site. One table can list every person who typed a cause biography. Ask your web vendor not to keep limb photos next to cause answers in one open submissions list longer than operations need, and to purge intake rows when the fitting is closed. A privacy-policy page does not by itself limit who can open a submissions list. A stored fitting is not a medical record. An uploaded prescription is not a chart entry.

Page tags handled by a vendor

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

Fitting, body-history 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 prosthetic or clinical 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 fitting or evaluation booking is a booking you create; a service name such as prosthetic fitting or orthotics evaluation is a label you configure. Neither is a documented default. Amputation-level, cause, date-of-loss, or insurance-carrier questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not a medical record — and a CSV export of fittings next to cause answers is still a name-keyed body-history row. 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.

Prosthetics fitting and evaluation 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. Amputation-level, cause, date-of-loss, measurement, photo, or insurance-carrier questions are fields you add; they are not documented defaults. Completing the form can store photos of the body itself next to a one-word cause biography — and the row outlives the fitting. A submitted fitting request is not a medical record or proof of any diagnosis. A cause answer is the client's phrasing, not a clinical or legal finding. An uploaded prescription is a client document, not a chart entry — and a limb photo next to a cause field can sit in the same row as a name and address. A staff login can open the photo next to the cause answer. 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.

Fitting-intake entries stored in WordPress; optional limb-photo, measurement, and prescription 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 amputation-level, cause, date-of-loss, or insurance field was sent. A page request from this script is not proof anyone lost a limb. The page URL can say prosthetics 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 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. Amputation-level, cause, date-of-loss, measurement, photo, or insurance-carrier fields often depend on the fields you configure. A fitting request is not a medical record or proof of any diagnosis. A cause answer is the client's phrasing, not a clinical or legal finding. An uploaded prescription is a client document, not a chart entry. A marketing-tag page request is not proof anyone lost a limb. The page URL can say prosthetics clinic even when no form is submitted. The cause field is a one-word biography next to photos of the body itself — that is a storage path next to a name, not a feature these plugins claim. This page is about that body-history intake, not a mastectomy-boutique post-surgical form, a veterans-benefits claim, a hair-restoration intake, a dialysis schedule, or a home-care roster. 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 patient 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 medical outcomes, prosthetic fitment, ADA or disability law, workers-comp rules, or VA benefits. 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

Scan your site for third-party requests

/wp-prosthetics-clinic-plugin-privacy