Denture clinic plugin privacy

The photo of your younger smile, uploaded so the lab can copy it

A denture clinic booking page can look like a calendar and a short intake form. The same form often asks for current situation (full upper, partial lower, immediate-after-extraction), extraction history (which teeth went, and when), sore spots or fit problems, and years wearing dentures — and asks for a photograph of the natural smile so the lab can copy it — and stores those answers next to the patient's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a wedding-day smile JPEG next to an extraction year and a marketing pixel — the photo of your younger smile, uploaded so the lab can copy it, typed once into a vendor table next to a newsletter signup. An impression booking is not a treatment outcome. An extraction-history answer is the patient's recollection, not a dental chart. A fit-problem note is the wearer's description, not a clinical finding. An uploaded smile photo is a family photograph in a site uploads folder, not a lab record. A page request is not proof anyone wears dentures. The page URL can say denture clinic even when no form is submitted. Ask what happens to the smile photo and the extraction-history field after the visit — the photo of your younger smile stays 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, a denture-fit or lab-quality claim, a dental-board-licensing claim, a Medicare or insurance coverage claim, an adhesive or material-safety 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 current-situation, extraction-history, sore-spots-or-fit-problems, or years-wearing-dentures fields you enable, who can open form entries and consult, impression, or fitting bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the photo of your younger smile is uploaded so the lab can copy it. Notification emails can also copy those fields off-site. One table can list every impression next to an extraction year and a wedding-day JPEG. Ask your web vendor not to keep smile-photo uploads next to extraction-history answers 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 outcome. A fit-problem note is not a clinical finding.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the denture clinic booking page. That page request can reach a vendor host before anyone submits. The page URL can say denture clinic 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 "new smile ready" badge is not a verified storage path.

Consult / impression / fitting booking, denture 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 denture lab and CAD-CAM 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, an impression visit, or a fitting is a booking you create; a service name such as new-patient consult, alginate impression, or try-in fitting is a label you configure. Neither is a documented default. Current-situation, extraction-history, sore-spots-or-fit-problems, or years-wearing-dentures questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not a treatment outcome — and a CSV export of an impression next to an extraction year and a full-upper checkbox is still a calendar that dates tooth loss beside the photo of your younger smile. 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, impression, and fitting 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. Current-situation, extraction-history, sore-spots-or-fit-problems, or years-wearing-dentures questions are fields you add; they are not documented defaults. Completing the form can store a current-situation answer next to an extraction-history field, a sore-spots-or-fit-problems note, years-wearing-dentures, and optional smile-photo or prior-denture-photo uploads — typed once as the photo of your younger smile, uploaded so the lab can copy it, into the same tables as a newsletter signup. An impression booking is not a treatment outcome. An extraction-history answer is the patient's recollection, not a dental chart. A fit-problem note is the wearer's description, not a clinical finding. An uploaded smile photo is a family photograph in a site uploads folder, not a lab record — and a staff login can open "full upper / partial lower, extractions 1998 and 2011, sore ridge left, 12 years wearing, wedding-day JPEG" next to a prior-denture snapshot 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.

Denture-clinic intake entries stored in WordPress; optional smile-photo and prior-denture-photo 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 current-situation, extraction-history, sore-spots-or-fit-problems, or years-wearing-dentures field was sent. A page request from this script is not proof anyone wears dentures. The page URL can say denture clinic 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. Current-situation, extraction-history, sore-spots-or-fit-problems, or years-wearing-dentures fields often depend on the fields you configure. An impression booking is not a treatment outcome. An extraction-history answer is the patient's recollection, not a dental chart. A fit-problem note is the wearer's description, not a clinical finding. An uploaded smile photo is a family photograph in a site uploads folder, not a lab record. A marketing-tag page request is not proof anyone wears dentures. The page URL can say denture clinic even when no form is submitted. The photo of your younger smile, uploaded so the lab can copy it — that is a storage path next to an extraction year, not a feature these plugins claim. This page is about that denture-clinic intake, not an orthodontist consult for a child, a wig-salon fitting, a hearing-aid battery subscription, or a medical-alert household setup. 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 "new smile 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 denture fit or lab quality, dental-board licensing, Medicare or insurance coverage, or adhesive or material safety. 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-denture-clinic-plugin-privacy