DNA-testing plugin privacy
The paternity inquiry that names people who never consented
DNA and paternity-testing labs on WordPress can host an inquiry that carries a family's most explosive secret in three text fields — who the mother is, who the presumed father is, and why someone doubts it. Relationship-testing labs, immigration DNA tests, and ancestry kits sold through WordPress storefronts can put names of people who never consented to being tested into a contact-form database — submitted by someone who may be hiding the inquiry from their own household. The inquiry itself is the secret. A remarketing pixel on that inquiry page can fire before consent and treat DNA-inquiry-intent traffic as an audience segment from the page URL alone. This sample reviews three plugins' documentation. Check which name and relationship fields you collect, who can open submissions, where temporary uploads and tags store or send that data, and how long inquiry rows, uploads, and backups are kept after the case closes.
Documentation review only. This is not legal advice, not a GINA or HIPAA guide, not a chain-of-custody or sample-handling claim, not a test-accuracy claim, and not a GDPR or other compliance assessment. Specialty lab portals and consumer ancestry apps without a WordPress-hosted inquiry form are outside this sample.
Scan your DNA-testing inquiry page for third-party requestsThe 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 inquiry answers, uploads, and inquiry-page tags are stored
Files and form entries handled on your WordPress site
Check which mother-name, presumed-father-name, relationship, why-someone-doubts, upload, or contact fields you enable, who can open entries, which uploads you accept, where temporary uploads live, which inboxes receive attachments, and how long records, uploads, and backups are kept after the case closes. Notification emails can also copy inquiry answers off-site. Those answers next to a name and email in the contact-form database can name people who never consented to being tested.
Marketing tags on the DNA-testing inquiry page
Some tools load a marketing pixel or tag on the same page as the DNA-testing inquiry form. A page request can fire before anyone submits a mother or presumed-father name — and the inquiry itself is the secret that page URL can reveal as a visit. A tag seeing a page request is evidence of a visit, not proof a test was ordered or that any named person was tested. Review which tags you enable, which consent filters you use, and what those platforms retain. A browser scan cannot inspect stored form entries or uploaded files.
DNA-testing inquiry 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 lab SaaS portals 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). The free-version listing states uploaded files move to a temporary folder under /wp-content/uploads/wp_dndcf7_uploads, attach to mail, then are removed from that temporary folder after submission — the same pattern Contact Form 7 documents for its default file field. That cleanup does not remove copies already sent as email attachments. Which ID scans, kit-registration photos, or other inquiry files you accept depends on the fields you add; they are not fixed DNA-testing defaults. Filenames chosen by visitors can include full legal names of people named in the inquiry. Pro documents Media Library storage, custom upload folders, auto-delete timers, and remote storage options. Public form-page browser hosts are unverified. | Uploaded files attached to email; temporary copies under wp-content/uploads | Browser hosts not verified | Not assessed | Not tested |
| |
| Formidable Forms Documented self-hosted form builder (plugin version 6.35). The listing states every form submission is stored in the WordPress database, with back-end entry access, CSV export, and email notifications or autoresponders you configure. Mother-name, presumed-father-name, relationship, why-someone-doubts, or contact fields depend on the fields you add — they are not fixed DNA-testing defaults. An inquiry form that stores those answers next to a name and email can name people who never consented to being tested, parked in the same contact-form database as ordinary lead capture. Optional payment, CRM, or spam-protection integrations send data only when enabled. Retention of entry rows after the case closes is not specified as a default purge. Public form browser hosts are unverified. | DNA-testing inquiry form entries stored in your WordPress database | 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, OpenAI Pixel, 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 mother name, presumed-father name, or doubt-reason answer was sent. A page request from this script on a DNA-testing inquiry page is evidence of a visit — not proof a test was ordered or that any named person was tested. A pre-consent tag on that page can still treat DNA-inquiry-intent traffic as an audience segment. The listing describes consent-plugin filters; that is not a legal-compliance assessment. Consent timing has not been tested. Review which tags you enable on inquiry 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. Mother-name, presumed-father-name, relationship, why-someone-doubts, or upload fields often depend on the fields you configure. An inquiry form is not a genetic test result, not a chain-of-custody record, and not proof a sample was collected or that any named person was tested. A marketing-tag page request is evidence of a visit — not proof a test was ordered. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess genetic-data handling, GINA, HIPAA, chain-of-custody procedures, sample mishandling, test accuracy, or other compliance status. Ask your web vendor where entries and uploads live, whether closed-case inquiry rows purge, whether portal links expire, whether marketing pixels stay off inquiry pages, whether ID scans stay off the first contact form, and whether “secure intake” badges match the storage path you can verify. Review stored records, uploaded files, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
Scan your DNA-testing inquiry page for third-party requests/wp-dna-testing-plugin-privacy