Dental intake privacy

The medical history behind the appointment reminder

Dental practices on WordPress can use booking or clinic plugins for appointment requests, patient records, and intake forms. Those records can include medical histories, insurance details, and appointment patterns you configure. An appointment-reminder email alone can reveal a patient relationship. This sample reviews three plugins' documentation. Check which fields you collect, who can open records, where vendor hosts store submissions, and how long booking or patient rows and backups are kept.

Documentation review only. This is not legal advice, clinical advice, or a HIPAA, 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, patient records, staff permissions, vendor accounts, or backups.

Where dental intake answers are stored

Answers stored on your WordPress site

Check which booking or patient fields you enable, who can open entries, and how long records and backups are kept. Notification and reminder emails can also copy the same answers — or reveal a patient relationship — off-site.

Answers stored by a vendor

Some tools send intake submissions into a vendor cloud vault. Review access and retention there. A browser scan cannot inspect those stored submissions.

Dental booking and intake 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 dental practice-management SaaS tools without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Dental Focus

Documented dental-clinic WordPress plugin (version 2.8.0) with a drag-and-drop form builder for appointment requests, new patient registrations, treatment enquiries, and surveys. The listing states every form submission is stored in the WordPress database under Dental Focus > Submissions, with CSV export and per-form email notifications. Supported free field types include text, email, phone, textarea, dropdown, checkboxes, radio, and date — medical-history, insurance, or imaging questions depend on the fields you configure; they are not fixed dental chart defaults. File or X-ray upload fields are not listed among those free field types. Portfolio before/after images are staff-published media, not private chart uploads. Optional GDPR consent checkbox settings are described; retention of submission rows is not specified as a default purge. Public form browser hosts are unverified.

Dental appointment and intake form submissions stored in WordPressBrowser hosts not verifiedNot assessedNot tested
  • None
KiviCare – Clinic & Patient Management System (EHR)

Documented self-hosted clinic EHR (plugin version 4.5.6) with patient records management, encounter (visit) tracking, custom fields, and a patient portal that can expose medical history. Role-based access includes clinic admin, doctor, receptionist, and patient. Which medical-history, insurance, appointment-pattern, or imaging fields you collect depends on the services and custom fields you configure — they are not established as fixed dental defaults by the listing. Optional Pro connectors (Google Calendar, SMS/WhatsApp, telemed addons, WooCommerce payments) can send appointment or notification data off-site when enabled; those paths were not assessed as free-version defaults. Retention of patient or encounter rows is not assessed here. Browser hosts for the public booking widgets were not verified for this snapshot.

Patient records, encounters, and medical history stored on your WordPress siteBrowser hosts not verifiedNot assessedNot tested
  • None
HIPAAtizer

Documented WordPress embed for the HIPAAtizer SaaS (plugin version 1.3.10). The listing states Protected Health Information collected through embedded forms is stored in vendor cloud vaults, not as ordinary WordPress form-entry tables; forms are added via Gutenberg block, shortcode, or embed after connecting a HIPAAtizer account. Listing tags include dental forms among supported uses. Which medical-history, insurance, imaging, or consent questions appear depends on the form you build or convert — they are not established as fixed dental defaults by the listing. This row describes the documented storage path only and does not assess legal or regulatory compliance status. Review vendor account access, retention, and any BAA or plan terms separately. Browser hosts for the embed were not verified for this snapshot.

Dental intake form submissions stored in a vendor cloud vaultBrowser hosts not verifiedNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Medical-history, insurance, imaging, or X-ray questions often depend on the fields you configure. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess legal compliance status or give clinical advice. Review stored records, connected services, exports, notification emails, and backups.

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

Related pages

Scan your site for third-party requests

/wp-dental-plugin-privacy