Political campaign plugin privacy

The yard-sign request that files your politics under your home address

A campaign site can look like a calendar and a short yard-sign form. The same form often asks for a street address, a precinct, volunteer interests, whether the campaign can count on your vote, and how you heard about them — and asks for an endorsement photo or a signed form scan — and stores those answers next to the supporter's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a canvass-shift booking next to a home address, a pledge answer, and a marketing pixel — the yard-sign request that files your politics under your home address, typed once into a vendor table next to a newsletter signup. A yard-sign request is lawn logistics, not a voter-file entry. A pledge answer is a stated intention, not a vote. A volunteer-interest checkbox is enthusiasm typed into a form, not affiliation on any register. A shift booking is a calendar row, not proof anyone showed up. An uploaded photo is a stored file in a site uploads folder, not an endorsement on record. A page request is not proof of how anyone votes. The page URL can say political-campaign even when no form is submitted. Ask what happens to the pledge answer and the home address after Election Day — the quietest field is "can we count on your vote?", and the row can outlive the committee that collected it. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the yard-sign page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, an FEC or campaign-finance claim, an election-law claim, a voter-file or NGP VAN / PDI claim, a claim about any party or candidate, 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 canvass bookings, yard-sign notes, and page tags go

Bookings and notes on your WordPress site

Check which yard-sign-address, precinct, volunteer-interests, can-we-count-on-your-vote, or how-did-you-hear fields you enable, who can open form entries and canvass or phone-bank bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the yard-sign request files your politics under your home address. Notification emails can also copy those fields off-site. One table can list every Saturday canvass next to a home address and a pledge answer. Ask your web vendor not to keep endorsement-photo uploads next to "yes, count on my vote" rows in one open submissions list longer than operations need, and to purge intake rows when the campaign ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not proof anyone showed up. A pledge answer is not a vote.

Page tags handled by a vendor

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

Canvass / phone-bank booking, yard-sign 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 campaign CRM and voter-file 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 Saturday canvass shift or a Tuesday phone-bank slot is a booking you create; a service name such as Precinct 12 canvass or phone bank is a label you configure. Neither is a documented default. Yard-sign-address, precinct, volunteer-interests, or can-we-count-on-your-vote questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof anyone showed up — and a CSV export of a canvass row next to a home address and a pledge answer is still a calendar that profiles stated politics beside a street. 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.

Canvass-shift and phone-bank 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. Yard-sign-request-address, precinct, volunteer-interests, can-we-count-on-your-vote, or how-did-you-hear questions are fields you add; they are not documented defaults. Completing the form can store a home address next to a precinct field, volunteer-interest checkboxes, a can-we-count-on-your-vote answer, a how-did-you-hear note, and optional endorsement-photo or signed-form uploads — typed once as the yard-sign request that files your politics under your home address, into the same tables as a newsletter signup. A yard-sign request is lawn logistics, not a voter-file entry. A pledge answer is a stated intention, not a vote. A volunteer-interest checkbox is enthusiasm typed into a form, not affiliation on any register. An uploaded photo is a stored file in a site uploads folder, not an endorsement on record — and a staff login can open "123 Oak St, Precinct 4, yard sign + phone bank, yes you can count on my vote, selfie with sign JPEG" next to everyone else's resume. 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.

Yard-sign and volunteer intake entries stored in WordPress; optional endorsement-photo and signed-form 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 yard-sign-address, precinct, volunteer-interests, or can-we-count-on-your-vote field was sent. A page request from this script is not proof of how anyone votes. The page URL can say political-campaign even when no form is submitted. Consent timing has not been tested. Review which tags you enable on yard-sign, volunteer, and booking 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. Yard-sign-address, precinct, volunteer-interests, can-we-count-on-your-vote, or how-did-you-hear fields often depend on the fields you configure. A yard-sign request is lawn logistics, not a voter-file entry. A pledge answer is a stated intention, not a vote. A volunteer-interest checkbox is enthusiasm typed into a form, not affiliation on any register. A shift booking is a calendar row, not proof anyone showed up. An uploaded photo is a stored file in a site uploads folder, not an endorsement on record. A marketing-tag page request is not proof of how anyone votes. The page URL can say political-campaign even when no form is submitted. The yard-sign request that files your politics under your home address — that is a storage path next to a pledge answer, not a feature these plugins claim. This page is about that campaign intake, not a published petition signature list or a union authorization-card roster. Ask your web vendor who can open entries, whether a marketing tag loads on the yard-sign page, and how long records and backups are kept after the committee dissolves. A "get out the vote" 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 FEC or campaign-finance compliance, election law, voter-file / NGP VAN / PDI vendor practices, or any party or candidate. Review stored records, bookings, connected services, exports, notification emails, marketing tags on yard-sign 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-political-campaign-plugin-privacy