Bounty hunter plugin privacy
The intake that files a wanted poster about someone who never visited the site
A recovery intake can store a last-known address, known associates, a vehicle, and an armed-or-dangerous checkbox. Those fields describe a third party who never saw the site and never consented. Subject photos, vehicle photos, and case-support PDFs can sit in the site uploads folder. A case-number field can sit next to a requester name in the same entries table. That table can sit after the recovery job ends. Subject-name, last-known-address, known-associate, vehicle, armed-or-dangerous, warrant-or-case-number, photo, requester-name, and phone fields are configured, not documented defaults. Optional photo and case-support files go in the site uploads folder. A subject name is a stored name, not proof anyone is wanted. A last-known-address field is a stored location, not proof anyone lives there. A known-associate field is a stored name, not proof of a relationship. A vehicle field is a stored description, not proof of ownership. An armed-or-dangerous checkbox is a stored flag, not proof anyone is armed. A warrant or case-number field is a stored identifier, not proof a warrant exists. A photo is an upload, not proof of identity. A recovery intake is not proof anyone was arrested. A page request is not proof anyone hired recovery. The page URL can say bounty hunter 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 recovery-intake pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, an arrest claim, a warrant-validity claim, a bail-enforcement-license claim, a skip-tracing-as-a-product claim, a repossession claim, a process-server 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, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where recovery-intake rows, photo uploads, and page tags go
Recovery forms and uploads handled on your WordPress site
Check which subject-name, last-known-address, known-associate, vehicle, armed-or-dangerous, warrant-or-case-number, photo, requester-name, or phone fields you enable, who can open form entries, where uploaded photos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after the recovery job ends. Notification emails can also copy the same subject names, last-known addresses, known-associate names, vehicle descriptions, armed-or-dangerous flags, case numbers, photos, and requester names off-site. One table can name a third party, a last-known address, and known associates next to an armed-or-dangerous flag, even when no recovery happens. Ask your web vendor not to collect a subject name next to a last-known address and known associates on the first public form, not to store those photos next to a case number in one open submissions list, and to purge unused recovery rows after the job ends. A privacy-policy page does not by itself limit who can export a recovery list or republish an upload. A stored recovery row is not proof anyone was arrested.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the bounty-hunter recovery-intake page. That page request can reach a vendor host before anyone submits. The page URL can say bounty hunter even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off recovery-intake and upload pages if you do not want that page request. A browser scan cannot inspect stored subject names, last-known addresses, or photo files. A "fugitive recovery" badge is not a verified storage path.
Bounty-hunter recovery-form, 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 bail-enforcement or fugitive-recovery 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 |
|---|---|---|---|---|---|---|
| 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. That is the same pattern Contact Form 7 documents for its default file field. That cleanup does not remove copies already sent as email attachments. Which subject photos, vehicle photos, case-support PDFs, or other recovery-support files you accept depends on the fields you add; they are not fixed bounty-hunter defaults. Filenames chosen by visitors can include a subject name, a last-known address, or a case number. A photo is an upload, not proof of identity. A vehicle photo is an upload, not proof of ownership. A case-support PDF is an upload, not proof a warrant exists. 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/uploads | 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, last-known-address, known-associate, vehicle, armed-or-dangerous, warrant-or-case-number, requester-name, or phone questions are fields you add; they are not documented defaults. Subject photos, vehicle photos, and case-support PDFs are files you accept; those file types are not documented defaults. A subject name is a stored name, not proof anyone is wanted. A last-known-address field is a stored location, not proof anyone lives there. A known-associate field is a stored name, not proof of a relationship. A vehicle field is a stored description, not proof of ownership. An armed-or-dangerous checkbox is a stored flag, not proof anyone is armed. A warrant or case-number field is a stored identifier, not proof a warrant exists. A photo is an upload, not proof of identity. A recovery intake is not proof anyone was arrested. 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 recovery row sits after the job ends is not a documented default of the plugin. | Recovery-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, 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 subject-name, last-known-address, or armed-or-dangerous field was sent. A page request from this script on a bounty-hunter recovery-intake page is not proof anyone hired recovery, and a pre-consent tag on that page can still treat bounty-hunter interest as an audience segment from the URL alone. The page URL can say bounty hunter even when no form is submitted. Consent timing has not been tested. Review which tags you enable on recovery-intake and document-upload pages. Keep marketing tags off those pages if you do not want that page 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. Subject-name, last-known-address, known-associate, vehicle, armed-or-dangerous, warrant-or-case-number, photo, requester-name, or phone fields often depend on the fields you configure. A subject name is a stored name, not proof anyone is wanted. A last-known-address field is a stored location, not proof anyone lives there. A known-associate field is a stored name, not proof of a relationship. A vehicle field is a stored description, not proof of ownership. An armed-or-dangerous checkbox is a stored flag, not proof anyone is armed. A warrant or case-number field is a stored identifier, not proof a warrant exists. A photo is an upload, not proof of identity. A recovery intake is not proof anyone was arrested. A marketing-tag page request is not proof anyone hired recovery. The page URL can say bounty hunter even when no form is submitted. The subject name, the last-known address, and the photo files can sit after the recovery job ends. This page is about a recovery intake that files a wanted poster about someone who never visited, not a bail-bond application, not desk-based skip-tracing as the product, not asset repossession, and not civil process delivery. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the recovery-intake page, and how long records and backups are kept. A "fugitive recovery" 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 arrest, warrant-validity, bail-enforcement-license, skip-tracing-as-a-product, repossession, or process-server claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on recovery pages, and backups.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress forms privacy
- WordPress file upload plugin privacy
- WordPress map plugin privacy
- All privacy guides
/wp-bounty-hunter-plugin-privacy