Party rental plugin privacy
The delivery form that maps one afternoon of children in your backyard
A bounce-house booking is a map of one specific afternoon at your home: the delivery address, the gate the driver should use, the hour the yard fills with children, and the birthday child's name and age for the banner. The form has to collect all of it or the truck can't come — and then it keeps all of it long after the party, in a plugin table that says, in effect, "this house hosts unsupervised backyard crowds of seven-year-olds every June." No other rental form describes your family's calendar this precisely. Those fields are configured, not documented defaults. A party booking is a calendar row, not proof anyone inflated a bounce house. A birthday-name answer is what a parent typed, not a guest list. A gate note is a logistics instruction, not a premises-access credential. A page request is not proof anyone booked a party. The page URL can say party rental even when no form is submitted. Ask what happens to the delivery address, the gate note, the party hour, and the birthday-child row after the party ends — the delivery form that maps one afternoon of children in your backyard outlives the bounce house. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a premises-access-law claim, a child-safety or COPPA claim, a party-liability-insurance claim, an unsupervised-minors-law claim, a product-safety 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 delivery intakes, party bookings, and page tags go
Intakes and bookings on your WordPress site
Check which delivery-address, gate-access, party-hour, birthday-name, or age fields you enable, who can open form entries and party bookings, which inboxes receive copies, and how long records, emails, and backups are kept after the party ends — when the delivery form that maps one afternoon of children in your backyard still holds that row. Notification emails can also copy those fields off-site. One table can list a legal name next to a home address, a side-gate latch note, a Saturday 2pm party hour, and a birthday child's name and age. Ask your web vendor not to keep backyard delivery maps next to birthday-child rows in one open submissions list longer than operations need, and to purge those fields when a party weekend closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored party booking is not proof anyone inflated a bounce house. A birthday-name answer is not a guest list.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the party-rental booking page. That page request can reach a vendor host before anyone submits. The page URL can say party rental even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "party rental privacy" badge is not a verified storage path.
Delivery-intake, party-booking, and marketing-tag setups
Three plugins reviewed from public documentation. Specialty bounce-house / party-rental SaaS tools without a WordPress.org listing are outside this sample.
No paid placement. Site-hosted tools appear first, followed by vendor-hosted tools. Names are alphabetical within each group.
| 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 Saturday bounce-house block or a backyard delivery window is a booking you create; a service name such as party rental or bounce house is a label you configure. Neither is a documented default. Delivery-address, gate-access, party-hour, birthday-name, or age 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 inflated a bounce house — and a CSV export of "Alex Rivera, address: 14 Maple Ct, gate: side yard latch, hour: Sat 2pm, birthday: Mia age 7" next to a contact name is still a calendar that holds a family's afternoon map next to a delivery logistics note. 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. | Party and delivery 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. Delivery-address, gate-access, party-hour, birthday-name, or age fields are fields you add; they are not documented defaults. Completing the form can store a home delivery address next to a side-gate latch note, a Saturday 2pm party hour, a birthday child's name and age for the banner, a contact name, and optional waiver PDF uploads — typed once so the truck does not have to re-key the delivery, into the same tables as a party-rental label that maps one afternoon of children in a backyard. A birthday-name answer is what a parent typed, not a guest list. A party booking is a calendar row, not proof anyone inflated a bounce house — and a staff login can open "Alex Rivera, address: 14 Maple Ct, gate: side yard latch, hour: Sat 2pm, birthday: Mia age 7" 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. | Delivery and birthday answers stored in WordPress; optional waiver 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 delivery-address, gate, party-hour, birthday-name, or age field was sent. A page request from this script is not proof anyone booked a party. The page URL can say party rental even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking 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. Delivery-address, gate-access, party-hour, birthday-name, or age fields often depend on the fields you configure. A party booking is a calendar row, not proof anyone inflated a bounce house. A birthday-name answer is what a parent typed, not a guest list. A gate note is a logistics instruction, not a premises-access credential. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone booked a party. The page URL can say party rental even when no form is submitted. The delivery form that maps one afternoon of children in your backyard — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that backyard delivery and birthday-banner stack, not a pool-service standing route, a laser-tag on-premises kids roster, a catering guest-dietary form, or a moving-company home-access inventory. Ask your web vendor who can open entries, whether a marketing tag loads on the booking page, and how long records and backups are kept. A "party rental privacy" or "kids party safe" 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 premises-access law, child-safety or COPPA, party-liability insurance, unsupervised-minors law, or product safety. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking 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-party-rental-plugin-privacy