EAP counseling plugin privacy
The therapy intake on a site your employer pays for
An EAP counseling site's paying customer is the employer. The employee books stress, substance, or marriage counseling through a portal whose contract, branding, and sometimes subdomain belong to the company. One session booking can hold an employer name, an employee ID, a work email, a reason-for-visit, and a manager-referral note. Those answers can sit in a local-first booking or intake plugin behind one admin login. The form plugin's row and a vendor tag's page request both live on infrastructure the company's contract funds. The confidentiality promise and the invoice go to the same address. A session booking is not a diagnosis. A page request is not proof that a reason-for-visit was collected. The page URL can say EAP or counseling even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries, 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, an EAP-confidentiality-law claim, an ERISA claim, a HIPAA-applicability claim, an employer-access claim, a therapy-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, intake answers, and page tags go
Bookings and entries handled on your WordPress site
Check which employer, employee-ID, work-email, reason-for-visit, substance, marriage, burnout, or manager-referral fields you enable, who can open form entries and bookings, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a session that was cancelled or never attended. Notification emails can also copy the same answers off-site. One table can list every employee who booked counseling even when only the employee typed. Ask your web vendor not to collect a work email or employee ID on the first public form, not to store a reason-for-visit next to an employer name in one open submissions list, and to purge bookings that were never attended. A privacy-policy page does not by itself limit who can open an uploads folder. A stored booking is not proof an employer opened it.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the EAP counseling booking or intake page. That page request can reach a vendor host before anyone submits. The page URL can say EAP or counseling 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 bookings. A "confidential EAP" badge is not a verified storage path.
EAP counseling 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 EAP or employee-assistance software without a WordPress.org listing is 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. An EAP counseling session is a booking you create; a service name such as counseling slot or EAP session is a label you configure. Neither is a documented default. Employer, employee-ID, work-email, reason-for-visit, substance, marriage, burnout, or manager-referral questions are custom fields you add (textarea, select, or input); they are not documented defaults. A submitted session booking is not a diagnosis. Cancelling or missing a session later does not erase the contact answers already stored next to a name, and does not unsend a confirmation email already delivered. The paying customer for the site can be the employer; that funding structure is not a documented default of the plugin. This row does not claim an employer can open the appointments list. 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. | Session bookings, custom intake 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. Employer, employee-ID, work-email, reason-for-visit, substance, marriage, burnout, or manager-referral questions are fields you add; they are not documented defaults. Supporting files are files you accept; they are not documented defaults. A submitted intake entry is not a diagnosis. 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. This row does not claim an employer can open the submissions list. The paying customer for the site can be the employer; that funding structure is not a documented default of the plugin. | Intake form 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 employer name, employee ID, work email, or reason-for-visit field was sent. A page request from this script is not proof a reason-for-visit was collected. The page URL can say EAP or counseling even when no form is submitted. Consent timing has not been tested. Review which tags you enable on EAP counseling booking and intake pages. Keep marketing tags off those pages if you do not want that page request. The page request lives on infrastructure the company's contract can also fund; this row does not claim an employer opened the vendor account. | 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. Employer, employee-ID, work-email, reason-for-visit, substance, marriage, burnout, or manager-referral fields often depend on the fields you configure. A session booking is not a diagnosis. A marketing-tag page request is not proof a reason-for-visit was collected. The page URL can say EAP or counseling even when no form is submitted. The paying customer for the site can be the employer even when the employee is the person filling the form. This page is about an employer-paid counseling intake, not a private therapy practice, a workers-compensation injury file, or a union authorization card. 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. A "secure" or "confidential EAP" 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 applicability, ERISA, EAP confidentiality law, employer access, or therapy outcomes. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and intake pages, and backups.
Documentation snapshot: Oct 13, 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-eap-counseling-plugin-privacy