Mobile phlebotomy plugin privacy

The standing appointment that maps which houses hold the sick

A one-off draw is an errand. A standing weekly booking is a calendar you can read as a diagnosis. A form can collect a home address, access notes such as a key under the mat, a patient who is bedbound, or a dog in the yard, an uploaded lab order that names the ordering physician and the test panel, and a draw-site note for which arm still has usable veins. That row can sit in a form plugin entries table any staffer can open. Standing-weekly, home-address, access-notes, lab-order, ordering-physician, test-panel, draw-site, patient-name, phone, and draw-date fields are configured, not documented defaults. Optional lab-order files go in the site uploads folder. A standing weekly booking is a stored calendar, not proof of a diagnosis. A home address is a stored location, not a verified residence. An access note is a stored instruction, not proof of entry. A lab-order upload is a file, not a lab result. An ordering physician is a stored name, not a verified clinician. A test-panel label is a stored label, not a verified panel. A draw-site note is a stored note, not proof of vein status. A mobile-phlebotomy booking is not proof anyone booked a draw. A page request is not proof anyone booked. The page URL can say mobile phlebotomy even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on booking and intake pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a plasma-donation claim, a cord-blood claim, a drug-testing claim, an IV-hydration claim, a home-care claim, a lab-information-system claim, a HIPAA 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 mobile-phlebotomy bookings, lab-order files, and page tags go

Draw bookings and forms handled on your WordPress site

Check which standing-weekly, home-address, access-notes, lab-order, ordering-physician, test-panel, draw-site, patient-name, phone, or draw-date fields you enable, who can open form entries and bookings, where uploaded lab-order files live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a request that never became a draw. Notification emails can also copy the same standing-weekly calendars, addresses, access notes, lab-order files, ordering-physician names, test-panel labels, draw-site notes, and patient names off-site. One table can name the house, the standing weekly slot, and the test panel next to a phone, even when the draw is never collected. Ask your web vendor not to collect a test-panel label next to a home address and an access note on the first public form, not to store those lab-order files next to a standing weekly slot in one open submissions list, and to purge unused bookings after the date passes. A privacy-policy page does not by itself limit who can export a booking list or republish an upload. A stored booking is not proof of a diagnosis.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the mobile-phlebotomy booking or intake page. That page request can reach a vendor host before anyone submits. The page URL can say mobile phlebotomy 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 standing-weekly calendars, lab-order files, or draw-site notes. An "at-home blood draw" badge is not a verified storage path.

Mobile-phlebotomy 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 mobile-phlebotomy LIS or lab-courier software without a WordPress.org listing is 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). The listing documents automatic email notifications: customers get instant booking confirmations; staff get notified; templates can include booking information and custom fields; customers can confirm or cancel via a link in the email. WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A mobile blood draw is a booking you create; a service name such as mobile phlebotomy, at-home blood draw, standing weekly INR, viral-load draw, or chemo monitoring is a label you configure. Neither is a documented default. The stored service name can say mobile phlebotomy in plain text before anyone arrives. Standing-weekly, home-address, access-notes, ordering-physician, test-panel, draw-site, patient-name, phone, or draw-date questions are custom fields you add (textarea, select, or input); they are not documented defaults. A standing weekly booking is a stored calendar, not proof of a diagnosis. A home address is a stored location, not a verified residence. An access note is a stored instruction, not proof of entry. An ordering physician is a stored name, not a verified clinician. A test-panel label is a stored label, not a verified panel. A draw-site note is a stored note, not proof of vein status. A booked slot is not proof anyone booked a draw, and is not proof a sample was collected. Cancelling or missing the slot later does not erase the standing-weekly note, address, access note, or draw-site already stored next to a name, and does not unsend a confirmation email already delivered. How long that pairing sits after a booking that never became a draw is not a documented default of the plugin. The appointments list can show who is booked this week and at which address. 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.

Mobile-phlebotomy bookings, custom intake fields, and automatic confirmation emails 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. Standing-weekly, home-address, access-notes, ordering-physician, test-panel, draw-site, patient-name, phone, or draw-date questions are fields you add; they are not documented defaults. Lab-order PDFs and requisition photos are files you accept; those file types are not documented defaults. A standing weekly booking is a stored calendar, not proof of a diagnosis. A home address is a stored location, not a verified residence. An access note is a stored instruction, not proof of entry. A lab-order upload is a file, not a lab result. An ordering physician is a stored name, not a verified clinician. A test-panel label is a stored label, not a verified panel. A draw-site note is a stored note, not proof of vein status. A mobile-phlebotomy booking is not proof anyone booked a draw. Notification emails can copy field values and file links off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. How long a pairing sits after a request that never became a draw is not a documented default of the plugin.

Intake and lab-order 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 standing-weekly, home-address, or test-panel field was sent. A page request from this script on a mobile-phlebotomy booking page is not proof anyone booked, and a pre-consent tag on that page can still treat mobile-phlebotomy interest as an audience segment from the URL alone. The page URL can say mobile phlebotomy even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and intake pages. Keep marketing tags off those pages if you do not want that page request. A tagged booking page can re-confirm mobile-phlebotomy interest next to a stored address; this row does not claim a draw from that request.

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. Standing-weekly, home-address, access-notes, lab-order, ordering-physician, test-panel, draw-site, patient-name, phone, or draw-date fields often depend on the fields you configure. A standing weekly booking is a stored calendar, not proof of a diagnosis. A home address is a stored location, not a verified residence. An access note is a stored instruction, not proof of entry. A lab-order upload is a file, not a lab result. An ordering physician is a stored name, not a verified clinician. A test-panel label is a stored label, not a verified panel. A draw-site note is a stored note, not proof of vein status. A mobile-phlebotomy booking is not proof anyone booked a draw. A marketing-tag page request is not proof anyone booked. The page URL can say mobile phlebotomy even when no form is submitted. The standing weekly slot, the address, the lab-order file, and the draw-site note can sit after a request that never became a draw. This page is about the standing appointment that maps which houses hold the sick, not a plasma-donation eligibility form, not a cord-blood banked-biology record, not a drug-testing suspicion appointment, not an IV-hydration drip-lounge intake, and not a home-care caregiver relationship. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or intake page, and how long records and backups are kept. An "at-home blood draw" 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 plasma-donation, cord-blood, drug-testing, IV-hydration, home-care, or lab-information-system claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and intake pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-mobile-phlebotomy-plugin-privacy