Polygraph plugin privacy

The booking that records the accusation before any test is run

A polygraph booking form can ask what the test is about. The answer is often an accusation: a suspected affair, missing cash, or a workplace allegation an employer wants resolved. The person named in that field is often not the person typing. A spouse can book a test for a partner. An employer can book a test for an employee. The examination can clear the named person. The booking row that records that someone paid to suspect them does not get that update. Those answers can sit in a local-first form or booking plugin behind one admin login. 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 a suspicion was described. A booking entry is not a test result, an accusation of record, or evidence of deception. The page URL can say polygraph even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries, where uploaded files land, which tags load on the booking page, and how long records, files, and backups are kept.

Documentation review only. This is not legal advice, an EPPA claim, a polygraph-admissibility claim, a polygraph-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 booking answers, subject names, and page tags go

Entries and bookings handled on your WordPress site

Check which test-reason, subject-name, or employer-contact fields you enable, who can open form entries and bookings, where uploaded intake files live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after a booking that never became a completed test. Notification emails can also copy the same answers off-site. Ask your web vendor not to collect accusation text on the first public form, and not to store a named person next to a suspicion typed by someone else in one open submissions list.

Page tags handled by a vendor

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

Polygraph booking, form, 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 lie-detection platforms without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Easy Appointments

Documented self-hosted appointment plugin marketed for clinics and service businesses (plugin version 4.0.3). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A polygraph test slot is a booking you create; a service name such as infidelity test or pre-employment screening is a label you configure. Neither is a documented default. Test-reason, subject-name, or employer-contact questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booking entry is not a test result, an accusation of record, or evidence of deception. The person named in the booking can be booked by a spouse or employer and may never have filled the form. The examination can clear the named person. The booking row that records that someone paid to suspect them does not get that update. Emails can include those custom fields. 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.

Test-slot bookings and custom intake fields stored 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. Test-reason, subject-name, or employer-contact questions are fields you add; they are not documented defaults. ID scans or intake files are files you accept; they are not documented defaults. One booking entry can store a named person next to accusation text typed by someone else. A booking entry is not a test result, an accusation of record, or evidence of deception. 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 a test reason, subject name, or employer contact was sent. A page request from this script is not proof that a suspicion was described. The page URL can say polygraph even when no form is submitted. Consent timing has not been tested. Review which tags you enable on polygraph booking 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. Test-reason, subject-name, or employer-contact answers often depend on the fields you configure. A booking entry is not a test result, an accusation of record, or evidence of deception. A marketing-tag page request is not proof that a suspicion was described. The page URL can say polygraph even when no form is submitted. The named person can be booked by a spouse or employer and may never have filled the form. The examination can clear the named person. The booking row does not get that update. This page is about the booking form, not a surveillance file, a mediation intake, or an anonymous tip. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking page, and how long records and backups are kept. A "secure" or "confidential testing" 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 EPPA, polygraph admissibility, or polygraph accuracy. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking 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-polygraph-plugin-privacy