Hypnotherapy plugin privacy
The booking that stores the habit you've told no one about
A hypnotherapy booking page can look like a calendar and a short intake. The same form often asks what habit you want to stop, what you have already tried, when it started, and which health history matters — plus a six-session package choice that dates how long the problem has been worth stopping — and stores those answers next to the client's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a smoking goal next to a "spouse does not know" note and a when-it-started year — the confession typed once into a vendor table next to a marketing pixel. A session request is not a diagnosis. A goal field is what the client chose to disclose, not a clinical finding. A what-you-have-tried answer is the client's account, not a treatment record. A package purchase is a prepayment, not an outcome. A page request is not proof anyone has the habit the page names. The page URL can say hypnotherapy even when no form is submitted. Ask what happens to the goal answer and the prior-treatment notes after the consult — the booking stores the habit you told no one about, and the row outlives the visit. 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 hypnotherapy-efficacy claim, a licensure or scope-of-practice claim, a HIPAA or therapy-privilege coverage claim, a smoking-cessation or weight-outcome 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 session bookings, habit notes, and page tags go
Bookings and notes on your WordPress site
Check which goal, what-you-have-tried, when-it-started, health-history, or referral-source fields you enable, who can open form entries and consult or session bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the booking stores the habit you have told no one about. Notification emails can also copy those fields off-site. One table can list every six-session package next to a goal field and a when-it-started date. Ask your web vendor not to keep goal next to health-history 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 a diagnosis. A package purchase is not an outcome.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the hypnotherapy booking page. That page request can reach a vendor host before anyone submits. The page URL can say hypnotherapy 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 "certified hypnotherapist" badge is not a verified storage path.
Consult / session booking, habit 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 hypnosis CRM 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 consult slot, a single session, or a six-session package is a booking you create; a service name such as smoking-cessation intake, phobia session, or package prepayment is a label you configure. Neither is a documented default. Goal, what-you-have-tried, when-it-started, health-history, or referral-source questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not a diagnosis — and a CSV export of a six-session package next to a goal field is still a calendar of how long the habit has been worth stopping. 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. | Consult and session 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. Goal, what-you-have-tried, when-it-started, health-history, or referral-source questions are fields you add; they are not documented defaults. Completing the form can store a goal answer next to a what-you-have-tried field, a when-it-started date, a health-history note, a referral-source, and optional prior-treatment-notes uploads — typed once as the habit you told no one about into the same tables as a newsletter signup. A session request is not a diagnosis. A goal field is what the client chose to disclose, not a clinical finding. A what-you-have-tried answer is the client's account, not a treatment record. A package purchase is a prepayment, not an outcome — and a staff login can open "quit smoking, spouse does not know, started 2019, tried patches twice" next to a six-session package choice. 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. | Habit / goal intake entries stored in WordPress; optional prior-treatment-notes 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 goal, what-you-have-tried, when-it-started, health-history, or referral-source field was sent. A page request from this script is not proof anyone has the habit the page names. The page URL can say hypnotherapy 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. Goal, what-you-have-tried, when-it-started, health-history, or referral-source fields often depend on the fields you configure. A session request is not a diagnosis. A goal field is what the client chose to disclose, not a clinical finding. A what-you-have-tried answer is the client's account, not a treatment record. A package purchase is a prepayment, not an outcome. A marketing-tag page request is not proof anyone has the habit the page names. The page URL can say hypnotherapy even when no form is submitted. The booking that stores the habit you've told no one about — that is a storage path next to a when-it-started field, not a feature these plugins claim. This page is about that habit intake, not gambling-addiction counseling, a ketamine clinic, a weight-loss program, a sleep clinic, or a psychic reading. 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 "certified hypnotherapist" 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 hypnotherapy efficacy, licensure or scope of practice, HIPAA or therapy-privilege coverage status, or smoking-cessation or weight outcomes. 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-hypnotherapy-plugin-privacy