Orthodontist plugin privacy

The before-and-after photos of a child's face, stored where the contact form keeps its attachments

An orthodontist booking page can look like a calendar and a short consult form. The same form often asks for the child's name and age, the school (because adjustments land on early-release days), habits such as thumb-sucking, previous dental work, and a payment-plan selection — a family-finance fact sitting next to a smile photo — and stores those answers next to the parent's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a child's face next to a payment plan and a marketing pixel — the before-and-after photos of a child's face, stored where the contact form keeps its attachments, typed once into a vendor table next to a newsletter signup. A consult booking is not a treatment plan. A smile photo is a picture of a minor in a site uploads folder, not a clinical imaging record. A habits answer is the parent's account, not a diagnosis. A payment-plan selection is a family-finance fact, not a credit record. A page request is not proof any child wears braces. The page URL can say orthodontist even when no form is submitted. Ask what happens to the smile photo and the school field after the visit — the photos stay where the contact form keeps its attachments, and the row outlives the appointment. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, an orthodontic-outcomes or treatment-necessity claim, a dental-board-licensing claim, an insurance or HSA coverage claim, a children's-privacy-law (COPPA) compliance 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, bookings, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.

Where consult bookings, intake notes, and page tags go

Bookings and notes on your WordPress site

Check which patient-name-and-age, school, habits, previous-dental-work, or payment-plan fields you enable, who can open form entries and consult or adjustment bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the before-and-after photos of a child's face are stored where the contact form keeps its attachments. Notification emails can also copy those fields off-site. One table can list every consult next to a school name and a smile JPEG. Ask your web vendor not to keep smile-photo uploads next to payment-plan selections in one open submissions list longer than operations need, and to purge intake rows when the booking ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not a treatment plan. A habits answer is not a diagnosis.

Page tags handled by a vendor

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

Consult / adjustment booking, orthodontist 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 orthodontic practice-management and imaging SaaS platforms without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
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 consult slot or an adjustment visit is a booking you create; a service name such as new-patient consult, wire adjustment, or retainer check is a label you configure. Neither is a documented default. Patient-name-and-age, school, habits, previous-dental-work, or payment-plan questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not a treatment plan — and a CSV export of a consult next to a school name and early-release notes is still a calendar that reconstructs a school week beside the before-and-after photos of a child's face. 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.

Consult and adjustment bookings 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. Patient-name-and-age, school, habits, previous-dental-work, or payment-plan questions are fields you add; they are not documented defaults. Completing the form can store a patient-name-and-age answer next to a school field, a habits answer, previous dental work, a payment-plan selection, and optional smile-photo or referral uploads — typed once as the before-and-after photos of a child's face, stored where the contact form keeps its attachments, into the same tables as a newsletter signup. A consult booking is not a treatment plan. A smile photo is a picture of a minor in a site uploads folder, not a clinical imaging record. A habits answer is the parent's account, not a diagnosis. A payment-plan selection is a family-finance fact, not a credit record — and a staff login can open "Maya, 12, Lincoln Middle, thumb-sucking until age 8, 24-month plan" next to a smile JPEG beside everyone else's resume. 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.

Orthodontist intake entries stored in WordPress; optional smile-photo and referral 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 patient-name-and-age, school, habits, previous-dental-work, or payment-plan field was sent. A page request from this script is not proof any child wears braces. The page URL can say orthodontist even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and intake 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. Patient-name-and-age, school, habits, previous-dental-work, or payment-plan fields often depend on the fields you configure. A consult booking is not a treatment plan. A smile photo is a picture of a minor in a site uploads folder, not a clinical imaging record. A habits answer is the parent's account, not a diagnosis. A payment-plan selection is a family-finance fact, not a credit record. A marketing-tag page request is not proof any child wears braces. The page URL can say orthodontist even when no form is submitted. The before-and-after photos of a child's face, stored where the contact form keeps its attachments — that is a storage path next to a payment plan, not a feature these plugins claim. This page is about that orthodontist consult intake, not a daycare roster, a summer-camp registration, an allergy-clinic child intake, or a genetic-counseling pedigree. Ask your web vendor who can open entries, whether a marketing tag loads on the booking page, and how long records and backups are kept. A "braces ready" 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 orthodontic outcomes or treatment necessity, dental-board licensing, insurance or HSA coverage, or children's-privacy-law (COPPA) compliance status. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking pages, and backups.

Documentation snapshot: Oct 14, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-orthodontist-plugin-privacy