Annuity seminar plugin privacy
The free-dinner RSVP that prequalifies you as prey
A dinner RSVP can look like a name, a guest, and a dietary restriction for a free steak. Qualifying questions such as age, retirement, home ownership, and IRA size mean the attendee table is not a guest list. It is a pre-qualified list of home-owning seniors with liquid savings. The attendee never loses a secret; they gain a classification. That row can sit after the dinner ends. An RSVP is not proof anyone attended. A qualifying answer is not a financial recommendation. A page request is not proof anyone RSVP'd. The page URL can say free dinner or annuity seminar 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 RSVP and follow-up consult pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, an annuity-suitability claim, a securities-regulation claim, an SEC or FINRA claim, an elder-fraud-statute 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 dinner RSVPs, follow-up consults, and page tags go
RSVPs and consult bookings handled on your WordPress site
Check which age, retirement, home-ownership, or IRA-size 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 dinner that never became a purchase. Notification emails can also copy the same answers off-site. One table can list every household that RSVP'd even when only the attendee typed. Ask your web vendor not to collect age, retirement, home-ownership, or IRA-size on the same public dinner RSVP as the seat count, not to store follow-up consult answers next to the original RSVP in one open submissions list, and to purge RSVPs after the event. A privacy-policy page does not by itself limit who can export an attendee list. A stored RSVP is not proof anyone attended.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the dinner RSVP or follow-up consult page. That page request can reach a vendor host before anyone submits. The page URL can say free dinner or annuity seminar even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off RSVP and follow-up consult pages if you do not want that page request. A browser scan cannot inspect stored RSVPs. A "free dinner" badge is not a verified storage path.
Annuity seminar RSVP, follow-up consult, 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 seminar CRM or annuity-lead 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 follow-up consult after a free dinner is a booking you create; a service name such as annuity review or retirement consult is a label you configure. Neither is a documented default. Age, retirement, home-ownership, or IRA-size questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked consult is not a purchase and is not a financial recommendation. Cancelling or missing the consult 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 dinner ends 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. | Follow-up consult 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. Age, retirement, home-ownership, or IRA-size questions are fields you add; they are not documented defaults. Guest name and dietary restriction are fields you add; they are not documented defaults. An RSVP submission is not proof anyone attended. 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 an RSVP sits after the dinner ends is not a documented default of the plugin. | Dinner RSVP 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 age, retirement, home-ownership, or IRA-size field was sent. A page request from this script is not proof anyone RSVP'd. The page URL can say free dinner or annuity seminar even when no form is submitted. Consent timing has not been tested. Review which tags you enable on RSVP and follow-up consult pages. Keep marketing tags off those pages if you do not want that page request. A tagged RSVP page can re-confirm a household that already answered qualifying questions; this row does not claim a purchase 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. Age, retirement, home-ownership, or IRA-size fields often depend on the fields you configure. An RSVP is not proof anyone attended. A qualifying answer is not a financial recommendation. A marketing-tag page request is not proof anyone RSVP'd. The page URL can say free dinner or annuity seminar even when no form is submitted. The stored row can sit after the dinner ends. This page is about a qualifying RSVP that classifies the attendee, not a reverse-mortgage form filled by adult children, an estate-sale inventory, an assisted-living application, a notary journal, a tax-preparer intake, a matchmaking profile, or a timeshare-exit consult. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the RSVP or follow-up consult page, and how long records and backups are kept. A "secure" or "free dinner" 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 annuity suitability, securities regulation, or purchase outcomes. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on RSVP and follow-up consult 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-annuity-seminar-plugin-privacy