Special education advocate plugin privacy
Where does the intake that lists everything your child struggles with go?
Special-education advocates collect a parent-authored WordPress intake that aggregates diagnosis lists, medication lists, incident reports, evaluation history, IEP or evaluation PDF uploads, and the school district being fought into one row about a minor — the most complete child file in the series, typically held by a one-person advocacy shop on shared hosting. Other pages leak one fact about a child; here the family's entire case theory sits in a local-first form or booking plugin behind one admin login while the adversary already has lawyers. A marketing tag on the same intake page can send a page request to a vendor host before anyone submits — and that page request alone can treat special-education-advocate intent as an audience segment from the URL. A page request is not proof anyone sought advocacy. An intake submission is not proof a dispute was filed. 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 intake page, and how long records, files, and backups are kept.
Documentation review only. This is not legal advice, an IDEA or FERPA claim, a special-education-law claim, a district-liability 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 intake answers, visitor fields, and page tags go
Entries and bookings handled on your WordPress site
Check which parent-name, minor-name, diagnosis, medication, incident, evaluation, district, or IEP-PDF fields you enable, who can open form entries and consult bookings, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after an intake that was abandoned, declined, or never completed. Notification emails can also copy the same parent identity, minor identity, and aggregated answers off-site. Ask your web vendor not to store a diagnosis list next to a minor's name and a district 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 special-education-advocate intake 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 intake 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.
Special-education-advocate intake, consult-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. Case-management SaaS platforms 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A special-education-advocate consult or intake call is a booking you create; a service name such as IEP consult or parent intake is a label you configure. Neither is a documented default. Parent name, minor name, diagnosis, medication, incident, evaluation, or district questions are custom fields you add (textarea, select, input, or file); they are not documented defaults. A consult booking is not proof a dispute was filed. Cancelling later does not erase the diagnosis or district 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. | Consult bookings and custom intake fields stored 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. Parent name, minor name, diagnosis list, medication list, incident report, evaluation history, school-district name, or IEP/evaluation-PDF questions are fields you add; they are not documented defaults. An IEP draft or evaluation PDF is a file you accept; it is not a documented default. One intake entry can store a minor's name next to diagnosis, medication, incident, and district answers plus uploaded case documents — the aggregation is the story. A submitted form is not proof a dispute was filed. 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 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 minor name, diagnosis list, or IEP PDF was sent. A page request from this script on a special-education-advocate intake page is not proof anyone sought advocacy — and a pre-consent tag on that page can still treat special-education-advocate intent as an audience segment from the URL alone. The page URL can say special education advocate even when no form is submitted. Consent timing has not been tested. Review which tags you enable on parent intake pages. | 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. Parent names, minor names, diagnosis lists, medication lists, incident reports, evaluation history, school-district names, or IEP/evaluation PDF uploads often depend on the fields you configure. An intake submission is not proof a dispute was filed. A marketing-tag page request is not proof anyone sought advocacy. Abandoning later does not erase the diagnosis answer already stored next to a minor's name and a district name. The parent authors the aggregated dossier about a child. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the intake 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 IDEA, FERPA, special-education law, or district liability. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on intake pages, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-special-education-advocate-plugin-privacy