Food bank plugin privacy

Where does the assistance application that documents a family's hardest month go?

A food-bank eligibility or pickup-registration form can collect household size, children's names and ages, income band, SNAP/EBT status, and sometimes a photo of a benefits letter — typed into a local-first form or pickup-slot booking plugin. File fields can store benefits-letter scans in the site uploads folder. The row can quietly outlive the crisis in a plugin table on a volunteer-run site. A marketing tag on the same application page can send a page request to a vendor host before anyone submits. A page request is not proof that income or children's names were collected. This sample reviews three plugins' documentation. Check which fields you collect, who can open bookings and entries, where uploaded files land, which tags load on the application page, and how long records, files, and backups are kept.

Documentation review only. This is not legal advice, a SNAP or government-program review, a nonprofit compliance assessment, a benefits determination, 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 bookings, form entries, uploaded benefits letters, email inboxes, staff permissions, vendor accounts, or backups.

Where pickup bookings, application answers, and page tags go

Bookings and files handled on your WordPress site

Check which household, income, benefits, or children's-name fields you enable, who can open bookings and form entries, where uploaded benefits letters live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after the crisis. Notification emails can also copy the same answers off-site. Ask your web vendor not to collect full income histories on the first public form, and to purge applications that never became active clients.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the food-bank eligibility or pickup-registration 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 application pages if you do not want that page request. A browser scan cannot inspect stored form entries. A "secure client forms" badge is not a verified storage path.

Food-bank pickup, form-upload, 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 software without a WordPress.org listing is outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Easy Appointments

Documented self-hosted appointment plugin marketed for clinics and service bookings (plugin version 4.0.3). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. Household size, children's names or ages, income band, or SNAP/EBT status are custom fields you add (textarea, select, or input); they are not documented defaults. A pickup booking is not a benefits determination. 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 and does not guarantee crisis-length retention limits. Google Calendar, SMS, and payments are Pro. Google reCAPTCHA is optional. Public booking-form browser hosts are unverified.

Pickup-slot bookings and custom intake fields 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, children's names and ages, income band, or SNAP/EBT questions are fields you add; they are not documented defaults. Benefits-letter photos are files you accept; they are not documented defaults. An application entry is not a benefits determination. Entries can quietly outlive the crisis in plugin tables. Notification emails can copy field values 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 household size, income, or children's names were sent. A page request from this script on a food-bank eligibility or pickup-registration page is not proof that income or children's names were collected — and a pre-consent tag on that page can still treat food-insecure intent as an audience segment. Consent timing has not been tested. Review which tags you enable on application 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, children's names and ages, income band, SNAP/EBT status, or benefits-letter files often depend on the fields you configure. An application entry is not a benefits determination. A pickup booking is not proof of need. A marketing-tag page request is not proof that income or children's names were collected. Ask your web vendor who can open bookings and entries, where uploaded files live, whether a marketing tag loads on the application page, and how long records and backups are kept. A "secure" or "client forms" 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 SNAP rules, nonprofit duties, or benefits eligibility. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on application pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-food-bank-plugin-privacy