Genealogy research plugin privacy

The family secret you paid someone to confirm

A genealogy research request can look like a name, a date, and a file upload. The question itself is the payload. "Is he my father?" sits in a form before any answer exists. The same row can name a living parent, a half-sibling, or a relative who did not fill out the form and may never learn the question was asked. Suspicion, relative-name, and document-upload fields are configured, not documented defaults. A birth certificate, an old letter, or a DNA-result PDF exported from elsewhere can sit in the same uploads folder. Abandoning the research does not erase the suspicion already stored next to real names. A research request is not proof the suspicion is true. A consult booking is not proof anyone was adopted. A page request is not proof a family has a secret. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on research-request and consult pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a GINA claim, a genetic-privacy-law claim, an adoption-law claim, a sealed-records-law claim, a research-accuracy 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, bookings, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.

Where research requests, consults, and page tags go

Research requests and consult bookings handled on your WordPress site

Check which suspicion, relative-name, or document-upload fields you enable, who can open form entries and bookings, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a request that never became a report. Notification emails can also copy the same answers off-site. One table can list every named relative even when only the client typed. Ask your web vendor not to collect a suspicion or a living relative's name on the first public form, not to store that question next to uploaded certificates in one open submissions list, and to purge research requests after the work ends. A privacy-policy page does not by itself limit who can export a research-request list. A stored research request is not proof the suspicion is true.

Page tags handled by a vendor

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

Genealogy research-request, consult, 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 genealogy CRM or research-case software without a WordPress.org listing is outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
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 genealogy consult is a booking you create; a service name such as family-history consult or research intake is a label you configure. Neither is a documented default. Suspicion or relative-name questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked consult is not a research report and is not proof anyone was adopted. Cancelling or missing the consult later does not erase the contact answers already stored next to a name, and does not unsend a confirmation email already delivered. How long that row sits after a request that never became a report 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.

Consult bookings, custom intake fields, and automatic confirmation emails on your WordPress siteBrowser 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. 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. Suspicion, relative-name, or document-upload questions are fields you add; they are not documented defaults. A birth certificate, an old letter, or a DNA-result PDF exported from elsewhere is a file you accept; none of those file types is a documented default. A research request is not proof the suspicion is true. The person named in a relative-name field is not the person who filled out the form. 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 research request sits after a request that never became a report is not a documented default of the plugin.

Research-request 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 a suspicion or relative-name field was sent. A page request from this script is not proof a family has a secret. The page URL can say genealogy or family-history even when no form is submitted. Consent timing has not been tested. Review which tags you enable on research-request and consult pages. Keep marketing tags off those pages if you do not want that page request. A tagged research-request page can re-confirm a household that already named a living relative; this row does not claim a research outcome 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. Suspicion, relative-name, or document-upload fields often depend on the fields you configure. A research request is not proof the suspicion is true. A consult booking is not proof anyone was adopted. A marketing-tag page request is not proof a family has a secret. The page URL can say genealogy or family-history even when no form is submitted. The question can sit after the research is abandoned. This page is about a research request that stores the question before any answer exists, not a lab DNA test, a private investigator file, an adoption agency home study, or a name change petition. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the research-request or consult page, and how long records and backups are kept. A "secure" or "confidential research" 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 GINA, genetic-privacy law, adoption law, sealed-records law, or research accuracy. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on research-request and consult pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-genealogy-research-plugin-privacy