Security guard plugin privacy

The quote form that lists what is worth stealing and when nobody is watching

A guard-service quote form can look like a site address and a start date. It is also a casing document. To price a patrol, the form asks what is worth protecting and when the building is empty. Asset, incident-history, coverage-gap, and patrol-schedule fields are configured, not documented defaults. Site-photo uploads can sit in the same folder. That row is a map of value plus a schedule of absence, stored in a form-plugin table by the client. The patrol can end. The inventory of what to take, and when nobody is watching, can stay. A quote request is not proof a site is unguarded. An incident-history answer is not a police report. A page request is not proof anyone requested coverage. The page URL can say security guard 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 quote and site-assessment pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a security-licensing claim, a negligent-security-liability claim, an insurance-requirement claim, a crime-statistics 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 quotes, site assessments, and page tags go

Quotes and site-assessment bookings handled on your WordPress site

Check which asset, incident-history, coverage-gap, or patrol-schedule fields you enable, who can open form entries and bookings, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a quote that never became a contract. Notification emails can also copy the same site map off-site. One table can list every camera blind spot even when only the client typed. Ask your web vendor not to collect an asset list or a coverage-gap map on the first public form, not to store that inventory next to a patrol schedule in one open submissions list, and to purge quotes after the work ends. A privacy-policy page does not by itself limit who can export a quote list. A stored quote is not proof a site is unguarded.

Page tags handled by a vendor

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

Security-guard quote, site-assessment, 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 guard-ops or alarm-monitoring 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 site-assessment visit is a booking you create; a service name such as guard quote or overnight patrol intake is a label you configure. Neither is a documented default. Asset, incident-history, coverage-gap, or patrol-schedule questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked assessment is not a staffing contract and is not proof a site is unguarded. Cancelling or missing the visit later does not erase the contact answers already stored next to a site address, and does not unsend a confirmation email already delivered. How long that row sits after a quote that never became a contract 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.

Site-assessment 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. Asset, incident-history, coverage-gap, or patrol-schedule questions are fields you add; they are not documented defaults. A site photo, a floor-plan PDF, or a camera-layout image is a file you accept; none of those file types is a documented default. A quote request is not proof a site is unguarded. An incident-history answer is not a police report. 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 contract is not a documented default of the plugin.

Quote 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 an asset, incident-history, coverage-gap, or patrol-schedule field was sent. A page request from this script is not proof anyone requested coverage. The page URL can say security guard even when no form is submitted. Consent timing has not been tested. Review which tags you enable on quote and site-assessment pages. Keep marketing tags off those pages if you do not want that page request. A tagged quote page can re-confirm a site that already listed valuables and shift gaps; this row does not claim a coverage outcome 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. Asset, incident-history, coverage-gap, or patrol-schedule fields often depend on the fields you configure. A quote request is not proof a site is unguarded. An incident-history answer is not a police report. A marketing-tag page request is not proof anyone requested coverage. The page URL can say security guard even when no form is submitted. The asset list can sit after the patrol ends. This page is about a quote form that inventories a site, not an alarm-company hardware quote, an executive-protection threat narrative, a locksmith job, a crime-scene cleanup intake, 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 or site-assessment 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 security licensing, negligent-security liability, insurance requirements, or crime statistics. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on quote and site-assessment 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-security-guard-plugin-privacy