Plasma donation plugin privacy

A paid questionnaire can store health answers next to payment

A plasma-center pre-screen form can store tattoo, travel, medication, and sex-history answers in the same WordPress table as an ID scan and the payment-card details used to pay the donor. Completing the form can record a paid-donor inquiry even when every answer is no. A staff login can open both the health answers and the payment fields. A marketing tag on the appointment page can send a page request to a vendor host before anyone submits. The page URL can say donor eligibility. A page request is not proof that questionnaire answers were collected. A pre-screen entry is not a completed donation or an eligibility decision. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and files, which tags load on the appointment page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal or medical advice, an FDA donor-eligibility claim, a blood-safety assessment, a compensation-regulation 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 health answers, ID scans, and page tags go

Pre-screen answers and files handled on your WordPress site

Check which tattoo, piercing, travel-history, medication, sex-history, ID-scan, or payment-card fields you enable, who can open form entries, which inboxes receive copies, and how long records, emails, and backups are kept. Notification emails can also copy the same answers off-site. One entry can store health-disclosure answers next to payment-card signup fields. Completing the form can record a paid-donor inquiry even when every answer is no. Ask your web vendor not to collect sex-history or medication answers on a public form, not to accept ID scans on a public pre-screen page, and to purge entries that never became donations. A privacy-policy page does not by itself limit who can open a pre-screen list.

Page tags handled by a vendor

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

Plasma-center form, upload, 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 donor-center software without a WordPress.org listing is outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Drag and Drop Multiple File Upload for Contact Form 7

Documented Contact Form 7 upload extension (plugin version 1.4.0). Version 1.4.0 drag-n-drop-upload-cf7.php defines wpcf7_dnd_dir as wp_dndcf7_uploads. The listing states the free version moves files to wp-content/uploads/wp_dndcf7_uploads, attaches them to mail, then removes them from that temporary folder about one hour after submission. That cleanup does not remove copies already sent as email attachments. ID scans or donor-card photos are files you accept; they are not documented defaults. An uploaded ID scan is not a completed donation. Pro documents saving to the Media Library, changing the upload directory, auto-delete timers, and remote storage to OneDrive, Google Drive, Amazon S3, Dropbox, or FTP. Public upload-page browser hosts are unverified.

Visitor files stored under wp-content/uploads/wp_dndcf7_uploadsBrowser 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 plus payment-form options. 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. Tattoo, piercing, travel-history, medication, or sex-history deferral questions are fields you add; they are not documented defaults. Payment-card signup or compensation fields are fields you add; they are not documented defaults. One form entry can store health-disclosure answers next to payment-card signup fields. Completing the form can record a paid-donor inquiry even when every answer is no. A pre-screen entry is not a completed donation or an eligibility decision. A staff login can open both the questionnaire answers and the payment fields in the same submissions list. Notification emails can copy field values off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified.

Form entries stored in WordPress; file 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 questionnaire answers or payment-card fields were sent. A page request from this script is not proof that questionnaire answers were collected. The page URL can say donor eligibility even when no form is submitted. Consent timing has not been tested. Review which tags you enable on appointment and pre-screen 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. Tattoo, piercing, travel-history, medication, sex-history, ID-scan, or payment-card fields often depend on the fields you configure. Completing the form can record a paid-donor inquiry even when every answer is no. A pre-screen entry is not a completed donation or an eligibility decision. An uploaded ID scan is not a finished donation visit. A marketing-tag page request is not proof that questionnaire answers were collected. The page URL can say donor eligibility even when no form is submitted. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the appointment page, and how long records and backups are kept. A "secure" or "donor portal" 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 FDA donor eligibility, blood safety, or compensation rules. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on appointment pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-plasma-donation-plugin-privacy