Food truck plugin privacy
The booking that puts your private party on a public calendar
Booking a food truck for a private event publishes the one thing a private event is supposed to keep private: that it exists. The quote form stores your home or venue address, the date, the headcount, and the occasion — and many trucks mirror confirmed bookings straight onto a public calendar so other customers know where the truck will be. Guest allergy notes ride along in the same row, so a dietary-medical detail about your guests sits in a WordPress option because someone wanted tacos at a retirement party. No other catering-adjacent form turns a private party into a public truck stop this precisely. Those fields are configured, not documented defaults. A food-truck booking is a calendar row, not proof anyone served tacos. An allergy answer is what a host typed, not a medical record. A public calendar listing is a truck schedule, not proof a private party was advertised. A page request is not proof anyone booked a truck. The page URL can say food truck even when no form is submitted. Ask what happens to the venue address, the event date, the headcount, the occasion, and the allergy row after the party ends — the booking that puts your private party on a public calendar outlives the tacos. 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 food-safety-law claim, an allergy or medical-disclosure-law claim, an event-liability-insurance claim, a public-calendar-advertising 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 private-event quotes, food-truck bookings, and page tags go
Quotes and bookings on your WordPress site
Check which venue-address, event-date, headcount, occasion, or guest-allergy fields you enable, who can open form entries and food-truck bookings, which inboxes receive copies, and how long records, emails, and backups are kept after the event ends — when the booking that puts your private party on a public calendar 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 Saturday 6pm date, a headcount of forty, a retirement occasion, and a guest allergy note. Ask your web vendor not to keep private-party maps next to allergy rows in one open submissions list longer than operations need, and to purge those fields when an event weekend closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored food-truck booking is not proof anyone served tacos. An allergy answer is not a medical record.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the food-truck booking page. That page request can reach a vendor host before anyone submits. The page URL can say food truck 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 "food truck privacy" badge is not a verified storage path.
Private-event quote, food-truck booking, and marketing-tag setups
Three plugins reviewed from public documentation. Specialty food-truck 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 food-truck block or a private-event service window is a booking you create; a service name such as food truck or private catering is a label you configure. Neither is a documented default. Venue-address, event-date, headcount, occasion, or guest-allergy 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 served tacos — and a CSV export of "Jordan Lee, venue: 14 Maple Ct, date: Sat 6pm, headcount: 40, occasion: retirement, allergies: tree-nut" next to a contact name is still a calendar that holds a private party's map next to a dietary-medical note that many trucks also mirror onto a public schedule. 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. | Private-event and food-truck 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. Venue-address, event-date, headcount, occasion, or guest-allergy fields are fields you add; they are not documented defaults. Completing the form can store a home or venue address next to a Saturday 6pm date, a headcount of forty, a retirement-party occasion, a contact name, guest allergy notes, and optional waiver or menu PDF uploads — typed once so the truck does not have to re-key the stop, into the same tables as a food-truck label that can place a private event on a public calendar. An allergy answer is what a host typed, not a medical record. A food-truck booking is a calendar row, not proof anyone served tacos — and a staff login can open "Jordan Lee, venue: 14 Maple Ct, date: Sat 6pm, headcount: 40, occasion: retirement, allergies: tree-nut" 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. | Venue and allergy answers stored in WordPress; optional intake 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 venue-address, date, headcount, occasion, or allergy field was sent. A page request from this script is not proof anyone booked a truck. The page URL can say food truck 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. Venue-address, event-date, headcount, occasion, or guest-allergy fields often depend on the fields you configure. A food-truck booking is a calendar row, not proof anyone served tacos. An allergy answer is what a host typed, not a medical record. A public calendar listing is a truck schedule, not proof a private party was advertised. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone booked a truck. The page URL can say food truck even when no form is submitted. The booking that puts your private party on a public calendar — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that private-event quote and public-calendar stack, not a catering staffed-service dietary form, a wedding-planner guest list, a limo-service passenger roster, or a meal-train household schedule. 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 "food truck privacy" or "private event 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 food-safety law, allergy or medical disclosure law, event-liability insurance, or public-calendar advertising rules. 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-food-truck-plugin-privacy