Volunteer meal delivery plugin privacy

Where does the route sheet go once you hand it to tonight's volunteer?

A volunteer meal-delivery WordPress stack is not only a database of recipients — it is a tool for printing route sheets. Names, addresses, gate codes, "knock loud, she is deaf", dietary flags, and "lives alone" answers are collected so staff can hand a photocopied sheet to whichever rotating volunteer showed up that week. Recipients rarely fill the form themselves; a caseworker or family member often does. A storage audit alone misses the point: ask who receives the route sheet and how that copy is revoked when a volunteer stops showing up. A marketing tag on the same page can send a page request to a vendor host before anyone submits — and that page request alone can treat meal-delivery enrollment intent as an audience segment from the URL. A page request is not proof anyone enrolled. An enrollment is not proof anyone is home alone. A delivery window is a schedule, not a welfare record. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where uploaded files land, who gets the printable export, which tags load on the enrollment page, and how long records, files, and backups are kept.

Documentation review only. This is not legal advice, an elder-abuse-law claim, a charity-regulation claim, a volunteer-screening-law claim, a welfare-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, printable route sheets, email inboxes, staff permissions, vendor accounts, or backups.

Where enrollment answers, route sheets, and page tags go

Entries, bookings, and printable exports on your WordPress site

Check which address, access-note, health-flag, dietary, or lives-alone fields you enable, who can open form entries and route bookings, where uploaded files live in the uploads folder, which inboxes receive copies, who can export or print tonight's route sheet, and how long records, files, and backups are kept after a volunteer stops showing up or a recipient leaves the program. Notification emails and photocopied sheets can also copy the same recipient identity and access notes off-site. Ask your web vendor not to put every access instruction next to a recipient name on one open roster when a short case ID would do — and ask how a printed copy is revoked.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the volunteer meal-delivery enrollment 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 enrollment pages if you do not want that page request. A browser scan cannot inspect stored form entries, bookings, or printed route sheets. A "confidential client list" badge is not a verified storage or distribution path.

Volunteer meal-delivery enrollment, route 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-delivery 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-route delivery window is a booking you create; a service name such as Tuesday route or evening delivery is a label you configure. Neither is a documented default. Address, access-note, dietary, or lives-alone questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A delivery-window booking is a schedule, not a welfare record. Cancelling later does not erase the access note already stored next to a recipient identity — and a CSV export of tonight's route is the sheet that leaves with a volunteer. 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.

Route-slot and delivery-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. Recipient-address, access-note, health-flag, dietary, lives-alone, emergency-contact, or volunteer-availability questions are fields you add; they are not documented defaults. A medical-note or gate-code photo is a file you accept; it is not a documented default. One enrollment entry can store every access instruction next to a recipient identity — and that same row is what staff print onto a route sheet for whichever volunteer shows up. Recipients rarely author their own row. A submitted form is not proof anyone is home alone. 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 an address, access note, or lives-alone flag was sent. A page request from this script on a volunteer meal-delivery enrollment page is not proof anyone enrolled — and a pre-consent tag on that page can still treat meal-delivery enrollment intent as an audience segment from the URL alone. The page URL can say volunteer meal delivery even when no form is submitted. Consent timing has not been tested. Review which tags you enable on enrollment 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. Addresses, access notes, health flags, dietary answers, or lives-alone flags often depend on the fields you configure. An enrollment is not proof anyone is home alone. A delivery window is a schedule, not a welfare record. A marketing-tag page request is not proof anyone enrolled. Leaving the program later does not erase the access note already stored next to a recipient name — and a photocopied route sheet may already be in a volunteer's car. Ask your web vendor who can open entries, who receives the printable export, where uploaded files live, whether a marketing tag loads on the enrollment page, and how long records and backups are kept. A "confidential client list" badge is not a verified storage or distribution path. Consent timing, access controls, and retention have not been tested. This page describes storage and distribution paths only and does not assess elder-abuse law, charity regulation, volunteer-screening law, or welfare outcomes. Review stored records, bookings, connected services, exports, printed route sheets, notification emails, marketing tags on enrollment 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-volunteer-meal-delivery-plugin-privacy