Private investigator plugin privacy
The intake form that names someone who never consented
A case-inquiry form names a person who never visited the site and never consented — the subject of the investigation. A typical inquiry names the subject, their address and vehicle, the suspected behavior (infidelity, fraud, custody violations), and the client's relationship to them. A public uploads directory, a marketing tag on the inquiry page, or retained entries expose two people's private lives per row — and reveal that an investigation exists at all. Those fields are configured, not documented defaults. A case booking is a calendar row, not proof anyone was investigated or that a suspicion is accurate. A subject or photo answer is a form answer or uploaded file, not a verified finding. A page request is not proof anyone opened a case. The page URL can say private investigator even when no form is submitted. Ask what happens to the subject name, the address, the vehicle, the suspicion line, and the photos after a case closes — the stack that named someone who never consented outlives the consult. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the inquiry page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, an investigation-legality claim, a licensing claim, a surveillance-law claim, a domestic-relations-discovery 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 case intakes, inquiry bookings, and page tags go
Intakes and bookings on your WordPress site
Check which subject-name, subject-address, vehicle, suspected-behavior, client-relationship, photo, or intake-upload fields you enable, who can open form entries and case bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a case closes — when the subject-plus-address-plus-suspicion row still holds two people's private lives. Notification emails can also copy those fields off-site. One table can list every "subject: Alex Rivera · 12 Oak St · plate ABC-1234 · suspected: infidelity · client: spouse · photos: subject-driveway.jpg" stack next to a client name. Ask your web vendor not to keep subject photos and suspicion lines next to client relationships in one open submissions list longer than operations need, and to purge those fields when a case closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored case booking is not proof anyone was investigated or that a suspicion is accurate. A subject or photo answer is not a verified finding.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the inquiry page. That page request can reach a vendor host before anyone submits. The page URL can say private investigator even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off inquiry pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "private investigator privacy" badge is not a verified storage path.
Private-investigator case intake, inquiry booking, 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 PI SaaS tools without a WordPress.org listing are 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A Tuesday consult window or a case-intake slot is a booking you create; a service name such as surveillance consult or background inquiry is a label you configure. Neither is a documented default. Subject-name, subject-address, vehicle, suspected-behavior, client-relationship, or photo questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof anyone was investigated or that a suspicion is accurate — and a CSV export of "subject: Alex Rivera · 12 Oak St · plate ABC-1234 · suspected: infidelity · client: spouse · photos: subject-driveway.jpg" next to a client name is still a calendar that pairs a non-consenting subject with a case file. Emails can include those custom fields and copy the appointment off-site. 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. | Private-investigator case bookings stored 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. Subject-name, subject-address, vehicle, suspected-behavior, client-relationship, or photo fields are fields you add; they are not documented defaults. Completing the form can store a subject-plus-address-plus-suspicion stack ("subject: Alex Rivera · 12 Oak St · plate ABC-1234 · suspected: infidelity · client: spouse · photos: subject-driveway.jpg") — typed once so an agency can quote a case, into the same tables as a "private investigator" label. A subject or photo answer is a form answer or uploaded file, not a verified finding. A case booking is a calendar row, not proof anyone was investigated — and a staff login can open "Alex Rivera, 12 Oak St, ABC-1234, infidelity, spouse, subject-driveway.jpg" next to everyone else's resume. Notification emails can copy field values and files off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | Subject, address, suspicion, and photo answers stored in WordPress; optional photos 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 a subject-name, address, suspicion, or photo field was sent. A page request from this script is not proof anyone opened a case. The page URL can say private investigator even when no form is submitted. 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. Subject-name, subject-address, vehicle, suspected-behavior, client-relationship, or photo fields often depend on the fields you configure. A case booking is a calendar row, not proof anyone was investigated or that a suspicion is accurate. A subject or photo answer is a form answer or uploaded file, not a verified finding. A marketing-tag page request is not proof anyone opened a case. The page URL can say private investigator even when no form is submitted. The subject-plus-address-plus-suspicion row that named someone who never consented — that is a storage path next to client names, not a feature these plugins claim. This page is about that third-party-subject intake, not an answering-service caller portal, a process-server delivery file, a reputation-management oppo dossier, a virtual-mailbox correspondence archive, or an HR consulting someone-else's-problem form. Ask your web vendor who can open entries, whether a marketing tag loads on the inquiry page, and how long records and backups are kept. A "private investigator privacy" or "confidential intake" 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 investigation legality, licensing, surveillance law, or domestic-relations discovery. Review stored records, bookings, connected services, exports, notification emails, marketing tags on inquiry pages, and backups.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-private-investigator-plugin-privacy