Surrogacy agency plugin privacy
Where does the application where your pregnancy history is the résumé go?
A surrogacy or gestational-carrier agency's application can collect prior pregnancy outcomes, C-section history, BMI, medications, mental-health screening answers, insurance status, and household income in a local-first form plugin — reproductive history submitted as candidacy, often years before any pregnancy exists. File fields can store home and family photos in the site uploads folder. The same row can name a partner's consent details for someone who never filled out the form. The application can quietly outlive a candidacy that never became a match. A marketing tag on the same page can send a page request to a vendor host before anyone submits. A page request is not proof that reproductive history was collected. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries, where uploaded files land, which tags load on the application page, and how long records, files, and backups are kept.
Documentation review only. This is not legal advice, a surrogacy-law review, an ART-regulation assessment, a compensation analysis, a medical-outcome 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, uploaded photos, email inboxes, staff permissions, vendor accounts, or backups.
Where application answers, photos, and page tags go
Entries and files handled on your WordPress site
Check which pregnancy-history, BMI, medication, mental-health, income, partner, or photo-upload fields you enable, who can open form entries, where uploaded photos live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after an application that never became a match. Notification emails can also copy the same answers off-site. Ask your web vendor not to collect full reproductive history on the first public form, and to keep partner details from sharing one open submissions list with applicant answers.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the carrier application page. That page request can reach a vendor host before anyone submits. Review which tags you enable, account access, and retention there. Keep marketing tags off application pages if you do not want that page request. A browser scan cannot inspect stored form entries. A "secure client forms" badge is not a verified storage path.
Surrogacy-agency application, 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 matching 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 |
|---|---|---|---|---|---|---|
| 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. Home photos, family photos, or medical-record scans are files you accept; they are not documented defaults. An uploaded photo is not a match decision or a pregnancy. 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_uploads | 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. Prior-pregnancy outcomes, C-section history, BMI, medications, mental-health screening answers, insurance status, household income, or partner name and consent answers are fields you add; they are not documented defaults. Home or family photos are files you accept; they are not documented defaults. One application can name a partner even when that person never filled out the form. A submitted application is not a match, a screening result, or a pregnancy. 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 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 pregnancy-history answers or partner details were sent. A page request from this script on a surrogacy-agency application page is not proof that reproductive history was collected — and a pre-consent tag on that page can still treat surrogacy-agency shopping intent as an audience segment from the URL alone. The page URL can say carrier application even when no form is submitted. Consent timing has not been tested. Review which tags you enable on application 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. Pregnancy-history answers, BMI, medications, mental-health screening, income, partner details, or uploaded photos often depend on the fields you configure. A submitted application is not a match, a screening result, or a pregnancy. A marketing-tag page request is not proof that reproductive history was collected. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the application page, and how long records and backups are kept. A "secure" or "client forms" 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 surrogacy law, ART regulation, compensation rules, or medical outcomes. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on application pages, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress fertility plugin privacy
- WordPress file upload plugin privacy
- WordPress survey plugin privacy
- All privacy guides
/wp-surrogacy-agency-plugin-privacy