Catering plugin privacy

The quote form that collects medical and religious facts about people who were only invited to dinner

A catering quote page can look like a tasting booking and a contact form. The same form often asks occasion, event date and address, headcount, dietary needs, and budget — plus venue-layout and inspiration-photo uploads — and stores those answers next to a name for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can record that a host typed "nut allergy — bride's father," "kosher — groom's table," or "no alcohol — uncle, in recovery" into a vendor table so a kitchen can plan trays. Guests named in the dietary grid never touched the form; an occasion dropdown such as celebration of life, gender reveal, or retirement can date a life event before half the guest list knows; the event block itself — date, address, headcount — is a written schedule of where a crowd will be. A quote request is an inquiry, not a booked event. A dietary-grid entry is the host's note about a guest, not the guest's disclosure. An occasion label is the host's framing, not a verified life event. A headcount is an estimate. An uploaded venue layout is a client document in a site uploads folder. A page request is not proof anyone is hosting anything. The page URL can say catering even when no form is submitted. Ask what happens to the dietary grid and the venue-layout upload after the tasting — the quote form collects medical and religious facts about people who were only invited to dinner, and the row outlives the menu board. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the quote page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a food-safety or allergen-law claim, a liquor-licensing claim, a caterer-quality claim, an event-outcome 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 tasting bookings, quote intakes, and page tags go

Intakes and bookings on your WordPress site

Check which occasion, event-date-and-address, headcount, dietary-grid, or budget-range fields you enable, who can open form entries and tasting bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a quote closes — when the quote form collects medical and religious facts about people who were only invited to dinner. Notification emails can also copy those fields off-site. One table can list every guest allergy note a host typed next to an occasion label and an event address. Ask your web vendor not to keep venue layouts next to dietary grids in one open submissions list longer than operations need, and to purge quote rows when the event is declined or closed. A privacy-policy page does not by itself limit who can open a submissions list. A stored tasting is not a booked event. An uploaded inspiration photo is not a verified floor plan.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the catering quote page. That page request can reach a vendor host before anyone submits. The page URL can say catering even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off quote and tasting pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "private event planning" badge is not a verified storage path.

Tasting, catering quote 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 catering CRM SaaS platforms 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 tasting or walkthrough booking is a booking you create; a service name such as tasting, menu walkthrough, or venue site visit is a label you configure. Neither is a documented default. Occasion, event-date-and-address, headcount, dietary-grid, or budget-range questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not a booked event — and a CSV export of tastings next to a dietary grid and an occasion label is still a quote row after someone asked about trays. 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.

Catering tasting and walkthrough 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. Occasion, event-date-and-address, headcount, dietary-grid, or budget-range questions are fields you add; they are not documented defaults. Completing the form can store a guest dietary grid next to an occasion label, an event address, a headcount, a budget range, and optional venue-layout or inspiration-photo uploads — typed once by a host into the same tables as a newsletter signup. A quote request is an inquiry, not a booked event. A dietary-grid entry is the host's note about a guest, not the guest's disclosure — the people it names never touched the form. An occasion label is the host's framing, not a verified life event. A headcount is an estimate. An uploaded venue layout is a client document in uploads/forminator, not a verified floor plan. A staff login can open the dietary grid next to the celebration-of-life date. 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.

Catering quote intake entries stored in WordPress; optional venue-layout and inspiration-photo uploads 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 an occasion, event-date-and-address, headcount, dietary-grid, or budget-range field was sent. A page request from this script is not proof anyone is hosting anything. The page URL can say catering even when no form is submitted. Consent timing has not been tested. Review which tags you enable on quote and tasting 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. Occasion, event-date-and-address, headcount, dietary-grid, or budget-range fields often depend on the fields you configure. A quote request is an inquiry, not a booked event. A dietary-grid entry is the host's note about a guest, not the guest's disclosure. An occasion label is the host's framing, not a verified life event. A headcount is an estimate. An uploaded venue layout is a client document in a site uploads folder. A marketing-tag page request is not proof anyone is hosting anything. The page URL can say catering even when no form is submitted. The quote form collects medical and religious facts about people who were only invited to dinner — that is a storage path next to guest names, not a feature these plugins claim. This page is about that catering quote intake, not a wedding-planner guest list, an allergy-clinic intake, or a meal-train signup. Ask your web vendor who can open entries, whether a marketing tag loads on the quote page, and how long records and backups are kept. A "private event planning" 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 or allergen law, liquor licensing, caterer quality, or event outcomes. Review stored records, bookings, connected services, exports, notification emails, marketing tags on quote pages, and backups.

Documentation snapshot: Oct 14, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-catering-plugin-privacy