Sleep study plugin privacy

The home-test referral that records who shares your bed and what the night sounds like

A sleep-study intake can look like a kit shipment and a consult slot. It is also a medical record about two people, signed by one: who sleeps next to you, what they hear you do at night, whether you have fallen asleep driving — and a recorder headed into the bedroom. The bed partner becomes a fully described, named data subject who never touched the form, and the does-your-partner-complain field is their testimony stored under your consent. Bed-partner-name, partner-complain, night-sounds, fallen-asleep-driving, home-test-kit, and shipping-address fields are configured, not documented defaults. Optional referral PDFs or insurance cards go in the site uploads folder. A study booking is not proof a study ran. A bed-partner answer is a stored note, not proof that person consented. A page request is not proof anyone ordered a home sleep test. The page URL can say sleep study 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 account pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, an apnea diagnosis, a driving-fitness 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 study bookings, bed-partner intakes, and page tags go

Study bookings and bed-partner forms handled on your WordPress site

Check which bed-partner-name, partner-complain, night-sounds, fallen-asleep-driving, home-test-kit, or shipping-address fields you enable, who can open form entries and bookings, where uploaded referral 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 study. Notification emails can also copy the same partner name and night-sounds note off-site. One table can name the patient, the bed partner, and the partner-complain answer next to a kit ship address, even when the recorder never leaves the box. Ask your web vendor not to collect a bed-partner name next to night-sounds on the first public form, not to store partner-complain answers next to contact details in one open submissions list, and to purge unused study bookings after the date passes. A privacy-policy page does not by itself limit who can export a customer list. A stored booking is not proof a study ran.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the sleep-study booking or account page. That page request can reach a vendor host before anyone submits. The page URL can say sleep study even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and account pages if you do not want that page request. A browser scan cannot inspect stored bed-partner names, partner-complain answers, or night-sounds notes. A "sleep patient" badge is not a verified storage path.

Sleep-study booking, bed-partner-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 sleep-lab or DME 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 sleep-study consult is a booking you create; a service name such as home sleep test, in-lab overnight, or CPAP follow-up is a label you configure. Neither is a documented default. Bed-partner-name, partner-complain, night-sounds, fallen-asleep-driving, home-test-kit, or shipping-address questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked consult is not proof a study ran, and a bed-partner answer is not proof that person consented. Cancelling or missing the slot later does not erase the partner name, night-sounds note, or kit ship address already stored next to a name, and does not unsend a confirmation email already delivered. How long that row sits after a booking that never became a study is not a documented default of the plugin. 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.

Study 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. Bed-partner-name, partner-complain, night-sounds, fallen-asleep-driving, home-test-kit, or shipping-address questions are fields you add; they are not documented defaults. A referral PDF or insurance card is a file you accept; that file type is not a documented default. A study request is not proof a recorder was worn. A partner-complain answer is a stored note, not proof that person consented to being described. A dead referral still leaves the bed-partner name and night-sounds answers in the submissions list. 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 an account row sits after a request that never became a study is not a documented default of the plugin.

Account and study-intake form 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 bed-partner-name, partner-complain, night-sounds, or fallen-asleep-driving field was sent. A page request from this script is not proof anyone ordered a home sleep test. The page URL can say sleep study even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and account pages. Keep marketing tags off those pages if you do not want that page request. A tagged sleep-study page can re-confirm kit interest next to a stored bed-partner description; this row does not claim a study 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. Bed-partner-name, partner-complain, night-sounds, fallen-asleep-driving, home-test-kit, or shipping-address fields often depend on the fields you configure. A study booking is not proof a study ran. A partner-complain answer is a stored note, not proof that person consented. A marketing-tag page request is not proof anyone ordered a home sleep test. The page URL can say sleep study even when no form is submitted. The bed-partner description and the kit ship address can sit after the study never runs. This page is about a home-test referral that describes an unsigned bed partner, not a lactation quiet mood score, not an interpreter someone-else appointment row, and not a weight-loss weigh-in log. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or account page, and how long records and backups are kept. A "sleep patient" 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 apnea diagnosis, driving fitness, or HIPAA. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and account pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-sleep-study-plugin-privacy