Holiday lighting plugin privacy
The install calendar that schedules your house to be admired and your absence to be known
The quote form takes roofline photos, lot size, and the display budget — an itemized inventory of high-value exterior decor pinned to a street address. Then the calendar does the rest: install date, teardown date, and the "install while we are away" note turn a seasonal display into a published wealth signal with an attached vacancy window, refreshed every year by design. Those fields are configured, not documented defaults. A holiday-lighting booking is a calendar row, not proof lights were hung or that anyone left town. A roofline, lot-size, budget, or away-note answer is a form answer or uploaded file, not a verified vacancy or wealth appraisal. A page request is not proof anyone booked an install. The page URL can say holiday lighting even when no form is submitted. Ask what happens to the name, the service address, the roofline photos, the display budget, and the install-plus-teardown calendar after a season ends — the stack that paired admiration with absence outlives the lights. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking or quote page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a home-security-advice claim, a vacancy-inference claim, a burglary-risk claim, a display-budget-valuation claim, a trespass 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, bookings, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where holiday-lighting bookings, install calendars, and page tags go
Bookings and install quotes on your WordPress site
Check which roofline-photo, lot-size, display-budget, install-date, teardown-date, away-note, name, or service-address fields you enable, who can open form entries and holiday-lighting bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a season ends — when the name-plus-address-plus-calendar row still holds a wealth-signal display next to an absence window. Notification emails can also copy those fields off-site. One table can list every "Alex · 19 Oak Ridge · roofline photos · lot 0.4 acre · $8k display · install Dec 1 · tear-down Jan 5 · install while away" stack next to a customer name. Ask your web vendor not to keep roofline photos and away notes next to service addresses and names in one open submissions list longer than operations need, and to purge those fields when a season ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored holiday-lighting booking is not proof lights were hung or that anyone left town. A roofline, lot-size, budget, or away-note answer is not a verified vacancy or wealth appraisal.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the booking or quote page. That page request can reach a vendor host before anyone submits. The page URL can say holiday lighting 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 entries or bookings. A "holiday lighting privacy" badge is not a verified storage path.
Holiday-lighting booking, install-calendar, 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 holiday-lighting SaaS tools without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Easy Appointments Documented self-hosted appointment plugin marketed for service businesses (plugin version 4.0.3). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A December install window, a January teardown slot, or an "install while away" note is a booking you create; a service name such as roofline hang or curb display is a label you configure. Neither is a documented default. Roofline-photo, lot-size, display-budget, install-date, teardown-date, away-note, or service-address questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof lights were hung or that anyone left town — and a CSV export of "Alex · 19 Oak Ridge · roofline photos · lot 0.4 acre · $8k display · install Dec 1 · tear-down Jan 5 · install while away" next to a customer name is still a calendar that pairs a wealth-signal display with an absence window. Emails can include those custom fields and copy the appointment off-site. 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. | Holiday-lighting bookings stored on your WordPress site | 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. Roofline-photo, lot-size, display-budget, install-date, teardown-date, away-note, or service-address fields are fields you add; they are not documented defaults. Completing the form can store a name-plus-address-plus-calendar stack ("Alex · 19 Oak Ridge · roofline photos · lot 0.4 acre · $8k display · install Dec 1 · tear-down Jan 5 · install while away") — typed or uploaded once so a shop can quote a display, into the same tables as a "holiday lighting" label. A roofline, lot-size, budget, or away-note answer is a form answer or uploaded file, not a verified vacancy or wealth appraisal. A holiday-lighting booking is a calendar row, not proof lights were hung or that anyone left town — and a staff login can open "Alex, 19 Oak Ridge, roofline photos, lot 0.4 acre, $8k display, install Dec 1, tear-down Jan 5, install while away" next to everyone else's resume. 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. | Name, service address, and calendar answers stored in WordPress; optional roofline photos 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, 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 roofline, lot-size, budget, install-date, teardown-date, or away-note field was sent. A page request from this script is not proof anyone booked an install. The page URL can say holiday lighting even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and quote pages. | 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. Roofline-photo, lot-size, display-budget, install-date, teardown-date, away-note, or service-address fields often depend on the fields you configure. A holiday-lighting booking is a calendar row, not proof lights were hung or that anyone left town. A roofline, lot-size, budget, or away-note answer is a form answer or uploaded file, not a verified vacancy or wealth appraisal. A marketing-tag page request is not proof anyone booked an install. The page URL can say holiday lighting even when no form is submitted. The name-plus-address-plus-calendar row that paired admiration with absence for a shop — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that install-calendar stack, not a pet-sitting vacancy-as-product booking, a snow-removal seasonal route log, an alarm-company security-stack inventory, or a pressure-washing portfolio publication. Ask your web vendor who can open entries, whether a marketing tag loads on the booking or quote page, and how long records and backups are kept. A "holiday lighting privacy" or "seasonal install ready" 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 home-security advice, vacancy inference, or display-budget valuation. Review stored records, bookings, 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
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-holiday-lighting-plugin-privacy