Firewood delivery plugin privacy
The standing order that files your gate code next to the winter you went quiet
A firewood delivery can look like a stack and a driveway. It is also a standing access note: stack it around back, the gate code is 4411, the dog is friendly, we are away till Sunday. That instructions field is a plaintext credential stored next to the address it opens. Recurring winter orders map which rural households heat with wood. A mid-January stop in reorders can be read as gone, hospitalized, or cold — the lead list often knows before the neighbors do. Stack-location, gate-code, dog-note, away-window, cord-count, delivery-cadence, and stop-reorder fields are configured, not documented defaults. Optional driveway or stack photos go in the site uploads folder. A delivery booking is not proof wood was stacked. A gate code is a stored instruction, not proof anyone used it. A winter silence is not proof the house is empty. A page request is not proof anyone ordered firewood. The page URL can say firewood 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 account pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, an occupancy-detection claim, a theft-risk claim, a fuel-dealer-licensing 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 standing orders, delivery bookings, and page tags go
Standing orders and forms handled on your WordPress site
Check which stack-location, gate-code, dog-note, away-window, cord-count, delivery-cadence, or stop-reorder fields you enable, who can open form entries and bookings, where uploaded driveway or stack 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 a delivery. Notification emails can also copy the same gate code and stack note off-site. One table can name the house, the gate code, the away window, and the winter cadence next to a name, even when the truck never comes. A later mid-January silence in that log can be read as an empty house. Ask your web vendor not to collect a gate code next to an address on the first public form, not to store away windows next to delivery cadence in one open submissions list, and to purge unused delivery bookings after the date passes. A privacy-policy page does not by itself limit who can export a customer list. A stored booking is not proof wood was stacked.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the firewood booking or account page. That page request can reach a vendor host before anyone submits. The page URL can say firewood even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and account pages if you do not want that page request. A browser scan cannot inspect stored gate codes, stack notes, or reorder gaps. A "seasonal customer" badge is not a verified storage path.
Firewood-delivery booking, standing-order, 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 firewood-logistics or route software without a WordPress.org listing is 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). 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 firewood delivery is a booking you create; a service name such as standing winter order, one-time cord drop, or restack is a label you configure. Neither is a documented default. Stack-location, gate-code, dog-note, away-window, cord-count, delivery-cadence, or stop-reorder questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked delivery is not proof wood was stacked, and a mid-January silence is not proof the house is empty. Cancelling or missing the slot later does not erase the gate code, stack note, away window, or cadence 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 delivery 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. | Delivery bookings, custom intake fields, and automatic confirmation emails 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. Stack-location, gate-code, dog-note, away-window, cord-count, delivery-cadence, or stop-reorder questions are fields you add; they are not documented defaults. A driveway or stack photo is a file you accept; that file type is not a documented default. A delivery request is not proof wood was stacked. A stop-reorder answer is a stored preference, not proof the house is empty. A winter silence in later bookings is not proof anyone left. A gate code is a stored instruction, not proof anyone used it. 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 an account row sits after a request that never became a delivery is not a documented default of the plugin. | Account and standing-order form entries stored in WordPress; file uploads 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 stack-location, gate-code, away-window, or stop-reorder field was sent. A page request from this script is not proof anyone ordered firewood. The page URL can say firewood even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and account pages. Keep marketing tags off those pages if you do not want that page request. A tagged delivery page can re-confirm firewood interest next to a stored address and gate code; this row does not claim a delivery from that request. | 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. Stack-location, gate-code, dog-note, away-window, cord-count, delivery-cadence, or stop-reorder fields often depend on the fields you configure. A delivery booking is not proof wood was stacked. A gate code is a stored instruction, not proof anyone used it. A winter silence is not proof the house is empty. A marketing-tag page request is not proof anyone ordered firewood. The page URL can say firewood even when no form is submitted. The gate code and the cadence can sit after the truck never comes. This page is about a standing order that files an access credential next to a winter reorder log, not a propane-delivery tank cadence, not a snow-removal two-address vacancy link, not an alarm-company away schedule, and not a medical-alert lives-alone list. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or account page, and how long records and backups are kept. A seasonal-customer 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 occupancy-detection claims, theft-risk claims, or fuel-dealer licensing. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and account 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-firewood-delivery-plugin-privacy