Sober companion plugin privacy
The calendar that marks the hours a client cannot be alone
A sober-companion booking calendar can store a Friday 6pm-to-midnight coverage window next to a first name and phone number. Every confirmed slot can say this person cannot be trusted alone during those hours. The intake can store relapse history, triggers, and the family member paying the invoice in the same row. Unlike a clinical chart locked in a treatment program, those rows sit in the same WordPress database as newsletter signups, indexed like a contact list. Recurring bookings with timestamps sit in an appointments list any staffer can open, a calendar of the hours a client is not supposed to be alone. Relapse-history, triggers, family-member-payer, client-name, coverage-window, and phone fields are configured, not documented defaults. A relapse-history answer is a stored field, not proof of relapse. A trigger answer is a stored preference, not proof anyone used. A family-member-payer is a stored billing contact, not proof anyone is paying. A Friday 6pm-midnight slot is a stored booking window, not proof anyone cannot be trusted alone. A coverage window labeled sober companion is a stored service name, not proof anyone needed a companion. A sober-companion booking is not proof anyone cannot be left alone. A page request is not proof anyone booked a slot. The page URL can say sober companion 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 intake pages, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a clinical-care claim, a rehab-facility claim, a sober-living-housing claim, a gambling-counseling claim, a HIPAA claim, a 42 CFR Part 2 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 sober-companion bookings, intake answers, and page tags go
Sober-companion bookings and forms handled on your WordPress site
Check which relapse-history, triggers, family-member-payer, client-name, coverage-window, 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 coverage window ends. Notification emails can also copy the same relapse history, triggers, family-member-payer names, client names, coverage windows, and phone numbers off-site. One table can name a relapse-history answer, a trigger, a family member paying the invoice, and a client name next to a coverage window, even when no companion is present. The appointments list can show which hours this week a client is booked not to be alone. Ask your web vendor not to collect a relapse-history answer next to a name, a trigger, and a family-member-payer on the first public form, not to store those answers next to a coverage window in one open submissions list, and to purge unused pairings after the window ends. A privacy-policy page does not by itself limit who can export an intake list. A stored relapse-history answer is not proof of relapse.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the sober-companion booking or intake page. That page request can reach a vendor host before anyone submits. The page URL can say sober companion 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 relapse-history answers or coverage windows. A "certified recovery escort" badge is not a verified storage path.
Sober-companion 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 recovery-escort or sober-companion 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 sober-companion appointment is a booking you create; a service name such as sober companion, recovery escort, or hours-alone coverage is a label you configure. Neither is a documented default. The stored service name can say sober companion in plain text before anyone arrives. Relapse-history, triggers, family-member-payer, client-name, coverage-window, or phone questions are custom fields you add (textarea, select, or input); they are not documented defaults. A relapse-history answer is a stored field, not proof of relapse. A trigger answer is a stored preference, not proof anyone used. A family-member-payer is a stored billing contact, not proof anyone is paying. A Friday 6pm-midnight slot is a stored booking window, not proof anyone cannot be trusted alone. A coverage window labeled sober companion is a stored service name, not proof anyone needed a companion. A booked slot is not proof anyone cannot be left alone, and is not proof a companion was present. Cancelling or ending the coverage window later does not erase the relapse-history answer, trigger, family-member-payer, or name already stored next to a coverage window, and does not unsend a confirmation email already delivered. How long that pairing sits after a booking that never produced a shift is not a documented default of the plugin. The appointments list can show which hours this week a client is booked not to be alone. 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. | Sober-companion bookings, custom coverage-window 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. Relapse-history, triggers, family-member-payer, client-name, coverage-window, or phone questions are fields you add; they are not documented defaults. Intake PDFs and ID photos are files you accept; those file types are not documented defaults. A relapse-history answer is a stored field, not proof of relapse. A trigger answer is a stored preference, not proof anyone used. A family-member-payer is a stored billing contact, not proof anyone is paying. A coverage window labeled sober companion is a stored service name, not proof anyone needed a companion. A sober-companion booking is not proof anyone cannot be left alone. 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 coverage window ends is not a documented default of the plugin. | Sober-companion intake 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 relapse-history, trigger, family-member-payer, or client-name field was sent. A page request from this script on a sober-companion intake page is not proof anyone booked a slot, and a pre-consent tag on that page can still treat sober-companion interest as an audience segment from the URL alone. The page URL can say sober companion even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and intake pages. Keep marketing tags off those pages if you do not want that page request. A tagged intake page can re-confirm sober-companion interest next to a stored coverage window; this row does not claim a companion was present 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. Relapse-history, triggers, family-member-payer, client-name, coverage-window, or phone fields often depend on the fields you configure. A relapse-history answer is a stored field, not proof of relapse. A trigger answer is a stored preference, not proof anyone used. A family-member-payer is a stored billing contact, not proof anyone is paying. A Friday 6pm-midnight slot is a stored booking window, not proof anyone cannot be trusted alone. A coverage window labeled sober companion is a stored service name, not proof anyone needed a companion. A sober-companion booking is not proof anyone cannot be left alone. A marketing-tag page request is not proof anyone booked a slot. The page URL can say sober companion even when no form is submitted. The relapse-history answer, the trigger, the family-member-payer, and the name can sit after a coverage window ends. This page is about a calendar that marks the hours a client cannot be alone, not an addiction-treatment admissions inquiry, not a rehab-facility intake, not a sober-living house application, and not a gambling-addiction counseling form. Ask your web vendor who can open entries, whether a marketing tag loads on the booking or intake page, and how long records and backups are kept. A "certified recovery escort" 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-care, rehab-facility, sober-living-housing, gambling-counseling, HIPAA, or 42 CFR Part 2 claims. Review stored records, connected services, exports, notification emails, marketing tags on booking and intake pages, and backups.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress membership plugin privacy
- WordPress SMS plugin privacy
- All privacy guides
/wp-sober-companion-plugin-privacy