Float spa plugin privacy
The waiver that collects a medical history to let you lie in salt water
A pre-float waiver can store epilepsy, pregnancy, heart-condition, claustrophobia, incontinence, and fresh-tattoo answers next to a name before anyone enters a tank. Those answers gate entry, then sit in the same form-plugin entries table as gift-card signups. Recurring bookings with timestamps can sit in an appointments list any staffer can open. A standing Tuesday float that stops for six months is a stored booking pattern that dates a condition. A first-float field plus an emergency-contact row records who should be called if the client panics alone in a dark tank. Epilepsy, pregnancy, heart-condition, claustrophobia, incontinence, fresh-tattoos, first-float, emergency-contact, client-name, session-type, and phone fields are configured, not documented defaults. An epilepsy answer is a stored screening answer, not proof of a diagnosis. A pregnancy answer is a stored screening answer, not proof anyone is pregnant. A standing Tuesday float that stops is a stored booking pattern, not proof of a medical change. A first-float field is a stored booking flag, not proof anyone panicked. An emergency contact is a named third party, not proof anyone was called. A float-spa booking is not proof anyone floated. A page request is not proof anyone booked a session. The page URL can say float spa even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on booking and waiver pages, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a clinical claim, a massage claim, a tanning claim, an IV-hydration claim, a HIPAA 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 float-spa bookings, waiver answers, and page tags go
Float-spa bookings and forms handled on your WordPress site
Check which epilepsy, pregnancy, heart-condition, claustrophobia, incontinence, fresh-tattoos, first-float, emergency-contact, client-name, session-type, or phone fields you enable, who can open form entries and bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a slot is missed. Notification emails can also copy the same screening answers, emergency contacts, names, session types, and phone numbers off-site. One table can name a medical screening answer, an emergency contact, and a client name next to a session type, even when no float is held, and that row can sit next to a gift-card signup. The appointments list can show a standing Tuesday float and the weeks it stopped. Ask your web vendor not to collect a medical screening answer next to a name and an emergency contact on the first public form, not to store those answers next to gift-card signups in one open submissions list, and to purge unused pairings after the slot passes. A privacy-policy page does not by itself limit who can export a waiver list. A stored pregnancy answer is not proof anyone is pregnant.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the float-spa booking or waiver page. That page request can reach a vendor host before anyone submits. The page URL can say float spa even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and waiver pages if you do not want that page request. A browser scan cannot inspect stored epilepsy answers, pregnancy answers, or emergency contacts. A "sensory deprivation certified" badge is not a verified storage path.
Float-spa booking, waiver, 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 float-spa or sensory-deprivation SaaS tools 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). 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 float-spa appointment is a booking you create; a service name such as sensory deprivation, isolation tank, or first float is a label you configure. Neither is a documented default. The stored service name can say float spa in plain text before anyone enters a tank. Epilepsy, pregnancy, heart-condition, claustrophobia, incontinence, fresh-tattoos, first-float, emergency-contact, client-name, session-type, or phone questions are custom fields you add (textarea, select, or input); they are not documented defaults. An epilepsy answer is a stored screening answer, not proof of a diagnosis. A pregnancy answer is a stored screening answer, not proof anyone is pregnant. A first-float field is a stored booking flag, not proof anyone panicked. An emergency contact is a named third party, not proof anyone was called. A booked slot is not proof anyone floated. Cancelling or missing the slot later does not erase the screening answers, emergency contact, or name already stored next to a session type, and does not unsend a confirmation email already delivered. How long that pairing sits after a booking that never produced a float is not a documented default of the plugin. The appointments list can show a standing Tuesday float and the weeks it stopped. 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. | Float-spa bookings, custom waiver fields, and automatic confirmation emails 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. Epilepsy, pregnancy, heart-condition, claustrophobia, incontinence, fresh-tattoos, first-float, emergency-contact, client-name, session-type, or phone questions are fields you add; they are not documented defaults. Waiver PDFs, ID photos, and gift-card forms are files and forms you accept; those types are not documented defaults. A medical screening answer can sit in the same entries table as a gift-card signup. An epilepsy answer is a stored screening answer, not proof of a diagnosis. A pregnancy answer is a stored screening answer, not proof anyone is pregnant. A first-float field is a stored booking flag, not proof anyone panicked. An emergency contact is a named third party, not proof anyone was called. A float-spa booking is not proof anyone floated. 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 slot is missed is not a documented default of the plugin. | Float-spa waiver entries stored in WordPress; file 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 an epilepsy, pregnancy, heart-condition, or client-name field was sent. A page request from this script on a float-spa waiver or booking page is not proof anyone booked a session, and a pre-consent tag on that page can still treat float-spa interest as an audience segment from the URL alone. The page URL can say float spa even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and waiver pages. Keep marketing tags off those pages if you do not want that page request. A tagged waiver page can re-confirm float-spa interest next to a stored screening answer; this row does not claim a session was held from that request. | 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. Epilepsy, pregnancy, heart-condition, claustrophobia, incontinence, fresh-tattoos, first-float, emergency-contact, client-name, session-type, or phone fields often depend on the fields you configure. An epilepsy answer is a stored screening answer, not proof of a diagnosis. A pregnancy answer is a stored screening answer, not proof anyone is pregnant. A standing Tuesday float that stops is a stored booking pattern, not proof of a medical change. A first-float field is a stored booking flag, not proof anyone panicked. An emergency contact is a named third party, not proof anyone was called. A float-spa booking is not proof anyone floated. A marketing-tag page request is not proof anyone booked a session. The page URL can say float spa even when no form is submitted. The screening answer, the emergency contact, and the name can sit after a slot is missed, in the same entries table as gift-card signups. This page is about a pre-float waiver that files a medical history at a wellness shop, not an IV drip-lounge intake, not a tanning session log, not an acupuncture health chart, and not a massage booking. Ask your web vendor who can open entries, whether a marketing tag loads on the booking or waiver page, and how long records and backups are kept. A "sensory deprivation certified" 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 clinical, HIPAA, massage, tanning, or IV claims. Review stored records, connected services, exports, notification emails, marketing tags on booking and waiver pages, and backups.
Documentation snapshot: Oct 16, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress forms privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-float-spa-plugin-privacy