Egg donor plugin privacy

The application that catalogs a family through the one member who consented

An egg-donor application can look like a booking and a contact form. The same form often asks the applicant for her own health history, then for her family's: parents' and grandparents' conditions and causes of death, siblings' mental-health history, three generations of genetic screening questions — plus childhood photos, adult photos, education, and SAT scores — and stores those answers next to her name and face for the life of the form table. Those fields are configured, not documented defaults. One WordPress row is a genetic and psychiatric catalog of an entire family, typed by the one member who consented; most of the people it describes never filled out the form. An application row is not proof anyone donated. A family-history answer is the applicant's account, not a relative's medical record or consent. A childhood photo is an upload the applicant chose, not the child's choice. A page request is not proof anyone applied. The page URL can say egg donor even when no form is submitted. Ask what happens to the three-generation family-history field and the childhood photo after the visit — the application catalogs a family through the one member who consented, and the row outlives the screening. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the application page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a fertility-outcome claim, a donor-anonymity-law claim, a genetic-privacy-law claim (including GINA), an ASRM-guideline claim, a compensation-legality 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 screening bookings, family-catalog intakes, and page tags go

Intakes and bookings on your WordPress site

Check which donor-health, family-history-three-generations, sibling-mental-health, genetic-screening, or education fields you enable, who can open form entries and screening bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when most of the dossier describes people who never filled out the form. Notification emails can also copy those fields off-site. One table can list every family whose one consenting member typed a three-generation catalog. Ask your web vendor not to keep childhood photos and transcripts next to family-history answers in one open submissions list longer than operations need, and to purge intake rows when the screening is closed. A privacy-policy page does not by itself limit who can open a submissions list. A stored appointment is not proof of donation. An uploaded childhood photo is not the child's consent.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the egg-donor application page. That page request can reach a vendor host before anyone submits. The page URL can say egg donor even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off application and booking pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "confidential donor intake" badge is not a verified storage path.

Screening, family-catalog 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 fertility-clinic or donor-agency 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 screening-appointment booking is a booking you create; a service name such as egg-donor screening or donor intake is a label you configure. Neither is a documented default. Donor-health, family-history-three-generations, sibling-mental-health, genetic-screening, or education questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof of donation — and a CSV export of visits next to an applicant name and a three-generation family catalog is still a relatives-as-data-subjects 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.

Egg-donor screening 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. Donor-health, family-history-three-generations, sibling-mental-health, genetic-screening, or education questions are fields you add; they are not documented defaults. Completing the form can store a genetic and psychiatric catalog of parents, grandparents, and siblings next to childhood photos, adult photos, and a transcript — typed by the one member who consented. An application row is not proof anyone donated. A family-history answer is the applicant's account, not a relative's medical record or consent. A childhood photo is an upload the applicant chose, not the child's choice — and a sibling mental-health answer can sit in the same row as the applicant's face. A staff login can open the uploaded childhood photo next to the three-generation family-history answer. 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.

Family-catalog intake entries stored in WordPress; optional childhood-photo, adult-photo, and transcript 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 donor-health, family-history-three-generations, sibling-mental-health, genetic-screening, or education field was sent. A page request from this script is not proof anyone applied. The page URL can say egg donor even when no form is submitted. Consent timing has not been tested. Review which tags you enable on application and booking 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. Donor-health, family-history-three-generations, sibling-mental-health, genetic-screening, or education fields often depend on the fields you configure. An application row is not proof anyone donated. A family-history answer is the applicant's account, not a relative's medical record or consent. A childhood photo is an upload the applicant chose, not the child's choice. A marketing-tag page request is not proof anyone applied. The page URL can say egg donor even when no form is submitted. Most of the dossier describes people who never filled out the form — that is a storage path next to a name, not a feature these plugins claim. This page is about that relatives-as-data-subjects intake, not a surrogacy-agency form, a DNA-testing kit, an adoption-agency application, a midwife intake, a plasma-donation signup, or a genealogy-research questionnaire. Ask your web vendor who can open entries, whether a marketing tag loads on the application page, and how long records and backups are kept. A "confidential donor intake" 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 fertility outcomes, donor-anonymity law, genetic-privacy law (including GINA), ASRM guidelines, or compensation legality. Review stored records, bookings, connected services, exports, notification emails, marketing tags on application 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-egg-donor-plugin-privacy