Executive protection plugin privacy

The quote form that explains who is threatening you

To buy protection you must first write down the threat. A quote form can ask who is following you, why, and for how long. Stalker-name, ex-history, schedule, address, threat-letter, or photo fields are configured, not documented defaults. That row can hold two files at once: you at your most exposed, and a named third party accused in a form that no court reviewed. The protection detail ends. The row describing the threat, and the person it names, can stay. A quote request is not a verified threat. A named person is not a court finding. A photo upload is not proof the person in it is a threat. A page request is not proof anyone is in danger. The page URL can say executive protection 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 the quote page, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a private-security-licensing claim, a restraining-order claim, a stalking-law 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, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.

Where quotes, threat files, and page tags go

Quotes and threat files handled on your WordPress site

Check which stalker-name, ex-history, schedule, address, threat-letter, or photo fields you enable, who can open form entries and the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a protection detail that has ended. Notification emails can also copy the same named third party off-site. One table can list every person a client named even when only the client typed. Ask your web vendor not to collect a named-threat narrative on the first public form, not to store that file next to a schedule or address in one open submissions list, and to purge quotes after the work ends. A privacy-policy page does not by itself limit who can open an uploads folder. A stored quote is not a verified threat.

Page tags handled by a vendor

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

Executive-protection quote, threat-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 close-protection or security-ops software without a WordPress.org listing is 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). Version 1.4.0 drag-n-drop-upload-cf7.php defines wpcf7_dnd_dir as wp_dndcf7_uploads. The listing states the free version moves files to wp-content/uploads/wp_dndcf7_uploads, attaches them to mail, then removes them from that temporary folder about one hour after submission. That cleanup does not remove copies already sent as email attachments. A threat letter or watch-for photo is a file you accept; it is not a documented default. The uploads folder can hold those files next to the quote list. A declined quote can still leave the photo until the documented cleanup, and the email copy can remain. An uploaded photo is not a verified threat. Pro documents saving to the Media Library, changing the upload directory, auto-delete timers, and remote storage to OneDrive, Google Drive, Amazon S3, Dropbox, or FTP. Public upload-page browser hosts are unverified.

Visitor files stored under wp-content/uploads/wp_dndcf7_uploadsBrowser 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. Stalker-name, ex-history, schedule, address, threat-letter, or photo questions are fields you add; they are not documented defaults. A threat letter or watch-for photo is a file you accept; it is not a documented default. Completing the form can record a quote request. A submitted quote is not a verified threat. A named person is not a court finding. A photo upload is not proof the person in it is a threat. A staff login can open the named third party next to contact details and other configured fields. The uploads folder can hold a threat letter after the protection detail ends. 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.

Quote entries stored in WordPress; threat-letter and photo 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 stalker-name, schedule, or threat-letter field was sent. A page request from this script is not proof anyone is in danger. The page URL can say executive protection even when no form is submitted. Consent timing has not been tested. Review which tags you enable on quote 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. Stalker-name, ex-history, schedule, address, threat-letter, or photo fields often depend on the fields you configure. A quote request is not a verified threat. A named person is not a court finding. A photo upload is not proof the person in it is a threat. A marketing-tag page request is not proof anyone is in danger. The page URL can say executive protection even when no form is submitted. The threat letter can sit in the same uploads folder after the protection detail ends. This page is about a quote form that names a threat, not a security-guard staffing form, an alarm-company hardware quote, a private-investigator case file, a reputation-management intake, a firearms-training signup, a polygraph booking, or a generic WordPress security plugin. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the quote page, and how long records and backups are kept. A "secure" or "confidential quote" 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 private-security licensing, restraining-order law, or stalking law. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on quote 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-executive-protection-plugin-privacy