Homeschool co-op plugin privacy

The application that explains why you left the school district

A homeschool co-op application can store a child name and age next to why the family left the school district. Answers can include an IEP that was not honored, bullying with the bully named, a medical condition, or a religious conviction. The family left the district to control that child record. The same answers can sit in a volunteer-run WordPress form behind one admin login. A marketing tag on the application page can send a page request to a vendor host before anyone submits. A page request is not proof a family homeschools. A submitted application is not enrollment. The page URL can say homeschool even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and files, which tags load on the application page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, an education-law claim, a truancy claim, a homeschool-legality 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, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.

Where exit reasons, transcripts, and page tags go

Applications and files handled on your WordPress site

Check which child-name, child-age, why-you-left, IEP, bully-name, medical, religious-conviction, or transcript-upload fields you enable, who can open form entries, which inboxes receive copies, and how long records, emails, and backups are kept. Notification emails can also copy the same answers off-site. One entry can store a child name and age next to why they left, and can name a bully who never filled out the form. Ask your web vendor not to collect why-you-left or bully-name fields on a public application, not to accept transcript or evaluation uploads on a public form, and to purge applications that never became enrollment. A privacy-policy page does not by itself limit who can open an application list on a volunteer-run site.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the application page. That page request can reach a vendor host before anyone submits. The page URL can say homeschool even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off application pages if you do not want that page request. A browser scan cannot inspect stored applications. A "confidential application" badge is not a verified storage path.

Homeschool co-op application, upload, 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 co-op or student-information software without a WordPress.org listing is outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Drag and Drop Multiple File Upload for Contact Form 7

Documented Contact Form 7 upload extension (plugin version 1.4.0). Version 1.4.0 drag-n-drop-upload-cf7.php defines wpcf7_dnd_dir as wp_dndcf7_uploads. The listing states the free version moves files to wp-content/uploads/wp_dndcf7_uploads, attaches them to mail, then removes them from that temporary folder about one hour after submission. That cleanup does not remove copies already sent as email attachments. Transcripts, evaluations, or IEP paperwork are files you accept; they are not documented defaults. An uploaded transcript is not an enrollment file. Pro documents saving to the Media Library, changing the upload directory, auto-delete timers, and remote storage to OneDrive, Google Drive, Amazon S3, Dropbox, or FTP. Public upload-page browser hosts are unverified.

Visitor files stored under wp-content/uploads/wp_dndcf7_uploadsBrowser 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. Child-name, child-age, why-you-left, IEP, bully-name, medical, or religious-conviction fields are fields you add; they are not documented defaults. One form entry can store a child name and age next to why the family left the school district, and can name a bully who never filled out the form. Completing the form can record an application. A submitted application is not enrollment. A staff login on a volunteer-run site can open the child name, the age, and the exit reason in the same submissions list. Notification emails can copy field values 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 child-name, why-you-left, or IEP fields were sent. A page request from this script is not proof a family homeschools. The page URL can say homeschool even when no form is submitted. Consent timing has not been tested. Review which tags you enable on application 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. Child-name, child-age, why-you-left, IEP, bully-name, medical, religious-conviction, or transcript-upload fields often depend on the fields you configure. A submitted application is not enrollment. An uploaded transcript is not an enrollment file. A marketing-tag page request is not proof a family homeschools. The page URL can say homeschool even when no form is submitted. This page is about the co-op application that records why a family left a school district, not daycare check-in or school attendance plugins. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the application page, and how long records and backups are kept. A "secure" or "confidential application" 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 education law, truancy, or homeschool legality. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on application 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-homeschool-coop-plugin-privacy