Food pantry plugin privacy

The eligibility form that makes the household prove it is poor

A food-pantry eligibility page can look like a booking and a contact form. The same form often asks household size, member names and ages, income, benefits status, and dietary needs — plus ID and award-letter 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 whole household proved it was poor enough to get groceries, typed once into a vendor table next to a marketing pixel. People at the pantry door do not read privacy policies; the kids named in the household list never touched the form; the row outlives the emergency that produced it. A pickup booking is not proof of hardship. An income answer is the applicant's statement, not a verified figure. A benefits-status checkbox is the applicant's claim, not an agency record. An uploaded award letter is a client document in a site uploads folder, not a government file. Household members named in the form are third parties who never consented. A page request is not proof anyone needed food. The page URL can say food pantry even when no form is submitted. Ask what happens to the household roster and the award-letter upload after the visit — the eligibility form makes the household prove it is poor, and the row outlives the bag of groceries. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the eligibility page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, an eligibility-law claim, a benefits-qualification claim, a nutrition claim, an immigration-status claim, a charity-effectiveness 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 pickup bookings, means-test intakes, and page tags go

Intakes and bookings on your WordPress site

Check which household-size, member-names-ages, income, benefits-status, or dietary-needs fields you enable, who can open form entries and pickup bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the eligibility form makes the household prove it is poor. Notification emails can also copy those fields off-site. One table can list every household whose income answer was typed next to kids' ages. Ask your web vendor not to keep award letters next to household rosters in one open submissions list longer than operations need, and to purge intake rows when the emergency closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored appointment is not proof of hardship. An uploaded ID is not an agency record.

Page tags handled by a vendor

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

Pickup, means-test eligibility 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 case-management 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 pickup or appointment booking is a booking you create; a service name such as grocery pickup, pantry visit, or eligibility interview is a label you configure. Neither is a documented default. Household-size, member-names-ages, income, benefits-status, or dietary-needs questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof of hardship — and a CSV export of visits next to a household roster and an income answer is still a means-test row after someone asked for groceries. 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.

Food-pantry pickup 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. Household-size, member-names-ages, income, benefits-status, or dietary-needs questions are fields you add; they are not documented defaults. Completing the form can store a household roster next to an income answer, a benefits-status claim, dietary needs, and optional ID or award-letter uploads — typed once to get groceries into the same tables as a newsletter signup. A pickup booking is not proof of hardship. An income answer is the applicant's statement, not a verified figure. A benefits-status checkbox is the applicant's claim, not an agency record. An uploaded award letter is a client document in uploads/forminator, not a government file. Household members named in the form are third parties who never consented — and a staff login can open the uploaded ID next to the kids' ages. 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.

Means-test eligibility intake entries stored in WordPress; optional ID and award-letter 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 household-size, member-names-ages, income, benefits-status, or dietary-needs field was sent. A page request from this script is not proof anyone needed food. The page URL can say food pantry even when no form is submitted. Consent timing has not been tested. Review which tags you enable on eligibility and pickup 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. Household-size, member-names-ages, income, benefits-status, or dietary-needs fields often depend on the fields you configure. A pickup booking is not proof of hardship. An income answer is the applicant's statement, not a verified figure. A benefits-status checkbox is the applicant's claim, not an agency record. An uploaded award letter is a client document in a site uploads folder, not a government file. Household members named in the form are third parties who never consented. A marketing-tag page request is not proof anyone needed food. The page URL can say food pantry even when no form is submitted. The eligibility form makes the household prove it is poor — that is a storage path next to kids' ages, not a feature these plugins claim. This page is about that means-test intake, not a day-labor-hall need-based sign-in, a home-care household roster, or a veterans-benefits award-letter upload. Ask your web vendor who can open entries, whether a marketing tag loads on the eligibility page, and how long records and backups are kept. A "confidential assistance" 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 eligibility law, benefits qualification, nutrition, immigration status, or charity effectiveness. Review stored records, bookings, connected services, exports, notification emails, marketing tags on eligibility 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-food-pantry-plugin-privacy