IV hydration plugin privacy

The drip-lounge intake that stores last night in a medical record

An IV-hydration lounge is retail with a needle. The booking intake asks for medications, allergies, conditions — and the reason for the drip. "Hangover recovery, Sunday 9am" is a timestamped statement about last night, co-signed by a med-history form, sitting in the same WordPress bookings table as a haircut. Those fields are configured, not documented defaults. Walk-in wellness, charted like a clinic, secured like a contact form. A drip booking is a calendar row, not proof anyone received an infusion. A hangover-recovery reason is what a guest typed, not a diagnosis. A medication or allergy answer is the guest's note, not a chart. An intake upload is a client document in a site uploads folder. A page request is not proof anyone booked a drip. The page URL can say IV hydration even when no form is submitted. Ask what happens to the med-history answers and the hangover-recovery reason after the visit — the drip-lounge intake that stores last night in a medical record outlives the Myers cocktail. 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 HIPAA or medical-privacy-law claim, an IV-therapy or hangover-cure efficacy claim, a nursing or prescribing-standards claim, a clinical-fitness 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 drip-lounge bookings, med-history intakes, and page tags go

Intakes and bookings on your WordPress site

Check which medication, allergy, condition, drip-reason, emergency-contact, or intake-upload fields you enable, who can open form entries and drip-lounge bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the drip-lounge intake stores last night in a medical record. Notification emails can also copy those fields off-site. One table can list every hangover-recovery reason a guest typed next to a Sunday slot and a medication list. Ask your web vendor not to keep intake uploads next to med-history answers in one open submissions list longer than operations need, and to purge booking rows when a drip is cancelled or a visit closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored drip booking is not proof anyone received an infusion. A hangover-recovery reason is not a diagnosis.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the IV-hydration booking or med-history intake page. That page request can reach a vendor host before anyone submits. The page URL can say IV hydration even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off drip-lounge booking and intake pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "wellness privacy" badge is not a verified storage path.

Drip-lounge booking, IV-hydration med-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 lounge or EHR SaaS tools 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 Sunday Myers cocktail or hangover-recovery drip slot is a booking you create; a service name such as IV hydration or hangover recovery is a label you configure. Neither is a documented default. Medication, allergy, condition, drip-reason, or emergency-contact questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof anyone received an infusion — and a CSV export of a Sunday 9am hangover-recovery slot next to a medication list and an allergy note is still a calendar that holds last night beside a contact name. 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.

Drip-lounge 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. Medication, allergy, condition, drip-reason, or emergency-contact fields are fields you add; they are not documented defaults. Completing the form can store a medication list next to an allergy note, a condition disclosure, a drip-reason such as hangover recovery, an emergency contact, and optional intake uploads — typed once as the drip-lounge intake that stores last night in a medical record, into the same tables as a haircut booking. A hangover-recovery reason is what a guest typed, not a diagnosis. A medication or allergy answer is the guest's note, not a chart — and a staff login can open "Alex, meds: sertraline, allergy: penicillin, reason: hangover recovery Sunday 9am, emergency Sam, intake.pdf" next to everyone else's resume. A drip booking is a calendar row, not proof anyone received an infusion. 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.

IV-hydration med-history intake stored in WordPress; optional intake 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 medication, allergy, condition, drip-reason, or emergency-contact field was sent. A page request from this script is not proof anyone booked a drip. The page URL can say IV hydration even when no form is submitted. Consent timing has not been tested. Review which tags you enable on drip-lounge booking and IV-hydration intake 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. Medication, allergy, condition, drip-reason, emergency-contact, or intake-upload fields often depend on the fields you configure. A drip booking is a calendar row, not proof anyone received an infusion. A hangover-recovery reason is what a guest typed, not a diagnosis. A medication or allergy answer is the guest's note, not a chart. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone booked a drip. The page URL can say IV hydration even when no form is submitted. The drip-lounge intake that stores last night in a medical record — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that OTC-adjacent retail hydration booking with a med-history form, not a medspa aesthetics intake, a ketamine-clinic failed-medication eligibility form, or a TRT-clinic bloodwork-first consult. 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 "wellness privacy" or "HIPAA" 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, medical privacy law, IV-therapy efficacy, hangover-cure efficacy, nursing or prescribing standards, or clinical fitness. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking and 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-iv-hydration-plugin-privacy