Security camera installation plugin privacy

The quote form that diagrams exactly where your cameras cannot see

A coverage map for a camera quote names which doors and which approaches get a lens. What it leaves blank is the blind spots. That map can sit in a form plugin entries table years after the install. A form can also collect an NVR app login and Wi-Fi details so the tech can finish setup, plus a site photo aimed down a driveway that can frame a slice of the neighbor's yard. That pairing can sit in one row any staffer can open. Coverage-map, doors, approaches, blind-spots, nvr-app-login, wifi-details, site-photo, driveway-photo, homeowner-name, phone, address, and install-date fields are configured, not documented defaults. Optional site photos go in the site uploads folder. A coverage map is a stored diagram, not proof cameras were installed. A door or approach label is a stored label, not a verified camera location. A blank on that map is a stored omission, not proof of a blind spot. An NVR app login is a stored secret, not proof of access to a recorder. A Wi-Fi detail is a stored credential, not proof of network access. A site photo is an upload, not proof of a neighbor, a driveway, or a camera view. A security-camera quote is not proof anyone booked an install. A page request is not proof anyone booked. The page URL can say security camera installation 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, an alarm-company claim, a home-theater claim, a handyman claim, a house-sitting claim, a CCTV-vendor claim, an NVR-SaaS 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 security-camera quotes, site photos, and page tags go

Install quotes and forms handled on your WordPress site

Check which coverage-map, doors, approaches, blind-spots, nvr-app-login, wifi-details, site-photo, driveway-photo, homeowner-name, phone, address, or install-date fields you enable, who can open form entries and bookings, where uploaded site photos 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 an install. Notification emails can also copy the same coverage maps, NVR app logins, Wi-Fi details, driveway photos, and addresses off-site. One table can name the house, the doors that get a lens, and the neighbor in a driveway photo next to a phone, even when the install never happens. Ask your web vendor not to collect an NVR app login next to a coverage map and a driveway photo on the first public form, not to store those site photos next to Wi-Fi details 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 cameras were installed.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the security-camera-installation booking or quote page. That page request can reach a vendor host before anyone submits. The page URL can say security camera installation 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 coverage maps, NVR app logins, or driveway photos. A "CCTV install" badge is not a verified storage path.

Security-camera-installation 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 CCTV or NVR 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 camera install is a booking you create; a service name such as security camera installation, CCTV quote, doorbell camera, or NVR setup is a label you configure. Neither is a documented default. The stored service name can say security camera installation in plain text before anyone arrives. Coverage-map, doors, approaches, blind-spots, nvr-app-login, wifi-details, homeowner-name, phone, address, or install-date questions are custom fields you add (textarea, select, or input); they are not documented defaults. A coverage map is a stored diagram, not proof cameras were installed. A door or approach label is a stored label, not a verified camera location. A blank on that map is a stored omission, not proof of a blind spot. An NVR app login is a stored secret, not proof of access to a recorder. A Wi-Fi detail is a stored credential, not proof of network access. A booked slot is not proof anyone booked an install, and is not proof cameras were mounted. Cancelling or missing the slot later does not erase the coverage map, NVR app login, Wi-Fi detail, or address already stored next to a name, and does not unsend a confirmation email already delivered. How long that pairing sits after a booking that never became an install is not a documented default of the plugin. The appointments list can show who is booked this week and at which address. 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.

Security-camera-installation 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. Coverage-map, doors, approaches, blind-spots, nvr-app-login, wifi-details, homeowner-name, phone, address, or install-date questions are fields you add; they are not documented defaults. Site photos, driveway photos, and coverage-map files are files you accept; those file types are not documented defaults. A coverage map is a stored diagram, not proof cameras were installed. A door or approach label is a stored label, not a verified camera location. A blank on that map is a stored omission, not proof of a blind spot. An NVR app login is a stored secret, not proof of access to a recorder. A Wi-Fi detail is a stored credential, not proof of network access. A site photo is an upload, not proof of a neighbor, a driveway, or a camera view. A security-camera quote is not proof anyone booked an install. 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 pairing sits after a request that never became an install is not a documented default of the plugin.

Quote and site-photo 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 coverage-map, nvr-app-login, or driveway-photo field was sent. A page request from this script on a security-camera-installation quote page is not proof anyone booked, and a pre-consent tag on that page can still treat security-camera-installation interest as an audience segment from the URL alone. The page URL can say security camera installation 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 security-camera-installation interest next to a stored address; this row does not claim an install 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. Coverage-map, doors, approaches, blind-spots, nvr-app-login, wifi-details, site-photo, driveway-photo, homeowner-name, phone, address, or install-date fields often depend on the fields you configure. A coverage map is a stored diagram, not proof cameras were installed. A door or approach label is a stored label, not a verified camera location. A blank on that map is a stored omission, not proof of a blind spot. An NVR app login is a stored secret, not proof of access to a recorder. A Wi-Fi detail is a stored credential, not proof of network access. A site photo is an upload, not proof of a neighbor, a driveway, or a camera view. A security-camera quote is not proof anyone booked an install. A marketing-tag page request is not proof anyone booked. The page URL can say security camera installation even when no form is submitted. The coverage map, the NVR app login, and the driveway photo can sit after a request that never became an install. This page is about the quote form that diagrams exactly where your cameras cannot see, not an alarm-company code and away-window form, not a home-theater AV install, not a handyman in-home access ticket, and not a house-sitting empty-nights calendar. 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 "CCTV install" 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 alarm-company, home-theater, handyman, house-sitting, CCTV-vendor, or NVR-SaaS claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and quote pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-security-camera-installation-plugin-privacy