Crisis line plugin privacy
Where does the page visit the tag reported before you ever touched the form go?
Every other privacy page in this series needs a submitted row to have something to leak. On a crisis-line site, the vendor marketing tag's page request is the disclosure: a visitor, timestamped (often at odd hours), reported to an ad network before any form is touched. The form is optional; the leak is not. A callback-request form or counseling follow-up booking — if someone later fills one — can store name, phone, and preferred-callback-time in a local-first form or booking plugin behind one admin login. But the page URL alone can already treat crisis-line visit intent as an audience segment from that earlier tag request. A page request is not proof of any crisis outcome. A callback request is not a clinical record. This sample reviews three plugins' documentation. Check which tags load on the crisis-line page, which visitor fields you collect on callback or follow-up forms, who can open entries, where uploaded files land, and how long tag logs, records, files, and backups are kept.
Documentation review only. This is not legal advice, a crisis-intervention-efficacy claim, a named-organization claim, a specific-incident fact claim, a mental-health-diagnosis 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 page tags, callback answers, and bookings go
Entries and bookings handled on your WordPress site
Check which name, phone, or preferred-callback-time fields you enable on a callback-request form, which counseling follow-up booking labels you create, who can open form entries and bookings, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after a visit with no submission, a callback that was completed, or a booking that was abandoned. Notification emails can also copy the same visitor identity and callback answers off-site. Ask your web vendor not to store a free-text "what is going on" field next to a phone number in one open submissions list when a short matter ID would do. These rows are optional; the tag page request can already have fired.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the crisis-line page. That page request can reach a vendor host before anyone submits — and that request alone is the disclosure this page is about. Review which tags you enable, account access, and retention there. Keep marketing tags off crisis-line, callback, and follow-up booking pages if you do not want that page request. A browser scan cannot inspect stored form entries or uploaded files. A "confidential help" badge is not a verified storage path.
Crisis-line page tags, callback forms, and follow-up booking 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. Case-management 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 counseling follow-up is a booking you create; a service name such as callback follow-up or counseling slot is a label you configure. Neither is a documented default. Name, phone, or preferred-callback-time questions are custom fields you add (textarea, select, or input); they are not documented defaults. A submitted follow-up booking is not a clinical record. Cancelling or abandoning a booking later does not erase the contact answers already stored next to a name. Emails can include those custom fields. 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. This row is secondary: the primary disclosure on this page is the marketing-tag page request before any booking is touched. | Counseling follow-up bookings and custom intake fields 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. Name, phone, or preferred-callback-time questions are fields you add; they are not documented defaults. Supporting files are files you accept; they are not documented defaults. A submitted callback request is not a clinical record. Submitted or not, a prior page visit can already have been reported by a marketing tag. 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 is secondary: the primary disclosure on this page is the marketing-tag page request before any form is touched. | Callback-request 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 a name, phone, or preferred-callback-time field was sent. On a crisis-line page, the page request from this script IS the disclosure even when no form is touched — a timestamped visit reported to a vendor host before anyone decides to submit. A page request is not proof of any crisis outcome. The page URL can identify a crisis-line site even when no form was submitted. Consent timing has not been tested. Review which tags you enable on crisis-line, callback, and follow-up booking pages. Keep marketing tags off those pages if you do not want that page 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. Visitor names, phone numbers, preferred-callback-time answers, or counseling follow-up bookings often depend on the fields you configure. A callback request is not a clinical record. A marketing-tag page request is not proof of any crisis outcome — and on this page that request can still be the entire disclosure when no form is ever touched. Leaving without submitting does not erase a page request already sent to a vendor host. Ask your web vendor which marketing tags load on the crisis-line page, who can open callback entries or follow-up bookings, where uploaded files live, and how long tag logs, records, and backups are kept. A "confidential help" 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 crisis-intervention efficacy, named organizations, specific incidents, or mental-health diagnoses. Review marketing tags on crisis-line pages, stored records, uploaded files, connected services, exports, notification emails, 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-crisis-line-plugin-privacy