Affordable housing waitlist plugin privacy
The application that waits longer than your circumstances stay true
A waitlist application can hold income, household composition, disability status, and sometimes a domestic-violence flag. It is filed once, then sits for years while the list moves. Annual recertification can re-confirm those answers on a page that also loads a marketing tag. The stored row is a problem because nobody knows whether it still matches the household. A waitlist application is not a tenancy. A page request is not proof of anyone's income. The page URL can say affordable housing even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries, which tags load on waitlist and recertification pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a HUD-policy claim, an eligibility-rule claim, a housing-outcome claim, or a GDPR or other compliance assessment.
Scan your site for third-party requestsThe 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 waitlist applications, recertification answers, and page tags go
Applications and entries handled on your WordPress site
Check which income, household-composition, disability-status, or domestic-violence-flag fields you enable, who can open form entries and bookings, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a wait that never became a tenancy. Notification emails can also copy the same answers off-site. One table can list every household still waiting even when only the applicant typed. Ask your web vendor not to collect a domestic-violence flag on the first public form, not to store recertification answers next to the original application in one open submissions list, and to purge applications that never became a tenancy. A privacy-policy page does not by itself limit who can open an uploads folder. A stored application is not proof a unit was offered.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the waitlist application or recertification page. That page request can reach a vendor host before anyone submits. The page URL can say affordable housing even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off waitlist and recertification pages if you do not want that page request. A browser scan cannot inspect stored applications. An "affordable housing" badge is not a verified storage path.
Affordable housing waitlist application, recertification, 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 housing-authority or waitlist software without a WordPress.org listing is outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Easy Appointments Documented self-hosted appointment plugin marketed for service businesses (plugin version 4.0.3). The listing documents automatic email notifications: customers get instant booking confirmations; staff get notified; templates can include booking information and custom fields; customers can confirm or cancel via a link in the email. WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A waitlist application or recertification slot is a booking you create; a service name such as waitlist intake or annual recert is a label you configure. Neither is a documented default. Income, household-composition, disability-status, or domestic-violence-flag questions are custom fields you add (textarea, select, or input); they are not documented defaults. A submitted waitlist booking is not a tenancy. Cancelling or missing a recertification later does not erase the contact answers already stored next to a name, and does not unsend a confirmation email already delivered. How long that row sits after the household changes is not a documented default of the plugin. 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. | Waitlist and recertification bookings, custom intake fields, and automatic confirmation emails on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| 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. Income, household-composition, disability-status, or domestic-violence-flag questions are fields you add; they are not documented defaults. Pay stubs, ID scans, or recertification PDFs are files you accept; they are not documented defaults. A submitted waitlist entry is not a tenancy. 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. How long a waitlist submission sits after the household changes is not a documented default of the plugin. | Waitlist application entries stored in WordPress; file uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| 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 income, household-composition, disability-status, or domestic-violence-flag field was sent. A page request from this script is not proof of anyone's income. The page URL can say affordable housing even when no form is submitted. Consent timing has not been tested. Review which tags you enable on waitlist application and recertification pages. Keep marketing tags off those pages if you do not want that page request. Recertification on a tagged page can re-confirm a household that has already waited years; this row does not claim a housing outcome from that request. | Marketing tags handled through Meta, Google, or other configured platforms | connect.facebook.net | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Income, household-composition, disability-status, or domestic-violence-flag fields often depend on the fields you configure. A waitlist application is not a tenancy. A marketing-tag page request is not proof of anyone's income. The page URL can say affordable housing even when no form is submitted. The stored row can sit for years after the household changed. This page is about a waitlist application that outlasts the facts it recorded, not an eviction-defense crisis file, a domestic-violence shelter intake, or a property-management tenant ledger. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the waitlist or recertification page, and how long records and backups are kept. A "secure" or "affordable housing" 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 HUD policy, eligibility rules, or housing outcomes. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on waitlist and recertification pages, and backups.
Documentation snapshot: Oct 14, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-affordable-housing-waitlist-plugin-privacy