Meal train plugin privacy

The signup page that tells forty neighbors what stage it is

A meal-train WordPress stack is not only a database of cooks — it is a page built to circulate. The organizer publishes a neighbor's diagnosis stage, address, allergies, dietary needs, and family schedule so friends can pick a night. The signup grid then shows every cook name and delivery slot to everyone who holds the URL. No breach required: forwarding the share link is the feature. The organizer is well-meaning; the mechanism is the story. A marketing tag on the same shared page can send a page request to a vendor host before anyone submits — and that page request alone can treat meal-train signup intent as an audience segment from the URL. A page request is not proof anyone signed up to cook. A signup is not proof of a medical condition. A delivery slot is a schedule, not a care record. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where uploaded files land, who can see the public signup grid, which tags load on the shared page, and how long records, files, and backups are kept.

Documentation review only. This is not legal advice, a medical claim, a HIPAA claim, a GDPR or other compliance assessment, or a judgment about organizers.

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, share-link recipients, email inboxes, staff permissions, vendor accounts, or backups.

Where signup answers, share links, and page tags go

Entries, bookings, and the public signup grid on your WordPress site

Check which diagnosis-stage, address, allergy, dietary, or family-schedule fields you enable, who can open form entries and delivery-slot bookings, where uploaded files live in the uploads folder, which inboxes receive copies, who can see every cook name next to every slot on the shared page, and how long records, files, and backups are kept after the meal schedule ends. Notification emails and forwarded share links can also copy the same household identity and care notes off-site. Ask your web vendor not to put every diagnosis-stage detail next to a recipient name on one open grid when a short case ID would do — and ask who receives the URL.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the meal-train signup page. That page request can reach a vendor host before anyone submits. Review which tags you enable, account access, and retention there. Keep marketing tags off shared signup pages if you do not want that page request. A browser scan cannot inspect stored form entries, bookings, or who received the share link. A "private family circle" badge is not a verified storage or visibility path.

Meal-train signup, delivery-slot booking, 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 meal-coordination 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 meal-delivery window is a booking you create; a service name such as Tuesday dinner or Thursday lunch is a label you configure. Neither is a documented default. Address, allergy, dietary, or family-schedule questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A delivery-slot booking is a schedule, not a care record. Cancelling later does not erase the allergy note already stored next to a household identity — and a public booking calendar that lists every cook name next to every slot is the grid everyone with the share link can read. Emails can include those custom fields. 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.

Delivery-slot and meal-window 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. Diagnosis-stage, address, allergy, dietary, family-schedule, cook-name, or delivery-slot questions are fields you add; they are not documented defaults. A care-note or parking-instruction photo is a file you accept; it is not a documented default. One organizer-authored entry can store every household detail next to a recipient identity — and when that same page is the public signup grid, every neighbor who holds the URL can see who signed which night. The data subject rarely authors their own row. A submitted form is not proof of a medical condition. 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.

Form entries stored in WordPress; file 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 a diagnosis-stage note, address, or allergy list was sent. A page request from this script on a meal-train signup page is not proof anyone signed up to cook — and a pre-consent tag on that shared page can still treat meal-train signup intent as an audience segment from the URL alone. The page URL can say meal train even when no form is submitted. Consent timing has not been tested. Review which tags you enable on shared signup 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. Diagnosis-stage notes, addresses, allergies, dietary answers, or family schedules often depend on the fields you configure. A signup is not proof of a medical condition. A delivery slot is a schedule, not a care record. A marketing-tag page request is not proof anyone signed up to cook. Ending the meal schedule later does not erase the allergy note already stored next to a household name — and a forwarded share link may already be in forty inboxes. Ask your web vendor who can open entries, who receives the share URL, where uploaded files live, whether a marketing tag loads on the shared page, and how long records and backups are kept. A "private family circle" badge is not a verified storage or visibility path. Consent timing, access controls, and retention have not been tested. This page describes storage and share-link visibility paths only and does not assess medical privacy law or organizer intent. Review stored records, bookings, connected services, exports, notification emails, marketing tags on shared signup 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-meal-train-plugin-privacy