Cord blood banking plugin privacy

The enrollment that banks a child's biology before the birth certificate exists

A cord-blood enrollment can look like a kit and a hospital pickup. It is also a biological dossier on a person who has not been born yet: due date, delivery hospital, OB name, both parents' medical histories, and consent over the newborn's genetic material — collected through a web form before the child has a name, sitting in a plugin entries table with ad pixels watching the signup. Due-date, delivery-hospital, OB-name, maternal-history, paternal-history, genetic-consent, and kit-ship fields are configured, not documented defaults. Optional consent PDFs and prenatal records go in the site uploads folder. An enrollment is not proof a sample was collected. A parent-history answer is a stored note, not a verified diagnosis. A page request is not proof anyone enrolled. The page URL can say cord blood banking even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on enrollment and account pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a stem-cell-efficacy claim, a genetic-discrimination claim, a HIPAA 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, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.

Where banking enrollments, medical-history forms, and page tags go

Enrollment forms and document uploads handled on your WordPress site

Check which due-date, delivery-hospital, OB-name, maternal-history, paternal-history, genetic-consent, or kit-ship fields you enable, who can open form entries, where uploaded consent PDFs live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after an enrollment that never became a collection. Notification emails can also copy the same parent medical histories and file link off-site. One table can name the parents, the due date, and the genetic consent next to a hospital, even when no sample is drawn. Ask your web vendor not to collect both parents' medical histories next to genetic consent on the first public form, not to store due dates next to contact details in one open submissions list, and to purge unused enrollments after the due date passes. A privacy-policy page does not by itself limit who can export an enrollment list. A stored enrollment is not proof a sample was collected.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the cord-blood enrollment or account page. That page request can reach a vendor host before anyone submits. The page URL can say cord blood banking even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off enrollment and account pages if you do not want that page request. A browser scan cannot inspect stored due dates, parent medical histories, or genetic-consent answers. An "expecting parent" badge is not a verified storage path.

Cord-blood enrollment, medical-history, 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 cord-blood lab or biobank software without a WordPress.org listing is outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
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. Due-date, delivery-hospital, OB-name, maternal-history, paternal-history, genetic-consent, or kit-ship questions are fields you add; they are not documented defaults. A prenatal record or consent PDF is a file you accept; that file type is not a documented default. An enrollment is not proof a sample was collected. A parent-history answer is a stored note, not a verified diagnosis. A cancelled enrollment still leaves the due date and both parents' medical histories in the submissions list. Notification emails can copy field values and file links off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. How long an enrollment row sits after a request that never became a collection is not a documented default of the plugin.

Enrollment form entries stored in WordPress; file uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
Iptanus File Upload

Documented frontend upload form (formerly WordPress File Upload). By default files land inside the wp-content directory of the site; the upload path is configurable. Uploaded files can be added to Media or attached to the current page. FTP and SFTP destinations are documented. The Professional version documents uploads to Google Drive, Dropbox, OneDrive, or Amazon S3. A signed consent PDF, OB referral, or insurance card is a file you accept; that file type is not a documented default. An uploaded consent is a file, not proof a sample was banked. Deleting a form entry later does not by itself prove the file was removed from the uploads path or from a cloud destination you enabled. The listing claims GDPR compliance without a tested EXIF-strip or retention length here. Review upload directory, Media attachment, and cloud destinations. Browser hosts for the visitor upload path were not verified for this snapshot.

Consent and prenatal-document uploads stored under the site wp-content pathBrowser 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 due-date, maternal-history, paternal-history, or genetic-consent field was sent. A page request from this script is not proof anyone enrolled in cord-blood banking. The page URL can say cord blood banking even when no form is submitted. Consent timing has not been tested. Review which tags you enable on enrollment and account pages. Keep marketing tags off those pages if you do not want that page request. A tagged enrollment page can re-confirm banking interest next to a stored unborn-dossier; this row does not claim a collection from that request.

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. Due-date, delivery-hospital, OB-name, maternal-history, paternal-history, genetic-consent, or kit-ship fields often depend on the fields you configure. A banking enrollment is not proof a sample was collected. A parent-history answer is a stored note, not a verified diagnosis. A marketing-tag page request is not proof anyone enrolled. The page URL can say cord blood banking even when no form is submitted. The due date and both parents' medical histories can sit after no sample is drawn. This page is about a pre-birth genetic enrollment, not a special-education child-medical-struggles intake, not a hospice end-of-life intake, and not a sleep-study overnight medical booking. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the enrollment or account page, and how long records and backups are kept. An "expecting parent" 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 stem-cell efficacy, genetic discrimination, or HIPAA. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on enrollment and account pages, and backups.

Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-cord-blood-banking-plugin-privacy