Wilderness therapy plugin privacy

Where does the enrollment form filled out while the child sleeps go?

Wilderness-therapy and teen residential programs enroll a minor through a parent-authored WordPress appointment or intake form — often filled out while the child is asleep and must not learn the row exists until transport day. The parent is the author; the fields are the parent's worst allegations about their own child: drug use, self-harm, running away, diagnoses, current school, and a recent photo for the transport team. Those answers sit in a local-first booking or form plugin behind one admin login. The row is an accusation written by the person the child trusts most, and it persists whether or not the child is ever enrolled. A marketing tag on the same enrollment page can send a page request to a vendor host before anyone submits — and that page request alone can treat wilderness-therapy intent as an audience segment from the URL. A page request is not proof anyone enrolled. An enrollment booking is not proof a child was transported. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where uploaded files land, which tags load on the enrollment page, and how long records, files, and backups are kept.

Documentation review only. This is not legal advice, a teen-transport-legality claim, a custody-law claim, a program-outcome 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 enrollment answers, visitor fields, and page tags go

Entries and bookings handled on your WordPress site

Check which parent-name, minor-name, behavior, diagnosis, school, or transport-photo fields you enable, who can open form entries and assessment-call bookings, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after an enrollment that was cancelled, declined, or never completed. Notification emails can also copy the same parent identity, minor identity, and enrollment answers off-site. Ask your web vendor not to store a behavior allegation next to a minor's name in one open submissions list when a short visit ID would do.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the wilderness-therapy enrollment page. That page request can reach a vendor host before anyone submits. Review which tags you enable, account access, and retention there. Keep marketing tags off enrollment pages if you do not want that page request. A browser scan cannot inspect stored form entries or uploaded files. A "confidential intake" badge is not a verified storage path.

Wilderness-therapy enrollment, assessment-call, 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. Clinical EHR platforms without a WordPress.org listing are 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A wilderness-therapy assessment call or enrollment booking is a booking you create; a service name such as parent assessment or intake call is a label you configure. Neither is a documented default. Parent name, minor name, behavior, diagnosis, school, or transport-photo questions are custom fields you add (textarea, select, input, or file); they are not documented defaults. An enrollment booking is not proof a child was transported. Cancelling later does not erase the behavior or diagnosis answer already stored next to a minor's 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.

Assessment-call bookings and custom enrollment fields stored 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. Parent name, minor name, behavior, diagnosis, school, or recent-photo-for-transport questions are fields you add; they are not documented defaults. A transport-team photo is a file you accept; it is not a documented default. One enrollment entry can store a minor's name next to a parent's allegations and a photo upload. A submitted form is not proof a child was transported. 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.

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 minor name, behavior answer, or transport photo was sent. A page request from this script on a wilderness-therapy enrollment page is not proof anyone enrolled — and a pre-consent tag on that page can still treat wilderness-therapy intent as an audience segment from the URL alone. The page URL can say wilderness therapy even when no form is submitted. Consent timing has not been tested. Review which tags you enable on parent enrollment pages.

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. Parent names, minor names, behavior or diagnosis answers, school names, or transport-photo uploads often depend on the fields you configure. An enrollment booking is not proof a child was transported. A marketing-tag page request is not proof anyone enrolled. Cancelling later does not erase the behavior answer already stored next to a minor's name. The parent authors the row about a child who is designed not to know it exists yet. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the enrollment page, and how long records and backups are kept. A "confidential intake" 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 teen-transport legality, custody law, or program outcomes. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on enrollment pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-wilderness-therapy-plugin-privacy