Allergy clinic plugin privacy

The intake that lists what could kill you

An allergy clinic booking page can look like a calendar and a short intake. The same form often asks for reaction history, suspected triggers, current medications, the child's school name for the action plan, and an emergency contact — who gets the call if the skin test goes wrong, named in a database row before any appointment has happened — 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 anaphylaxis story next to a peanut checkbox, a school name, and a mom's cell phone — the intake that lists what could kill you, typed once into a vendor table next to a marketing pixel. A testing appointment is not a diagnosis. A reaction history is the patient's account, not a clinical finding. A suspected-trigger checkbox is a worry, not a confirmed allergy. An uploaded prior result is a stored document, not proof the clinic reviewed it. A page request is not proof anyone is allergic to anything. The page URL can say allergy clinic even when no form is submitted. Ask what happens to the reaction history and the action-plan upload after the visit — the intake lists what could kill you, 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 test-accuracy claim, an immunotherapy-efficacy claim, anaphylaxis treatment or emergency guidance, a HIPAA coverage claim, dietary or medical advice, 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 testing bookings, allergy notes, and page tags go

Bookings and notes on your WordPress site

Check which reaction-history, suspected-triggers, medication-list, school-or-daycare-name, or emergency-contact fields you enable, who can open form entries and testing or shot bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the intake lists what could kill you. Notification emails can also copy those fields off-site. One table can list every weekly shot next to a reaction-history field and a school name. Ask your web vendor not to keep reaction history next to emergency contact 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 suspected-trigger checkbox is not a confirmed allergy.

Page tags handled by a vendor

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

Testing / shot booking, allergy 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 allergy EHR and immunotherapy 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 skin-test slot, a challenge-test visit, or a standing immunotherapy shot is a booking you create; a service name such as initial consult, skin testing, or shot clinic is a label you configure. Neither is a documented default. Reaction-history, suspected-triggers, medication-list, school-or-daycare-name, or emergency-contact 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 weekly shot next to a peanut reaction-history field is still a calendar that lists what could kill the patient. 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.

Testing and immunotherapy-shot 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. Reaction-history, suspected-triggers, medication-list, school-or-daycare-name, or emergency-contact questions are fields you add; they are not documented defaults. Completing the form can store a reaction-history answer next to a suspected-trigger checklist, a medication list, a school name for the action plan, an emergency contact, and optional prior-test-results or action-plan uploads — typed once as the intake that lists what could kill you into the same tables as a newsletter signup. A testing appointment is not a diagnosis. A reaction history is the patient's account, not a clinical finding. A suspected-trigger checkbox is a worry, not a confirmed allergy. An uploaded prior result is a stored document, not proof the clinic reviewed it — and a staff login can open "anaphylaxis after peanut butter at age 4, EpiPen twice, school: Lincoln Elementary, call mom first" next to an action-plan PDF. 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.

Allergy intake entries stored in WordPress; optional prior-test-results and action-plan 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 reaction-history, suspected-triggers, medication-list, school-or-daycare-name, or emergency-contact field was sent. A page request from this script is not proof anyone is allergic to anything. The page URL can say allergy 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. Reaction-history, suspected-triggers, medication-list, school-or-daycare-name, or emergency-contact fields often depend on the fields you configure. A testing appointment is not a diagnosis. A reaction history is the patient's account, not a clinical finding. A suspected-trigger checkbox is a worry, not a confirmed allergy. An uploaded prior result is a stored document, not proof the clinic reviewed it. A marketing-tag page request is not proof anyone is allergic to anything. The page URL can say allergy clinic even when no form is submitted. The intake that lists what could kill you — that is a storage path next to an emergency-contact field, not a feature these plugins claim. This page is about that allergy intake, not a summer camp EpiPen card, a daycare allergy note, a sleep clinic, or a food pantry dietary form. 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. An "allergy-friendly clinic" 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 test accuracy, immunotherapy efficacy, anaphylaxis treatment or emergency guidance, HIPAA coverage status, or dietary or medical advice. 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-allergy-clinic-plugin-privacy