Skip tracing plugin privacy

The locate request that files who is hunting whom

A skip-tracing WordPress stack is not only a contact form — it is a registry of who is looking for whom. Every locate request can store the target's last-known addresses, plates, and workplaces next to the client's reason for hunting them. The person named as the target never consented and may have moved specifically to not be found. No breach required: the locate request is the product and the leak. Closed jobs still name both parties. A marketing tag on the same locate-request page can send a page request to a vendor host before anyone submits — and that page request alone can treat skip-tracing intent as an audience segment from the URL. A page request is not proof anyone ordered a locate. A locate request is not proof anyone was found. A reason-for-locate note is a field you configure, not a default. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where uploaded files land, which tags load on the locate-request page, and how long past locate rows, files, and backups are kept.

Documentation review only. This is not legal advice, a locate-success or skip-trace-accuracy claim, a debt-recovery or repossession guide, a service-of-process or court-procedure assessment, 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, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.

Where locate requests, target details, and page tags go

Entries, uploads, and the who-hunts-whom registry on your WordPress site

Check which target-address, plate, workplace, employer, alias, SSN-last-4, client-name, or reason-for-locate fields you enable, who can open form entries, where uploaded support files live in the uploads folder, which inboxes receive copies, and how long past locate rows, files, and backups are kept after the job ends. Notification emails can also copy the same two identities off-site. Ask your web vendor not to put every target detail next to a client reason-for-locate on one open entries table when a short job ID would do — and ask how long closed locate rows are kept.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the skip-tracing locate-request page. That page request can reach a vendor host before anyone submits. Review which tags you enable, account access, and retention there. Keep marketing tags off locate-intake and upload pages if you do not want that page request. A browser scan cannot inspect stored form entries or uploaded files. A "secure locate" badge is not a verified storage or visibility path.

Skip-tracing locate intake, file-upload, 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 skip-tracing SaaS tools without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
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 target photos, old utility bills, plate photos, employment records, or other locate-support files you accept depends on the fields you add; they are not fixed skip-tracing defaults. Filenames chosen by visitors can include full legal names or plate fragments. An uploaded address scan is not proof anyone was found. 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/uploadsBrowser hosts not verifiedNot assessedNot tested
  • None
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. Target last-known address, plate, workplace, employer, alias, SSN-last-4, client name, or reason-for-locate fields depend on the fields you add — they are not fixed skip-tracing defaults. One client-authored entry can store who is hunting whom next to the target's last-known addresses — and the person named as the locate target never consented and may have moved specifically to not be found. A locate request is not proof anyone was found. A reason-for-locate note is a configured field, not a default. Optional payment, CRM, or spam-protection integrations send data only when enabled. Retention of entry rows after the job ends is not specified as a default purge. Public form browser hosts are unverified.

Locate-request form entries stored in your WordPress databaseBrowser 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, 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 target address, plate, workplace, or reason-for-locate note was sent. A page request from this script on a skip-tracing locate-request page is not proof anyone ordered a locate — and a pre-consent tag on that page can still treat skip-tracing intent as an audience segment from the URL alone. The page URL can say skip tracing even when no form is submitted. Consent timing has not been tested. Review which tags you enable on locate-intake and document-upload 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. Target addresses, plates, workplaces, or reason-for-locate notes often depend on the fields you configure. A locate request is not proof anyone was found. A reason-for-locate note is a configured field, not a default. A marketing-tag page request is not proof anyone ordered a locate. Closing the job later does not erase the two identities already stored next to each other — and closed locate rows may still show who was hunting whom. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the locate-request page, and how long past locate rows and backups are kept. A "secure locate" badge is not a verified storage or visibility path. Consent timing, access controls, and retention have not been tested. This page describes storage and locate-intake visibility paths only and does not assess locate success, skip-trace accuracy, debt recovery, repossession, service of process, court procedure, or legal advice. Review stored records, uploads, connected services, exports, notification emails, marketing tags on locate pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-skip-tracing-plugin-privacy