Medical transport plugin privacy
The ride schedule that spells the diagnosis, held by the company with no chart
A non-emergency medical transport booking page can look like a van schedule and a short logistics form. The same form often asks for a pickup address, a destination facility, mobility equipment, a reason for visit, and an emergency contact — plus an optional insurance-card or broker-authorization upload — and stores those answers next to the rider's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a Tuesday / Thursday / Saturday standing ride next to a named dialysis center — a diagnosis spelled as a calendar entry, held by the third business in the chain, the company with no chart. A ride request is not proof any treatment occurred. A destination-facility field is the booker's routing note, not a referral. A mobility-equipment answer is logistics typed by whoever booked, often a caseworker, not the rider. An uploaded insurance card is a client document, not a claim. A page request is not proof anyone needed a ride. The page URL can say medical transport even when no form is submitted. Ask what happens to the destination facility and the reason-for-visit note after the trip — the ride schedule spells the diagnosis, and the row outlives the ride. 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 HIPAA coverage or business-associate claim, a Medicaid or broker (MTM, Modivcare) compliance claim, an ADA paratransit-law claim, a vehicle or driver licensing 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 ride bookings, logistics notes, and page tags go
Bookings and notes on your WordPress site
Check which pickup-address, destination-facility, mobility-equipment, reason-for-visit, or emergency-contact fields you enable, who can open form entries and recurring ride bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a trip closes — when the ride schedule spells the diagnosis and is held by the company with no chart. Notification emails can also copy those fields off-site. One table can list every standing dialysis run next to a destination-facility field and a reason-for-visit note. Ask your web vendor not to keep pickup next to destination-facility and reason-for-visit 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 proof treatment occurred. An uploaded insurance card is not a claim.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the medical-transport booking page. That page request can reach a vendor host before anyone submits. The page URL can say medical transport 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 broker authorization PDF is not a verified storage path for the rest of the row.
Recurring ride booking, logistics 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 NEMT dispatch 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 standing Tuesday / Thursday / Saturday dialysis run, a one-way clinic drop-off, or a round-trip specialist visit is a booking you create; a service name such as wheelchair van, stretcher transport, or oxygen-capable ride is a label you configure. Neither is a documented default. Pickup-address, destination-facility, mobility-equipment, reason-for-visit, or emergency-contact questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof treatment occurred — and a CSV export of a three-day-a-week ride next to a named dialysis center is still a calendar that spells a diagnosis without a chart. 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. | Recurring ride 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. Pickup-address, destination-facility, mobility-equipment, reason-for-visit, or emergency-contact questions are fields you add; they are not documented defaults. Completing the form can store a pickup address next to a destination-facility field, a mobility-equipment answer, a reason-for-visit note, an emergency contact, and optional insurance-card or broker-authorization uploads — typed once as logistics for a standing clinic run into the same tables as a newsletter signup. A ride request is not proof any treatment occurred. A destination-facility field is the booker's routing note, not a referral. A mobility-equipment answer is logistics typed by whoever booked, often a caseworker, not the rider. An uploaded insurance card is a client document, not a claim — and a staff login can open "123 Oak St → Riverside Dialysis, Tue/Thu/Sat, wheelchair, dialysis" next to a broker authorization 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. | Ride logistics intake entries stored in WordPress; optional insurance-card or broker-authorization 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 pickup-address, destination-facility, mobility-equipment, reason-for-visit, or emergency-contact field was sent. A page request from this script is not proof anyone needed a ride. The page URL can say medical transport 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. Pickup-address, destination-facility, mobility-equipment, reason-for-visit, or emergency-contact fields often depend on the fields you configure. A ride request is not proof any treatment occurred. A destination-facility field is the booker's routing note, not a referral. A mobility-equipment answer is logistics typed by whoever booked, often a caseworker, not the rider. An uploaded insurance card is a client document, not a claim. A marketing-tag page request is not proof anyone needed a ride. The page URL can say medical transport even when no form is submitted. The ride schedule that spells the diagnosis, held by the company with no chart — that is a storage path next to a destination-facility field, not a feature these plugins claim. This page is about that third-company logistics table, not a dialysis clinic's own calendar, home care, hospice, a medical-alert signup, or an alarm company. 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 broker authorization PDF is not a verified storage path for the rest of the row. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess HIPAA coverage or business-associate status, Medicaid or broker compliance, ADA paratransit law, or vehicle or driver licensing. 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-medical-transport-plugin-privacy