Genetic counseling plugin privacy
The intake where your family tree becomes a medical record
A genetic-counseling booking page can look like a calendar and a short intake. The same form often asks for a reason for referral, a family-history grid, which relatives were affected, prior test results, and an insurance question — and stores those answers next to the client's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold your mother's breast cancer next to a BRCA concern and a pedigree PDF — the intake where your family tree becomes a medical record, typed once into a vendor table next to a marketing pixel. Every relative in that grid is a third party who never touched the form. A counseling request is not a diagnosis or a test result. A family-history answer is the client's recollection, not a relative's medical record. A reason-for-referral is a concern, not a finding. An uploaded lab report is a stored document, not proof anyone reviewed it. A page request is not proof anyone carries anything. The page URL can say genetic counseling even when no form is submitted. Ask what happens to the pedigree and the lab upload after the visit — the intake turns a family tree into a medical record, 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 genetic-test-accuracy claim, hereditary-risk or medical advice, a GINA or insurance-discrimination claim, a HIPAA coverage claim, a counseling-efficacy 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 counseling bookings, pedigree notes, and page tags go
Bookings and notes on your WordPress site
Check which reason-for-referral, family-history-grid, relatives-affected, prior-test-results, or insurance-question fields you enable, who can open form entries and counseling-session bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the intake where your family tree becomes a medical record. Notification emails can also copy those fields off-site. One table can list every counseling slot next to a family-history grid and a relationship column. Ask your web vendor not to keep a relative's diagnosis next to the client's 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. Relatives named in the pedigree never touched the form.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the genetic counseling booking page. That page request can reach a vendor host before anyone submits. The page URL can say genetic counseling 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 "family history" badge is not a verified storage path.
Counseling-session booking, pedigree 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 genetics EHR and counseling 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 first counseling session, a results-review visit, or a cascade-testing consult is a booking you create; a service name such as initial counseling, results review, or family consult is a label you configure. Neither is a documented default. Reason-for-referral, family-history-grid, relatives-affected, prior-test-results, or insurance-question fields 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 counseling slot next to a BRCA-in-the-family referral field is still a calendar that turns a pedigree into a row. 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. | Counseling-session 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. Reason-for-referral, family-history-grid, relatives-affected, prior-test-results, or insurance-question fields are fields you add; they are not documented defaults. Completing the form can store a reason-for-referral answer next to a family-history grid, a relatives-affected list, an insurance question, and optional pedigree-chart or prior-lab-report uploads — typed once as the intake where your family tree becomes a medical record into the same tables as a newsletter signup. A counseling request is not a diagnosis or a test result. A family-history answer is the client's recollection, not a relative's medical record. A reason-for-referral is a concern, not a finding. Relatives named in the pedigree never touched the form and may not know the row exists. An uploaded lab report is a stored document, not proof anyone reviewed it — and a staff login can open "mother breast cancer age 42, maternal aunt ovarian cancer, BRCA concern" next to a pedigree 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. | Genetic-counseling intake entries stored in WordPress; optional pedigree-chart and prior-lab-report 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 reason-for-referral, family-history-grid, relatives-affected, prior-test-results, or insurance-question field was sent. A page request from this script is not proof anyone carries anything. The page URL can say genetic counseling 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. Reason-for-referral, family-history-grid, relatives-affected, prior-test-results, or insurance-question fields often depend on the fields you configure. A counseling request is not a diagnosis or a test result. A family-history answer is the client's recollection, not a relative's medical record. A reason-for-referral is a concern, not a finding. Relatives named in the pedigree never touched the form and may not know the row exists. An uploaded lab report is a stored document, not proof anyone reviewed it. A marketing-tag page request is not proof anyone carries anything. The page URL can say genetic counseling even when no form is submitted. The intake where your family tree becomes a medical record — that is a storage path next to a relationship column, not a feature these plugins claim. This page is about that pedigree intake, not a consumer DNA test, a fertility clinic, or an adoption agency birth-family 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. A "family history" 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 genetic-test accuracy, hereditary-risk or medical advice, GINA or insurance-discrimination law, HIPAA coverage status, or counseling efficacy. 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-genetic-counseling-plugin-privacy