Snow removal plugin privacy
The contract that links your two addresses and says which one is empty
A snowbird contract is the only service form that links a customer's two addresses and states which one is empty: "bill the Florida address, clear the Michigan driveway all season." That single row connects a northern house that will stand vacant for four months to the exact faraway place its owners are — plus the per-storm GPS-stamped service log proving, storm by storm, that no car ever moved. Route siblings know a house's rhythm; this one documents its abandonment, with a forwarding address. Those fields are configured, not documented defaults. A snow-removal booking is a calendar row, not proof anyone left town or that a driveway was cleared. A service-address or storm-log answer is a form answer or uploaded file, not a verified vacancy. A page request is not proof anyone signed a snowbird contract. The page URL can say snow removal even when no form is submitted. Ask what happens to the service address, the billing address, the season window, the gate code, and the per-storm GPS log after the season ends — the stack that paired an empty northern house with a southern forwarding address outlives the last plow. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the season-intake or storm-log page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a snow-removal-contract-law claim, a home-security-advice claim, a vacancy-inference claim, an insurer-underwriting claim, a trespass-law claim, a seasonal-service-regulation 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 snowbird contracts, storm logs, and page tags go
Contracts and bookings on your WordPress site
Check which service-address, billing-address, season-window, gate-code, vehicle-leave-behind, per-storm GPS-log, or intake-upload fields you enable, who can open form entries and season bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a season ends — when the service-plus-billing-plus-season-plus-storm-log row still holds the vacant northern house next to the southern forwarding address. Notification emails can also copy those fields off-site. One table can list every "bill: 214 Palm Ct Naples FL · clear: 88 Maple Dr Ann Arbor MI · Nov 15–Mar 31 · storm 1/12 GPS ✓, 1/19 GPS ✓ — no car moved" stack next to a customer name. Ask your web vendor not to keep linked address rows next to gate codes and storm GPS logs in one open submissions list longer than operations need, and to purge those fields when a season closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored snow-removal booking is not proof anyone left town or that a driveway was cleared. A service-address or storm-log answer is not a verified vacancy.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the season-intake or storm-log page. That page request can reach a vendor host before anyone submits. The page URL can say snow removal even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off season-intake and storm-log pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "snow removal privacy" badge is not a verified storage path.
Snowbird-contract, storm-log booking, 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 snow-removal 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 Tuesday post-storm clear window or a season kickoff slot is a booking you create; a service name such as snowbird season or driveway plow is a label you configure. Neither is a documented default. Service-address, billing-address, season-window, gate-code, vehicle-leave-behind, or per-storm GPS-log questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof anyone left town or that a driveway was cleared — and a CSV export of "bill: 214 Palm Ct Naples FL · clear: 88 Maple Dr Ann Arbor MI · Nov 15–Mar 31 · storm 1/12 GPS ✓, 1/19 GPS ✓ — no car moved" next to a customer name is still a calendar that pairs a vacant northern house with a southern billing address. 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. | Snow-removal season 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. Service-address, billing-address, season-window, gate-code, vehicle-leave-behind, or per-storm GPS-log fields are fields you add; they are not documented defaults. Completing the form can store a service-plus-billing-plus-season-plus-storm-log stack ("bill: 214 Palm Ct Naples FL · clear: 88 Maple Dr Ann Arbor MI · Nov 15–Mar 31 · storm 1/12 GPS ✓, 1/19 GPS ✓ — no car moved") — typed once so a contractor can bill south and clear north, into the same tables as a "snow removal" label. A service-address or storm-log answer is a form answer or uploaded file, not a verified vacancy. A snow-removal booking is a calendar row, not proof anyone left town — and a staff login can open "Jordan, bill Naples FL, clear Ann Arbor MI, gate 4412, storm-1-12.jpg GPS ✓" 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. | Service, billing, season, and storm-log answers stored in WordPress; optional GPS 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 service-address, billing-address, season-window, or storm-log field was sent. A page request from this script is not proof anyone signed a snowbird contract. The page URL can say snow removal even when no form is submitted. Consent timing has not been tested. Review which tags you enable on season-intake and storm-log 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. Service-address, billing-address, season-window, gate-code, vehicle-leave-behind, or per-storm GPS-log fields often depend on the fields you configure. A snow-removal booking is a calendar row, not proof anyone left town or that a driveway was cleared. A service-address or storm-log answer is a form answer or uploaded file, not a verified vacancy. A marketing-tag page request is not proof anyone signed a snowbird contract. The page URL can say snow removal even when no form is submitted. The service-plus-billing-plus-season-plus-storm-log row that links two addresses and says which one is empty — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that snowbird abandonment-with-forwarding-address stack, not a summer pool-service route sheet, a christmas-lights install with away dates, a dog-boarding vacation window, an RV-rental route-plus-vacancy booking, or an HOA two-address community record. Ask your web vendor who can open entries, whether a marketing tag loads on the season-intake or storm-log page, and how long records and backups are kept. A "snow removal privacy" or "seasonal contractor compliant" 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 snow-removal contract law, home-security advice, vacancy inference, insurer underwriting, trespass law, or seasonal-service regulation. Review stored records, bookings, connected services, exports, notification emails, marketing tags on season-intake and storm-log 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-snow-removal-plugin-privacy