Propane delivery plugin privacy
The fill-up schedule that knows when your house goes cold
A propane fill-up can look like a date and a tank. It is also a running log of how much fuel a house uses, when the tank was last filled, and which dates were skipped. Recurring delivery turns a WordPress customer account into consumption telemetry. Tank-size, usage-cadence, auto-fill-date, skipped-fill, driver-notes, gate-code, and tank-location fields are configured, not documented defaults. Optional tank photos or account documents go in the site uploads folder. A quiet winter gap in that log can be read as nobody living there. Occupancy inferred from fuel. The driver-notes field can hold tank behind garage and a gate code next to the address. A fill-up booking is not proof a tank was filled. A skipped fill is not proof of money trouble. A winter gap is not proof the house is empty. A gate code is a stored instruction, not proof anyone used it. A page request is not proof anyone ordered propane. The page URL can say propane 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, a utility-regulation claim, a fuel-dealer-licensing claim, an occupancy-detection claim, a theft-risk 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 tank accounts, fill-up bookings, and page tags go
Fill-up bookings and forms handled on your WordPress site
Check which tank-size, usage-cadence, auto-fill-date, skipped-fill, driver-notes, gate-code, or tank-location fields you enable, who can open form entries and bookings, where uploaded tank 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 tank size, cadence, and gate code off-site. One table can name the house, the tank, the skipped fills, and the gate code next to a name, even when the truck never comes. A later quiet winter 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 skipped fills next to tank size in one open submissions list, and to purge unused fill-up 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 a tank was filled.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the propane booking or account page. That page request can reach a vendor host before anyone submits. The page URL can say propane 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 tank sizes, skipped fills, or gate codes. An "auto-fill customer" badge is not a verified storage path.
Propane-delivery booking, account, 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 fuel-delivery or tank-monitoring 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 propane fill-up is a booking you create; a service name such as auto-fill, will-call, or tank exchange is a label you configure. Neither is a documented default. Tank-size, usage-cadence, auto-fill-date, skipped-fill, driver-notes, gate-code, or tank-location questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked fill-up is not proof a tank was filled, and a skipped slot is not proof of money trouble. Cancelling or missing the slot later does not erase the tank size, cadence, gate code, or driver notes 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. | Fill-up 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. Tank-size, usage-cadence, auto-fill-date, skipped-fill, driver-notes, gate-code, or tank-location questions are fields you add; they are not documented defaults. A tank photo or account document is a file you accept; that file type is not a documented default. A fill-up request is not proof a tank was filled. A skipped-fill answer is a stored preference, not proof of money trouble. A winter gap in later bookings is not proof the house is empty. 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 fill-up-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 tank-size, usage-cadence, skipped-fill, or gate-code field was sent. A page request from this script is not proof anyone ordered propane. The page URL can say propane 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 fill-up page can re-confirm fuel-delivery interest next to a stored address and tank size; 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. Tank-size, usage-cadence, auto-fill-date, skipped-fill, driver-notes, gate-code, or tank-location fields often depend on the fields you configure. A fill-up booking is not proof a tank was filled. A skipped fill is not proof of money trouble. A winter gap is not proof the house is empty. A gate code is a stored instruction, not proof anyone used it. A marketing-tag page request is not proof anyone ordered propane. The page URL can say propane even when no form is submitted. The tank size and the cadence can sit after the truck never comes. This page is about a fill-up schedule that can be read as occupancy from fuel use, not a well-drilling site survey, not a snow-removal seasonal route, not a marina slip ledger, and not an alarm-company away schedule. 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. An auto-fill 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 utility regulation, fuel-dealer licensing, occupancy-detection claims, or theft-risk claims. 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-propane-delivery-plugin-privacy