Paternity testing plugin privacy
The intake that names two parents and the doubt between them
A paternity-testing appointment can store two adult names next to a child name and a collection date. The appointment type itself, stored in plain text in a booking plugin, can say someone doubts a parentage before any swab is taken. Chain-of-custody PDFs and ID photos can sit in the site uploads folder. That pairing can sit in a form plugin entries table any staffer can open after a result never arrives. Alleged-father-name, alleged-mother-name, child-name, collection-date, appointment-type, chain-of-custody-pdf, id-photo, requester-name, and phone fields are configured, not documented defaults. Optional chain-of-custody PDFs and ID photos go in the site uploads folder. Two adult names next to a child is a stored pairing, not a DNA result. An appointment type labeled paternity test is a stored service name, not proof anyone is not a parent. A collection date is a stored date, not proof a swab was taken. A chain-of-custody PDF is an upload, not a lab report. An ID photo is an upload, not proof of identity. A paternity booking is not proof anyone doubted parentage. A page request is not proof anyone booked a test. The page URL can say paternity testing 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 booking and intake pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a DNA-result claim, a parentage claim, a custody claim, a fertility claim, an adoption claim, a HIPAA 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, bookings, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where paternity-intake rows, uploaded files, and page tags go
Paternity bookings and forms handled on your WordPress site
Check which alleged-father-name, alleged-mother-name, child-name, collection-date, appointment-type, chain-of-custody-pdf, id-photo, requester-name, or phone fields you enable, who can open form entries and bookings, where uploaded chain-of-custody PDFs and ID photos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a result never arrives. Notification emails can also copy the same alleged-father names, alleged-mother names, child names, collection dates, appointment types, chain-of-custody PDFs, ID photos, and requester names off-site. One table can name two adults, a child, and a collection date next to an appointment type, even when no swab is taken. Ask your web vendor not to collect two adult names next to a child name and a collection date on the first public form, not to store those files next to an appointment type in one open submissions list, and to purge unused pairings after the collection date passes. A privacy-policy page does not by itself limit who can export an intake list or republish an upload. A stored pairing is not a DNA result.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the paternity-testing booking or intake page. That page request can reach a vendor host before anyone submits. The page URL can say paternity testing even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and intake pages if you do not want that page request. A browser scan cannot inspect stored alleged-father names, child names, or chain-of-custody PDFs. A "legal DNA" badge is not a verified storage path.
Paternity-testing booking, 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 paternity-lab or relationship-DNA software without a WordPress.org listing is outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Easy Appointments Documented self-hosted appointment plugin marketed for service businesses (plugin version 4.0.3). The listing documents automatic email notifications: customers get instant booking confirmations; staff get notified; templates can include booking information and custom fields; customers can confirm or cancel via a link in the email. WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A paternity-testing appointment is a booking you create; a service name such as paternity test, relationship DNA, legal collection, or buccal swab is a label you configure. Neither is a documented default. The stored service name can say paternity testing in plain text before any swab is taken. Alleged-father-name, alleged-mother-name, child-name, collection-date, appointment-type, requester-name, or phone questions are custom fields you add (textarea, select, or input); they are not documented defaults. Two adult names next to a child is a stored pairing, not a DNA result. An appointment type labeled paternity test is a stored service name, not proof anyone is not a parent. A collection date is a stored date, not proof a swab was taken. A booked slot is not proof anyone doubted parentage, and is not proof a lab ran a test. Cancelling or missing the slot later does not erase the two adult names, child name, collection date, or appointment type already stored next to a requester name, and does not unsend a confirmation email already delivered. How long that pairing sits after a booking that never produced a result is not a documented default of the plugin. 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. | Paternity-testing bookings, custom intake fields, and automatic confirmation emails on your WordPress site | 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. Alleged-father-name, alleged-mother-name, child-name, collection-date, appointment-type, requester-name, or phone questions are fields you add; they are not documented defaults. Chain-of-custody PDFs and ID photos are files you accept; those file types are not documented defaults. Two adult names next to a child is a stored pairing, not a DNA result. An appointment type labeled paternity test is a stored service name, not proof anyone is not a parent. A collection date is a stored date, not proof a swab was taken. A chain-of-custody PDF is an upload, not a lab report. An ID photo is an upload, not proof of identity. A paternity booking is not proof anyone doubted parentage. 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 a pairing sits after a result never arrives is not a documented default of the plugin. | Paternity-intake 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 an alleged-father-name, child-name, or collection-date field was sent. A page request from this script on a paternity-testing intake page is not proof anyone booked a test, and a pre-consent tag on that page can still treat paternity-testing interest as an audience segment from the URL alone. The page URL can say paternity testing even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and intake pages. Keep marketing tags off those pages if you do not want that page request. A tagged intake page can re-confirm paternity-testing interest next to a stored pairing; this row does not claim a DNA result from that request. | 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. Alleged-father-name, alleged-mother-name, child-name, collection-date, appointment-type, chain-of-custody-pdf, id-photo, requester-name, or phone fields often depend on the fields you configure. Two adult names next to a child is a stored pairing, not a DNA result. An appointment type labeled paternity test is a stored service name, not proof anyone is not a parent. A collection date is a stored date, not proof a swab was taken. A chain-of-custody PDF is an upload, not a lab report. An ID photo is an upload, not proof of identity. A paternity booking is not proof anyone doubted parentage. A marketing-tag page request is not proof anyone booked a test. The page URL can say paternity testing even when no form is submitted. The two adult names, the child name, and the collection date can sit after a result never arrives. This page is about a paternity intake that names two parents and the doubt between them, not an ancestry or identity DNA kit, not a custody worksheet, not a fertility treatment history, and not an adoption home study. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or intake page, and how long records and backups are kept. A "legal DNA" 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 DNA-result, parentage, custody, fertility, adoption, or HIPAA claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and intake pages, and backups.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress forms privacy
- WordPress email plugin privacy
- All privacy guides
/wp-paternity-testing-plugin-privacy