Podiatrist plugin privacy
The standing six-week toenail appointment that is actually a diabetes record
A podiatrist booking page can look like a calendar and a short intake form. The same form often asks for diabetic or circulation status, numbness or tingling, current footwear, and mobility aids — and asks for a wound photo so the clinic can triage from a picture — 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 six-week nail-care booking next to a diabetic checkbox and a marketing pixel — the standing six-week toenail appointment that is actually a diabetes record, typed once into a vendor table next to a newsletter signup. A recurring booking is a calendar rhythm, not a diagnosis. A diabetic checkbox is the patient's answer, not an endocrinology record. A numbness answer is a symptom description, not a neuropathy finding. A wound photo is a client image in a site uploads folder, not clinical imaging. A page request is not proof anything is wrong with anyone's feet. The page URL can say podiatrist even when no form is submitted. Ask what happens to the wound photo and the diabetic checkbox after the visit — the six-week rhythm keeps re-dating the condition every time the slot renews, 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 wound-care outcomes claim, a diabetes management or screening claim, a podiatric-licensure claim, a Medicare routine-foot-care coverage claim, or a GDPR or other compliance assessment.
Scan your site for third-party requestsThe 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 routine-care bookings, intake notes, and page tags go
Bookings and notes on your WordPress site
Check which diabetic-or-circulation, numbness, footwear, or mobility-aids fields you enable, who can open form entries and routine-care or assessment bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the standing six-week toenail appointment is actually a diabetes record. Notification emails can also copy those fields off-site. One table can list every six-week nail-care slot next to a diabetic checkbox and a wound JPEG. Ask your web vendor not to keep wound-photo uploads next to diabetic-or-circulation 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 diagnosis. A numbness answer is not a neuropathy finding.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the podiatrist booking page. That page request can reach a vendor host before anyone submits. The page URL can say podiatrist 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 "healthy feet" badge is not a verified storage path.
Routine-care / assessment booking, podiatry 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 wound-care and diabetic-foot SaaS platforms without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| 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 routine nail-care slot or a new-patient assessment is a booking you create; a service name such as six-week toenail care or diabetic-foot assessment is a label you configure. Neither is a documented default. Recurring appointments can re-date the same patient on a standing cadence. Diabetic-or-circulation, numbness, footwear, or mobility-aids 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 a six-week nail-care row next to a diabetic checkbox and a numbness answer is still a calendar that dates a systemic condition beside a wound photo. 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. | Routine-care and assessment bookings stored on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| 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. Diabetic-or-circulation, numbness, footwear, or mobility-aids questions are fields you add; they are not documented defaults. Completing the form can store a diabetic-or-circulation answer next to a numbness field, a footwear note, mobility-aids, and optional wound-photo or referral uploads — typed once as the standing six-week toenail appointment that is actually a diabetes record, into the same tables as a newsletter signup. A recurring booking is a calendar rhythm, not a diagnosis. A diabetic checkbox is the patient's answer, not an endocrinology record. A numbness answer is a symptom description, not a neuropathy finding. A wound photo is a client image in a site uploads folder, not clinical imaging — and a staff login can open "diabetic checkbox yes, numbness left forefoot, tight shoes, cane, ulcer JPEG" next to a referral letter 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. | Podiatry intake entries stored in WordPress; optional wound-photo and referral uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| 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 diabetic-or-circulation, numbness, footwear, or mobility-aids field was sent. A page request from this script is not proof anything is wrong with anyone's feet. The page URL can say podiatrist 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 platforms | connect.facebook.net | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Diabetic-or-circulation, numbness, footwear, or mobility-aids fields often depend on the fields you configure. A recurring booking is a calendar rhythm, not a diagnosis. A diabetic checkbox is the patient's answer, not an endocrinology record. A numbness answer is a symptom description, not a neuropathy finding. A wound photo is a client image in a site uploads folder, not clinical imaging. A marketing-tag page request is not proof anything is wrong with anyone's feet. The page URL can say podiatrist even when no form is submitted. The standing six-week toenail appointment that is actually a diabetes record — that is a storage path next to a wound JPEG, not a feature these plugins claim. This page is about that podiatry intake, not a dialysis calendar, a home-care mobility roster, a medical-alert household setup, or a stairlift quote. 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 "healthy feet" 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 wound-care outcomes, diabetes management or screening standards, podiatric licensure, or Medicare routine-foot-care 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
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-podiatrist-plugin-privacy