Supervised visitation plugin privacy

Where does the scheduling form that records a judge does not trust you alone with your child go?

A supervised visitation center's booking form has three data subjects in one row — the visiting parent, the custodial parent, and the child — and the row exists at all only because a court ordered supervision. The reason-for-supervision dropdown stores an allegation verbatim; the recurring booking pattern reconstructs the custody order; a cancellation note becomes an exhibit in the next hearing. Both parents can read the same site, and only one of them typed the row. Those answers sit in a local-first booking or form plugin behind one admin login. A marketing tag on the same scheduling page can send a page request to a vendor host before anyone submits — and that page request alone can treat custody-supervision intent as an audience segment from the URL. A page request is not proof of a custody case. A booking is not a court record. This sample reviews three plugins' documentation. Check which parent and child fields you collect, who can open entries, where uploaded files land, which tags load on the scheduling page, and how long records, files, and backups are kept.

Documentation review only. This is not legal advice, a family-court-procedure claim, a custody-law-outcome claim, a mandated-reporting assessment, a parental-fitness 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 scheduling answers, parent and child fields, and page tags go

Entries and bookings handled on your WordPress site

Check which visiting-parent, custodial-parent, child-name, reason-for-supervision, or cancellation-note fields you enable, who can open form entries and visitation-slot bookings, where uploaded court orders or parenting plans live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after a visit that was completed, cancelled, or never attended. Notification emails can also copy the same parent identities and allegation off-site. Ask your web vendor not to store a reason-for-supervision allegation next to a child 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 supervised-visitation scheduling 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 scheduling pages if you do not want that page request. A browser scan cannot inspect stored form entries or uploaded files. A "confidential" or "court-ordered" badge is not a verified storage path.

Supervised-visitation scheduling, 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. Case-management CRM 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 supervised visitation or parenting-exchange booking is a booking you create; a service name such as supervised visit or monitored exchange is a label you configure. Neither is a documented default. Visiting-parent, custodial-parent, child-name, reason-for-supervision, or cancellation-note questions are custom fields you add (textarea, select, or input); they are not documented defaults. A visitation booking is not a court record. Ending supervision later does not erase the reason-for-supervision allegation already stored next to a child name. The recurring booking pattern can reconstruct who had which hours. 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.

Visitation-slot bookings and custom intake 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. Visiting-parent, custodial-parent, child-name, reason-for-supervision, or cancellation-note questions are fields you add; they are not documented defaults. Court-order, parenting-plan, or ID uploads are files you accept; they are not documented defaults. One scheduling entry can store a visiting parent, a custodial parent, and a child next to a reason-for-supervision allegation. A submitted form is not a court record. 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 visiting-parent name, child name, or reason-for-supervision allegation was sent. A page request from this script on a supervised-visitation scheduling page is not proof of a custody case — and a pre-consent tag on that page can still treat custody-supervision intent as an audience segment from the URL alone. The page URL can say supervised visitation even when no form is submitted. Consent timing has not been tested. Review which tags you enable on scheduling 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. Visiting-parent names, custodial-parent names, children's names, reason-for-supervision answers, or cancellation notes often depend on the fields you configure. A booking is not a court record. A marketing-tag page request is not proof of a custody case. Ending supervision later does not erase the reason-for-supervision allegation already stored next to a child name. The recurring booking pattern can reconstruct who had which hours. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the scheduling page, and how long records and backups are kept. A "confidential" or "court-ordered" 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 family-court procedure, custody-law outcomes, mandated reporting, or parental fitness. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on scheduling 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-supervised-visitation-plugin-privacy