ESL school plugin privacy
The placement form that writes down what you can't yet say for yourself
An ESL school's site can look like a class calendar and a short placement form. The same form often asks for a first language, country of origin, years in the US, the employer whose shifts the classes must fit around, a goal, and an emergency contact — and asks for a prior certificate — and stores those answers next to the student's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a placement-test booking next to a goal sentence, a country-of-origin field, an employer-and-shift note, an emergency-contact line that names which child speaks English, and a marketing pixel — the placement form that writes down what you can't yet say for yourself, typed once into a vendor table next to a newsletter signup. An enrollment is not an immigration record and says nothing about status. A country-of-origin answer is biography the student chose to share, not a legal fact about anyone. A goal is an aspiration, not an application filed anywhere. An employer field is shift logistics, not a workplace report. The emergency contact named never touched the form. An uploaded certificate is a stored document, not a verified credential. A page request is not proof of anyone's language or origin. The page URL can say ESL even when no form is submitted. Ask what happens to the prior-certificate uploads and goal rows after the Tuesday-night class is scheduled — the quietest field is the emergency-contact note that records, in one line, which child is the family's interpreter. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the intake page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, an immigration-law or status claim, a USCIS or citizenship-test claim, a school-accreditation claim, a teaching-efficacy claim, a claim about the school's data-security practices, a provider-quality 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 placement-test bookings, enrollment goals, and page tags go
Bookings and notes on your WordPress site
Check which first-language, country-of-origin, years-in-us, employer-and-shift, goal, or emergency-contact fields you enable, who can open form entries and placement-test or class-registration bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a Tuesday-night class is scheduled — when the placement form that writes down what you can't yet say for yourself. Notification emails can also copy those fields off-site. One table can list every placement next to a prior-certificate upload and a goal sentence. Ask your web vendor not to keep prior-certificate uploads next to plaintext goal and emergency-contact rows in one open submissions list longer than operations need, and to purge intake rows when the class is no longer active. A privacy-policy page does not by itself limit who can open a submissions list — and the people those rows describe are often the site's least equipped to read it. A stored booking is not an enrollment. A goal sentence in a form table is not an application the plugin claims to file.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the ESL placement-test or enrollment-intake page. That page request can reach a vendor host before anyone submits. The page URL can say ESL even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off placement-test, class-registration, and ESL enrollment-intake pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "trusted school partner" badge is not a verified storage path.
Placement-test / class-registration booking, ESL enrollment 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. Specialty school-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 Tuesday-night placement test, a class-registration slot, or a makeup-class booking is a booking you create; a service name such as placement test, class registration, or evening ESL is a label you configure. Neither is a documented default. First-language, country-of-origin, years-in-us, employer-and-shift, goal, or emergency-contact questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not an enrollment — and a CSV export of a placement-test row next to a first language and a goal note is still a calendar that holds a biography beside a contact name. An enrollment is not an immigration record and says nothing about status. Emails can include those custom fields and copy the appointment off-site. 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. | Placement-test and class-registration bookings 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. First-language, country-of-origin, years-in-us, employer-and-shift, goal, or emergency-contact fields are fields you add; they are not documented defaults. Completing the form can store a goal sentence next to a first language, a country of origin, years in the US, an employer-and-shift note, an emergency contact, and optional prior-certificate uploads — typed once as the placement form that writes down what you can't yet say for yourself, into the same tables as a newsletter signup. An enrollment is not an immigration record and says nothing about status. A country-of-origin answer is biography the student chose to share, not a legal fact about anyone. A goal is an aspiration, not an application filed anywhere. An employer field is shift logistics, not a workplace report. The emergency contact named never touched the form — and a staff login can open "Spanish, Mexico, 4 years, night-shift kitchen, pass citizenship interview, my son — he speaks English, prior-cert.pdf" next to everyone else's resume. An uploaded certificate is a stored document, not a verified credential. Notification emails can copy field values and files off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | ESL enrollment intake stored in WordPress; optional prior-certificate 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 first-language, country-of-origin, years-in-us, employer-and-shift, goal, or emergency-contact field was sent. A page request from this script is not proof of anyone's language or origin. The page URL can say ESL even when no form is submitted. Consent timing has not been tested. Review which tags you enable on placement-test, class-registration, and ESL enrollment-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. First-language, country-of-origin, years-in-us, employer-and-shift, goal, or emergency-contact fields often depend on the fields you configure. An enrollment is not an immigration record and says nothing about status. A country-of-origin answer is biography the student chose to share, not a legal fact about anyone. A goal is an aspiration, not an application filed anywhere. An employer field is shift logistics, not a workplace report. The emergency contact named never touched the form. An uploaded certificate is a stored document, not a verified credential. A marketing-tag page request is not proof of anyone's language or origin. The page URL can say ESL even when no form is submitted. The placement form that writes down what you can't yet say for yourself — that is a storage path next to a prior-certificate upload, not a feature these plugins claim. This page is about that ESL enrollment intake, not an immigration legal story, an immigration-lawyer passport scan, an adult-literacy native-language form, or an interpreter language disclosure. Ask your web vendor who can open entries, whether a marketing tag loads on the intake page, and how long goal rows and backups are kept after the Tuesday-night class is scheduled. A "trusted school partner" 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 immigration law or status, USCIS or citizenship-test procedure, school accreditation, teaching efficacy, the school's data-security practices, or provider quality. Review stored records, bookings, connected services, exports, notification emails, marketing tags on intake pages, and backups.
Documentation snapshot: Oct 14, 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-esl-school-plugin-privacy