HOA plugin privacy

A violation complaint can name your neighbor

An HOA complaint form can store the neighbor you report, their address, a violation note, and a photo of their yard or car, plus your name as the complainant, in the same WordPress table. The neighbor never filled out the form. A board-member login can open both names. Dues or meeting RSVP forms can add unit numbers and emails. A marketing tag on the portal page can send a page request to a vendor host before anyone submits. The page URL can say violation report. A page request is not proof that a neighbor's address or photo was collected. A complaint entry is not a violation finding. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and files, which tags load on the portal page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, an HOA-rule claim, a fair-housing assessment, 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, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.

Where both names, photos, and page tags go

Complaints and files handled on your WordPress site

Check which reported-address, violation-description, neighbor-name, unit-number, or photo-upload fields you enable, who can open form entries, which inboxes receive copies, and how long records, emails, and backups are kept. Notification emails can also copy the same answers off-site. One entry can name the complainant and the accused neighbor even when only the complainant typed. Ask your web vendor not to collect the accused neighbor's name on a public form, not to accept yard or car photos on a public complaint page, and to purge complaints that never became board actions. A privacy-policy page does not by itself limit who can open a complaint list.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the HOA portal page. That page request can reach a vendor host before anyone submits. The page URL can say violation report even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off complaint pages if you do not want that page request. A browser scan cannot inspect stored complaints. A "secure member portal" badge is not a verified storage path.

HOA complaint, 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 HOA-portal software without a WordPress.org listing is outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Drag and Drop Multiple File Upload for Contact Form 7

Documented Contact Form 7 upload extension (plugin version 1.4.0). Version 1.4.0 drag-n-drop-upload-cf7.php defines wpcf7_dnd_dir as wp_dndcf7_uploads. The listing states the free version moves files to wp-content/uploads/wp_dndcf7_uploads, attaches them to mail, then removes them from that temporary folder about one hour after submission. That cleanup does not remove copies already sent as email attachments. Yard photos, car photos, or architectural-request plans are files you accept; they are not documented defaults. A photo of a neighbor's yard or car is not a violation finding. Pro documents saving to the Media Library, changing the upload directory, auto-delete timers, and remote storage to OneDrive, Google Drive, Amazon S3, Dropbox, or FTP. Public upload-page browser hosts are unverified.

Visitor files stored under wp-content/uploads/wp_dndcf7_uploadsBrowser 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. Reported-neighbor name, reported address, violation description, unit number, complainant name, or dues and meeting-RSVP answers are fields you add; they are not documented defaults. Yard, car, or architectural-request photos are files you accept; they are not documented defaults. One form entry can name the complainant and the accused neighbor even when only the complainant typed. The accused neighbor never filled out the form. A complaint entry is not a violation finding. A board-member login can open both names in the same submissions list. 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 a reported address, violation note, or yard photo was sent. A page request from this script is not proof that a neighbor's address or photo was collected. The page URL can say violation report even when no form is submitted. Consent timing has not been tested. Review which tags you enable on HOA portal 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. Reported addresses, violation notes, neighbor names, unit numbers, or yard photos often depend on the fields you configure. Two people can be named in one entry even when only the complainant typed. The accused neighbor never filled out the form. A complaint entry is not a violation finding. An uploaded photo is not a finished board action. A marketing-tag page request is not proof that a neighbor's address or photo was collected. The page URL can say violation report even when no form is submitted. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the portal page, and how long records and backups are kept. A "secure" or "member portal" 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 HOA rules, fair housing, or board duties. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on portal 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-hoa-plugin-privacy