Pediatric dentist plugin privacy

Where does the new-patient form about someone too young to consent go?

A pediatric new-patient or booking form can collect a child's date of birth, health history, medications, behavioral or anxiety notes, and insurance member ID — typed by a parent into a local-first form or booking plugin. File fields can store insurance-card or referral scans in the site uploads folder. The data subject cannot consent. The row can quietly outlive childhood in a plugin table. A marketing tag on the same booking page can send a page request to a vendor host before anyone submits. A page request is not proof that a child's DOB or insurance ID was collected. This sample reviews three plugins' documentation. Check which fields you collect, who can open bookings and 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 or medical advice, a COPPA or HIPAA review, a treatment outcome, 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 bookings, form entries, uploaded insurance cards, email inboxes, staff permissions, vendor accounts, or backups.

Where bookings, child intake answers, and page tags go

Bookings and files handled on your WordPress site

Check which child-DOB, health-history, medication, behavioral, or insurance fields you enable, who can open bookings and form entries, where uploaded insurance cards live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after childhood. Notification emails can also copy the same answers off-site. Ask your web vendor not to collect full health histories on the first public form, and to purge bookings that never became patients.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the pediatric new-patient booking 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 booking pages if you do not want that page request. A browser scan cannot inspect stored form entries. A "secure patient forms" badge is not a verified storage path.

Pediatric-dentist booking, form-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 pediatric dental software without a WordPress.org listing is outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Easy Appointments

Documented self-hosted appointment plugin marketed for clinics and health practices (plugin version 4.0.3). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. Child date of birth, health history, medications, behavioral or anxiety notes, or insurance member ID are custom fields you add (textarea, select, or input); they are not documented defaults. A booking entry is not a dental record. The subject of those fields is often a child who never consented — a parent typed them. 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 and does not guarantee childhood-length retention limits. Google Calendar, SMS, and payments are Pro. Google reCAPTCHA is optional. Public booking-form browser hosts are unverified.

New-patient bookings and custom intake fields stored 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. Child DOB, health history, medications, behavioral notes, or insurance questions are fields you add; they are not documented defaults. Insurance-card or referral scans are files you accept; they are not documented defaults. A form entry is not a finished dental exam. Entries can quietly outlive childhood in plugin tables. 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 a child's DOB or insurance ID was sent. A page request from this script on a pediatric new-patient booking page is not proof that a child's health details were collected — and a pre-consent tag on that page can still treat pediatric-care intent as an audience segment. Consent timing has not been tested. Review which tags you enable on new-patient and booking 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 dates of birth, health-history answers, medications, behavioral notes, insurance member IDs, or insurance-card files often depend on the fields you configure. A booking entry is not a dental record. A form entry is not a finished exam. A marketing-tag page request is not proof that a child's DOB or insurance ID was collected. Ask your web vendor who can open bookings and 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 "patient 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 COPPA, HIPAA, 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

Scan your site for third-party requests

/wp-pediatric-dentist-plugin-privacy