Bodyguard plugin privacy

The threat-assessment intake that lists who scares you and your daily route

To hire protection you first write the stalker's handbook. A quote form can collect the named person you fear, a restraining-order file, your home address, your gym schedule, and your kids' school run. That threat-assessment row can sit in a form plugin entries table any staffer can open. Named-person, restraining-order, home-address, daily-route, gym-schedule, school-run, client-name, phone, and protection-start-date fields are configured, not documented defaults. Optional restraining-order files go in the site uploads folder. A quote request is not proof protection was hired. A named person is a stored note, not a verified threat. A restraining-order file is an upload, not proof a court issued an order. A daily-route field is a stored schedule, not proof anyone follows it. A gym-schedule field is a stored note, not proof of a gym membership. A school-run field is a stored note, not proof children exist or attend that school. A home address is a stored location, not a verified residence. A protection-start-date is a stored date, not proof a detail started. A page request is not proof anyone booked. The page URL can say bodyguard 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 booking and quote pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a protection-effectiveness claim, a licensing claim, a concealed-carry claim, a threat-credibility claim, a restraining-order-validity claim, a stalking-crime claim, a domestic-violence-shelter claim, a private-investigator claim, a security-guard-staffing 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 bodyguard quotes, restraining-order files, and page tags go

Protection quotes and forms handled on your WordPress site

Check which named-person, restraining-order, home-address, daily-route, gym-schedule, school-run, client-name, phone, or protection-start-date fields you enable, who can open form entries and bookings, where uploaded restraining-order files live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a request that never became a hired detail. Notification emails can also copy the same named-person notes, restraining-order files, home addresses, daily routes, gym schedules, school-run notes, and client names off-site. One table can name who you fear, your home, and your school run next to a phone, even when the detail is never hired. Ask your web vendor not to collect a named person next to a home address and a daily route on the first public form, not to store that threat-assessment next to a restraining-order file in one open submissions list, and to purge unused quotes after the date passes. A privacy-policy page does not by itself limit who can export a quote list or republish an upload. A stored quote is not proof protection was hired.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the bodyguard booking or quote page. That page request can reach a vendor host before anyone submits. The page URL can say bodyguard even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and quote pages if you do not want that page request. A browser scan cannot inspect stored named-person notes, restraining-order files, or daily routes. A "close protection" badge is not a verified storage path.

Bodyguard booking, quote, 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 executive-protection or threat-assessment software without a WordPress.org listing is outside this sample.

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

Documented self-hosted appointment plugin marketed for service businesses (plugin version 4.0.3). The listing documents automatic email notifications: customers get instant booking confirmations; staff get notified; templates can include booking information and custom fields; customers can confirm or cancel via a link in the email. WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A bodyguard quote is a booking you create; a service name such as bodyguard, executive protection, close protection, threat assessment, or personal security is a label you configure. Neither is a documented default. Named-person, restraining-order, home-address, daily-route, gym-schedule, school-run, client-name, phone, or protection-start-date questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked quote is not proof protection was hired, and is not a verified threat. Cancelling or missing the slot later does not erase the named person, restraining-order note, home address, daily route, gym schedule, or school-run already stored next to a name, and does not unsend a confirmation email already delivered. How long that row sits after a booking that never became a hired detail is not a documented default of the plugin. 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.

Protection bookings, custom intake fields, and automatic confirmation emails 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. Named-person, restraining-order, home-address, daily-route, gym-schedule, school-run, client-name, phone, or protection-start-date questions are fields you add; they are not documented defaults. A restraining-order file is a file you accept; that file type is not a documented default. A quote request is not proof protection was hired. A named person is a stored note, not a verified threat. A restraining-order file is an upload, not proof a court issued an order. A daily-route field is a stored schedule, not proof anyone follows it. A gym-schedule field is a stored note, not proof of a gym membership. A school-run field is a stored note, not proof children exist or attend that school. A home address is a stored location, not a verified residence. A protection-start-date is a stored date, not proof a detail started. 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 quote sits after a request that never became a hired detail is not a documented default of the plugin.

Quote and restraining-order 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 named-person, restraining-order, or daily-route field was sent. A page request from this script is not proof anyone booked. The page URL can say bodyguard even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and quote pages. Keep marketing tags off those pages if you do not want that page request. A tagged quote page can re-confirm bodyguard interest next to a stored address and files; this row does not claim a hired detail from that request.

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. Named-person, restraining-order, home-address, daily-route, gym-schedule, school-run, client-name, phone, or protection-start-date fields often depend on the fields you configure. A quote request is not proof protection was hired. A named person is a stored note, not a verified threat. A restraining-order file is an upload, not proof a court issued an order. A daily-route field is a stored schedule, not proof anyone follows it. A gym-schedule field is a stored note, not proof of a gym membership. A school-run field is a stored note, not proof children exist or attend that school. A home address is a stored location, not a verified residence. A protection-start-date is a stored date, not proof a detail started. A marketing-tag page request is not proof anyone booked. The page URL can say bodyguard even when no form is submitted. The named person, the home address, and the daily route can sit after the quote never becomes a hired detail. This page is about a threat-assessment intake that lists who scares you and your daily route, not a staffed property-guard quote, not a shelter address that is not supposed to exist, and not a watching-someone-else investigator intake. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or quote page, and how long records and backups are kept. A protection-badge export 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 protection-effectiveness, licensing, concealed-carry, threat-credibility, restraining-order-validity, stalking-crime, domestic-violence-shelter, private-investigator, or security-guard-staffing claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and quote 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-bodyguard-plugin-privacy