Optometrist plugin privacy

The eye-exam intake that asks about everything except your eyes

An optometrist booking page can look like a calendar and a short intake form. The same form often asks for diabetes or blood-pressure status, a full medications list, family eye history that names relatives who never saw the form, night-driving difficulty, and a current prescription — and asks for a prior-Rx photo or insurance-card scan — 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 an annual exam booking next to a diabetes checkbox, a night-driving answer, and a marketing pixel — the eye-exam intake that asks about everything except your eyes, typed once into a vendor table next to a newsletter signup. An exam booking is not a diagnosis. A diabetes checkbox is the patient's answer, not an endocrine record. A family-history field names third parties who never consented. A night-driving answer is a self-description, not a fitness-to-drive finding. An uploaded prescription is a client copy in a site uploads folder, not a clinical file. A page request is not proof anyone's vision changed. The page URL can say optometrist even when no form is submitted. Ask what happens to the night-driving answer and the diabetes checkbox after the visit — the quietest field is the one about the car keys, 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 exam-accuracy or disease-screening claim, an optometric-licensure claim, a fitness-to-drive or DMV-reporting claim, a vision-insurance coverage 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 exam bookings, intake notes, and page tags go

Bookings and notes on your WordPress site

Check which diabetes-or-blood-pressure, medications, family-eye-history, night-driving-difficulty, or current-prescription fields you enable, who can open form entries and exam or contact-lens-fitting bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the eye-exam intake asks about everything except your eyes. Notification emails can also copy those fields off-site. One table can list every annual exam next to a diabetes checkbox and a night-driving answer. Ask your web vendor not to keep prior-Rx uploads next to family glaucoma notes 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 diagnosis. A night-driving answer is not a fitness-to-drive finding.

Page tags handled by a vendor

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

Exam / contact-lens-fitting / recheck booking, eye-exam 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 optometry EHR and practice-management 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. An annual exam slot, a contact-lens fitting, or a post-Rx recheck is a booking you create; a service name such as comprehensive eye exam or contact lens fitting is a label you configure. Neither is a documented default. Diabetes-or-blood-pressure, medications, family-eye-history, night-driving-difficulty, or current-prescription questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not a diagnosis — and a CSV export of an exam row next to a diabetes checkbox, a medications list, and a night-driving answer is still a calendar that profiles systemic history beside the car-keys question. 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.

Exam, contact-lens-fitting, and recheck 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. Diabetes-or-blood-pressure, medications, family-eye-history, night-driving-difficulty, or current-prescription questions are fields you add; they are not documented defaults. Completing the form can store a diabetes checkbox next to a medications list, a family glaucoma note naming relatives who never consented, a night-driving-difficulty answer, a current-prescription field, and optional prior-Rx or insurance-card uploads — typed once as the eye-exam intake that asks about everything except your eyes, into the same tables as a newsletter signup. An exam booking is not a diagnosis. A diabetes checkbox is the patient's answer, not an endocrine record. A family-history field names third parties who never consented. A night-driving answer is a self-description, not a fitness-to-drive finding. An uploaded prescription is a client copy in a site uploads folder, not a clinical file — and a staff login can open "diabetes yes, lisinopril, mother glaucoma, difficulty driving at night, prior Rx JPEG" next to an insurance-card scan 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.

Eye-exam intake entries stored in WordPress; optional prior-Rx and insurance-card 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 diabetes-or-blood-pressure, medications, family-eye-history, night-driving-difficulty, or current-prescription field was sent. A page request from this script is not proof anyone's vision changed. The page URL can say optometrist 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. Diabetes-or-blood-pressure, medications, family-eye-history, night-driving-difficulty, or current-prescription fields often depend on the fields you configure. An exam booking is not a diagnosis. A diabetes checkbox is the patient's answer, not an endocrine record. A family-history field names third parties who never consented. A night-driving answer is a self-description, not a fitness-to-drive finding. An uploaded prescription is a client copy in a site uploads folder, not a clinical file. A marketing-tag page request is not proof anyone's vision changed. The page URL can say optometrist even when no form is submitted. The eye-exam intake that asks about everything except your eyes — that is a storage path next to a night-driving answer, not a feature these plugins claim. This page is about that eye-exam intake, not an audiology hearing test, a hearing-aid battery subscription, a podiatry diabetes record, or a dialysis calendar. 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 "20/20 vision" 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 exam accuracy or disease-screening efficacy, optometric licensure or scope, fitness-to-drive or DMV reporting rules, or vision-insurance coverage. 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-optometrist-plugin-privacy