Co-parenting class plugin privacy

The enrollment that files the custody fight under both parents' names

A co-parenting-class enrollment form can store the family-court case number, the children's names and ages, and the other parent next to the person who filled it in. The other parent is a named third party who may never visit the site. A certificate-of-completion request can sit in the same row as that case number. Class dates in an appointments list can timestamp the divorce for anyone who can open the table. Two parents ordered to the same course often enroll on the same site, and one case-number column can list both of them next to the same children. Family-court-case-number, child-name, child-age, other-parent-name, enrollee-name, class-date, certificate-request, and phone fields are configured, not documented defaults. A family-court case number is a stored note, not a court record. A child name is a stored name, not proof of custody. A child age is a stored number, not a birth record. An other-parent name is a stored third-party name, not proof that person enrolled or was served. An enrollee name is a stored name, not proof a class was completed. A class date is a stored booking, not proof a session was attended. A certificate request is a stored form answer, not a certified court document. Two rows that share a case number are stored enrollments, not proof the two parents were ordered together. A page request is not proof anyone enrolled. The page URL can say co-parenting class 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 enrollment pages, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a court-order claim, a custody claim, a divorce-lawyer claim, a supervised-visitation claim, a traffic-school claim, an anger-management claim, a HIPAA 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 co-parenting-class enrollments, bookings, and page tags go

Co-parenting-class enrollments and forms handled on your WordPress site

Check which family-court-case-number, child-name, child-age, other-parent-name, enrollee-name, class-date, certificate-request, 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 an enrollment that never produced a certificate. Notification emails can also copy the same case numbers, child names, other-parent names, enrollee names, class dates, and certificate requests off-site. One table can name the enrollee, the other parent, and the children next to a case number, even when the class is never finished. Two enrollments that share a case number can sit in the same submissions list. Ask your web vendor not to collect an other-parent name next to a child name and a case number on the first public form, not to store those answers next to a class date in one open submissions list, and to purge unused pairings after the class date passes. A privacy-policy page does not by itself limit who can export an enrollment list. A stored other-parent name is not proof that person enrolled or was served.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the co-parenting-class enrollment or booking page. That page request can reach a vendor host before anyone submits. The page URL can say co-parenting class even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off enrollment and booking pages if you do not want that page request. A browser scan cannot inspect stored case numbers, child names, or other-parent names. A "court-approved parenting class" badge is not a verified storage path.

Co-parenting-class enrollment, booking, 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 parenting-class, court-education, or divorce-education LMS tools 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). 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 co-parenting-class appointment is a booking you create; a service name such as parenting class, divorce education, or court-ordered session is a label you configure. Neither is a documented default. The stored service name can say co-parenting class in plain text before anyone attends. Family-court-case-number, child-name, child-age, other-parent-name, enrollee-name, class-date, or certificate-request questions are custom fields you add (textarea, select, or input); they are not documented defaults. A family-court case number is a stored note, not a court record. A child name is a stored name, not proof of custody. A child age is a stored number, not a birth record. An other-parent name is a stored third-party name, not proof that person enrolled or was served. An enrollee name is a stored name, not proof a class was completed. A class date is a stored booking, not proof a session was attended. A certificate request is a stored form answer, not a certified court document. Two bookings that share a case number are stored enrollments, not proof the two parents were ordered together. Cancelling or missing the slot later does not erase the case number, child name, other-parent name, or enrollee already stored next to a class date, and does not unsend a confirmation email already delivered. How long that pairing sits after a booking that never produced a certificate is not a documented default of the plugin. The appointments list can show who is booked this week and which case numbers repeat. 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.

Co-parenting-class bookings, custom enrollment fields, and automatic confirmation emails 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. Family-court-case-number, child-name, child-age, other-parent-name, enrollee-name, class-date, or certificate-request questions are fields you add; they are not documented defaults. Court-order PDFs and ID photos are files you accept; those file types are not documented defaults. A family-court case number is a stored note, not a court record. A child name is a stored name, not proof of custody. A child age is a stored number, not a birth record. An other-parent name is a stored third-party name, not proof that person enrolled or was served. An enrollee name is a stored name, not proof a class was completed. A class date is a stored booking, not proof a session was attended. A certificate request is a stored form answer, not a certified court document. Two form entries that share a case number in one submissions list can name both parents next to the same children, even when only one parent filled the form. 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 an enrollment that never produced a certificate is not a documented default of the plugin.

Co-parenting-class enrollment 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 family-court-case-number, child-name, other-parent-name, or enrollee-name field was sent. A page request from this script on a co-parenting-class enrollment page is not proof anyone enrolled, and a pre-consent tag on that page can still treat co-parenting-class interest as an audience segment from the URL alone. The page URL can say co-parenting class even when no form is submitted. Consent timing has not been tested. Review which tags you enable on enrollment and booking pages. Keep marketing tags off those pages if you do not want that page request. A tagged enrollment page can re-confirm co-parenting-class interest next to a stored case number; this row does not claim a class was completed from that request.

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. Family-court-case-number, child-name, child-age, other-parent-name, enrollee-name, class-date, or certificate-request fields often depend on the fields you configure. A family-court case number is a stored note, not a court record. A child name is a stored name, not proof of custody. A child age is a stored number, not a birth record. An other-parent name is a stored third-party name, not proof that person enrolled or was served. An enrollee name is a stored name, not proof a class was completed. A class date is a stored booking, not proof a session was attended. A certificate request is a stored form answer, not a certified court document. Two rows that share a case number are stored enrollments, not proof the two parents were ordered together. A marketing-tag page request is not proof anyone enrolled. The page URL can say co-parenting class even when no form is submitted. The case number, the child names, and the other parent can sit after a class that was never completed. This page is about an enrollment form that names both parents and the children in one row, not a traffic-school ticket enrollment, not a supervised-visitation calendar, not an anger-management referral, and not a divorce-lawyer intake. Ask your web vendor who can open entries, whether a marketing tag loads on the enrollment or booking page, and how long records and backups are kept. A "court-approved parenting class" 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 court-order, custody, divorce-lawyer, supervised-visitation, traffic-school, or anger-management claims. Review stored records, connected services, exports, notification emails, marketing tags on enrollment and booking pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-co-parenting-class-plugin-privacy