Dumpster rental plugin privacy

The driveway rental that dates your worst month

The order form stores the address, drop-off and pickup dates, container size, and the contents declaration the prohibited-items checklist forces you to make. The lateral truth: nobody rents a 30-yard dumpster for an ordinary week — the rental row is a label on a crisis: an eviction, an estate cleanout, a hoard, a flood, a divorce purge. The neighbors can see the dumpster; only the database says who rented it, for what, and exactly how long the crisis lasted. Leak it and the anonymous container in the driveway gets a name and a reason. Those fields are configured, not documented defaults. A dumpster-rental booking is a calendar row, not proof a crisis happened or that a container sat in a driveway. A dates, size, or contents answer is a form answer or uploaded file, not a verified crisis label. A page request is not proof anyone rented a dumpster. The page URL can say dumpster rental even when no form is submitted. Ask what happens to the name, the service address, the drop-off and pickup dates, the container size, and the contents declaration after a rental ends — the stack that dated the crisis the whole street could see outlives the haul. 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, an eviction-law claim, an estate-administration claim, a hoarding-diagnosis claim, a flood-insurance claim, a divorce-proceedings claim, a trespass 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 dumpster-rental bookings, driveway intakes, and page tags go

Bookings and rental orders on your WordPress site

Check which drop-off-date, pickup-date, container-size, contents-declaration, prohibited-item, name, or service-address fields you enable, who can open form entries and dumpster-rental bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a rental ends — when the name-plus-address-plus-rental row still holds a dated crisis label next to a driveway everyone could see. Notification emails can also copy those fields off-site. One table can list every "Jordan · 12 Maple Ave · 30-yard · drop-off Mar 3 · pickup Mar 17 · contents: estate cleanout · prohibited checklist signed" stack next to a customer name. Ask your web vendor not to keep drop-off dates, pickup dates, container sizes, and contents declarations next to service addresses and names in one open submissions list longer than operations need, and to purge those fields when a rental ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored dumpster-rental booking is not proof a crisis happened or that a container sat in a driveway. A dates, size, or contents answer is not a verified crisis label.

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 dumpster rental 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 "dumpster rental privacy" badge is not a verified storage path.

Dumpster-rental booking, driveway-intake, 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 dumpster-rental SaaS tools without a WordPress.org listing are 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A March drop-off window or a two-week pickup slot is a booking you create; a service name such as 30-yard roll-off or driveway delivery is a label you configure. Neither is a documented default. Drop-off-date, pickup-date, container-size, contents-declaration, prohibited-item, 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 a crisis happened or that a container sat in a driveway — and a CSV export of "Jordan · 12 Maple Ave · 30-yard · drop-off Mar 3 · pickup Mar 17 · contents: estate cleanout · prohibited checklist signed" next to a customer name is still a calendar that pairs a dated crisis label with a service 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.

Dumpster-rental bookings stored 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. Drop-off-date, pickup-date, container-size, contents-declaration, prohibited-item, or service-address fields are fields you add; they are not documented defaults. Completing the form can store a name-plus-address-plus-rental stack ("Jordan · 12 Maple Ave · 30-yard · drop-off Mar 3 · pickup Mar 17 · contents: estate cleanout · prohibited checklist signed") — typed or uploaded once so a shop can quote a rental, into the same tables as a "dumpster rental" label. A dates, size, or contents answer is a form answer or uploaded file, not a verified crisis label. A dumpster-rental booking is a calendar row, not proof a crisis happened or that a container sat in a driveway — and a staff login can open "Jordan, 12 Maple Ave, 30-yard, drop-off Mar 3, pickup Mar 17, estate cleanout, prohibited checklist signed" 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 rental answers stored in WordPress; optional contents photos 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 drop-off-date, pickup-date, container-size, contents-declaration, or prohibited-item field was sent. A page request from this script is not proof anyone rented a dumpster. The page URL can say dumpster rental 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 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. Drop-off-date, pickup-date, container-size, contents-declaration, prohibited-item, or service-address fields often depend on the fields you configure. A dumpster-rental booking is a calendar row, not proof a crisis happened or that a container sat in a driveway. A dates, size, or contents answer is a form answer or uploaded file, not a verified crisis label. A marketing-tag page request is not proof anyone rented a dumpster. The page URL can say dumpster rental even when no form is submitted. The name-plus-address-plus-rental row that dated the crisis the whole street could see for a shop — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that driveway-rental stack, not a junk-removal shame-photo set, an estate-sale house inventory, a hoarding-cleanup how-you-live gallery, or a restoration everything-you-lost photo set. 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 "dumpster rental privacy" or "roll-off 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 eviction law, estate administration, hoarding diagnosis, flood insurance, divorce proceedings, or trespass. 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

Scan your site for third-party requests

/wp-dumpster-rental-plugin-privacy