Wedding planner plugin privacy

A guest list can hand 200 strangers' addresses to one form

An inquiry or planning-portal form can collect guest names, home addresses, phone numbers, dietary notes, and plus-one relationships for people who never visited the site. File fields can store seating charts or guest-list spreadsheets in the site uploads folder. A marketing tag on the same inquiry page can send a page request to a vendor host before anyone submits. The people named on the list are not the person filling the form. A page request is not proof that guest addresses were collected. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries, where uploaded files land, which tags load on the inquiry page, and how long records, files, and backups are kept.

Documentation review only. This is not legal advice, a vendor-contract review, a venue-liability review, 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 guest-list entries, uploaded seating charts, email inboxes, staff permissions, vendor accounts, or backups.

Where guest lists, uploads, and page tags go

Guest lists and files handled on your WordPress site

Check which guest-name, address, dietary, or plus-one fields you enable, who can open form entries, where uploaded seating charts live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept. Notification emails can also copy the same answers off-site. Ask your web vendor not to collect guest details on the first public form, to keep guest lists in a locked portal instead of a public form, not to leave seating charts at a public uploads URL, and to purge files after the event. A privacy-policy page does not by itself limit who can open guest entries.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the inquiry 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 inquiry and planning-portal pages if you do not want that page request. A browser scan cannot inspect stored guest lists. A "private planning portal" badge is not a verified storage path.

Wedding-planner form, file-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 wedding CRMs without a WordPress.org listing are 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. Seating charts, guest-list spreadsheets, or ID scans are files you accept; they are not documented defaults. An uploaded seating chart is not a published seating assignment. 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
Formidable Forms

Documented WordPress form builder (plugin version 6.35). The listing states every form submission is stored in the WordPress database, not on an external form host, and that entries can be viewed in admin and exported to CSV. Guest names, home addresses, phone numbers, dietary notes, or plus-one relationships are fields you add; they are not documented defaults. A planner inquiry form is not a final guest list. Repeater or table fields that store many guest rows are fields you enable. File uploads are a Pro field, not a Lite default. Optional Mailchimp, Stripe, PayPal, and Zapier paths send data only when you enable them. IP tracking and whether submissions are saved are documented as GDPR controls you set. Public form-page browser hosts are unverified.

Guest-list and inquiry entries stored in your WordPress databaseBrowser 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 guest names or home addresses were sent. A page request from this script is not proof that a guest list was collected. Consent timing has not been tested. Review which tags you enable on inquiry and planning-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. Guest names, home addresses, phone numbers, dietary notes, plus-one relationships, seating charts, or ID scans often depend on the fields you configure. A planner inquiry form is not a final guest list. An uploaded seating chart is not a published seating assignment. A marketing-tag page request is not proof that guest addresses were collected. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the inquiry page, and how long records and backups are kept. Collect guest details in a locked portal, not a public form. A privacy-policy page does not by itself cover the guests named on a list. A "private planning 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 vendor contracts or venue liability. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on inquiry 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-wedding-planner-plugin-privacy