Lice removal plugin privacy
Where does the booking that names your kid's school on the day you found lice go?
A lice-removal or in-home lice-service booking can ask for the child's name and age, the school and classroom, household size, and how long ago you noticed — because clinics ask where it came from and who else needs checking. One row can embarrass three parties at once: a named minor, a family, and a school whose name now sits next to an infestation date in a strip-mall clinic's WordPress tables. Parents book these appointments so nobody finds out; the form is the record that someone could. A marketing tag on the same page can send a page request to a vendor host before anyone submits. A page request is not proof that a child or school was named. A booking is not a confirmed infestation. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries, where uploaded files land, which tags load on the booking page, and how long records, files, and backups are kept.
Documentation review only. This is not legal advice, a public-health reporting assessment, a school-notification-law assessment, a treatment-outcome 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 child names, school fields, and page tags go
Entries and bookings handled on your WordPress site
Check which child-name, age, school, classroom, household, or noticed-date fields you enable, who can open form entries and bookings, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after a booking that never became a treatment. Notification emails can also copy the same answers off-site. Ask your web vendor not to collect a school name next to a child's name on the first public form, and not to store classroom or household fields in one open submissions list.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the lice-removal booking page. That page request can reach a vendor host before anyone submits — and a third party can learn that someone sought lice treatment. Review which tags you enable, account access, and retention there. Keep marketing tags off booking pages if you do not want that page request. A browser scan cannot inspect stored form entries. A "secure client forms" badge is not a verified storage path.
Lice-removal booking, form, 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 clinic 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 booking and intake (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 same-day lice-treatment or in-home visit slot is a booking you create; a service name such as lice removal is a label you configure. Neither is a documented default. Child name, age, school, classroom, household size, or noticed-date fields are custom fields you add (textarea, select, or input); they are not documented defaults. A booking is not a confirmed infestation. Notes can name a school that never consented to being listed next to an infestation date. 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. | Treatment-slot 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. Child name, age, school, classroom, household size, or noticed-date questions are fields you add; they are not documented defaults. Scalp photos or school-nurse notes attached to a booking are files you accept; they are not documented defaults. One booking entry can store a child's name next to a school on the day lice were found. A booking is not a confirmed infestation. 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 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 child name, school, classroom, or noticed date was sent. A page request from this script is not proof that a child or school was named. Consent timing has not been tested. Review which tags you enable on lice-removal booking 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. Child names, schools, classrooms, household sizes, or noticed dates often depend on the fields you configure. A booking is not a confirmed infestation. A marketing-tag page request is not proof that a child or school was named. A school named in the form may never have consented to being an outbreak record. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking page, and how long records and backups are kept. A "secure" or "client forms" 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 public-health reporting duties, school-notification rules, or treatment outcomes. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking pages, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress pediatric dentist plugin privacy
- WordPress daycare plugin privacy
- WordPress summer camp plugin privacy
- All privacy guides
/wp-lice-removal-plugin-privacy