Union organizing plugin privacy
The authorization-card form that lists who signed before the employer finds out
An organizing drive's one operational secret is the list of who signed. The employer is the reader those rows must never reach, and the rows sit in WordPress plugin tables on whatever hosting the local could afford. Name, employer, worksite, shift, personal phone because the work email is monitored, and a who-referred-you field that maps the committee can all sit in one table. Those answers can sit in a local-first form or upload plugin behind one admin login. A failed drive ends. The list stays. A marketing tag on the same page can send a page request to a vendor host before anyone submits. A page request is not proof that anyone organized. A submitted card is not a vote. The page URL can say union even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on the card page, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, an NLRA or labor-law claim, a union-election-procedure claim, a retaliation-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, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where authorization cards and page tags go
Cards and files handled on your WordPress site
Check which worker-name, employer, worksite, shift, personal-phone, who-referred-you, or card-photo-upload fields you enable, who can open form entries and the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a drive that never went public. A failed drive can still leave the list. Notification emails can also copy the same roster off-site. One table can list every worker who signed even when only the signer typed. Ask your web vendor not to collect a who-referred-you map on a public card form, not to accept signed-card photos on that page, and to purge cards from a drive that ended. A privacy-policy page does not by itself limit who can open an uploads folder.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the authorization-card page. That page request can reach a vendor host before anyone submits. The page URL can say union even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off card pages if you do not want that page request. A browser scan cannot inspect stored cards. A "secure organizing portal" badge is not a verified storage path.
Union-organizing card, 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 union-organizing or labor-campaign 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 |
|---|---|---|---|---|---|---|
| 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. A photo of a signed authorization card is a file you accept; it is not a documented default. The uploads folder can hold those card photos next to the signer list. A failed drive can still leave the files until the documented cleanup, and the email copy can remain. An uploaded card photo is not a vote. 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_uploads | 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. Worker-name, employer, worksite, shift, personal-phone, or who-referred-you questions are fields you add; they are not documented defaults. A photo of a signed card is a file you accept; it is not a documented default. One table can list every worker who signed. Completing the form can record an authorization card. A submitted card is not a vote. A failed drive can remain as rows. A staff login can open the roster next to the attached card photos. 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. | Form 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 a worker name, worksite, or signed-card photo was sent. A page request from this script is not proof anyone organized. The page URL can say union even when no form is submitted. Consent timing has not been tested. Review which tags you enable on authorization-card pages. | 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. Worker-name, employer, worksite, shift, personal-phone, who-referred-you, or card-photo-upload fields often depend on the fields you configure. The employer never consented to receive this list and is the reader the rows must never reach. A submitted card is not a vote. A failed drive can still leave the list. A marketing-tag page request is not proof anyone organized. The page URL can say union even when no form is submitted. This page is about a roster of who signed before a campaign goes public, not a public petition, a single anonymous tip, or an employment complaint. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the card page, and how long records and backups are kept. A "secure" or "organizing 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 NLRA, labor-law, union-election procedure, or retaliation outcomes. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on card pages, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress petition plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-union-organizing-plugin-privacy