Class reunion plugin privacy

The RSVP that reports what became of you to the people you were avoiding

A class-reunion RSVP can look like a headcount and a banquet seat. The same intake often asks for a life-outcome update, a memory, a then-and-now photo, and a plus-one name — and stores those answers next to a classmate's contact details for the life of the form table. Those fields are configured, not documented defaults. The audience is the exposure: the implied readers are the exact graduating cohort. Declining by silence is still an answer when a published attendee list makes every non-RSVP legible by omission. An RSVP is not proof anyone attended. A life-update answer is self-reported, not a record of what became of anyone. An attendee list's omissions are the organizer's publication habit, not a statement about the missing. A page request is not proof anyone RSVP'd. The page URL can say class reunion even when no form is submitted. Ask what happens to the life-update answer and the then-and-now photo after the weekend — the update form is read by the whole graduating class. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the RSVP page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, an alumni-association claim, a school-records or FERPA claim, a reunion-attendance claim, 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 RSVPs, life updates, banquet bookings, and page tags go

RSVPs and bookings on your WordPress site

Check which life-update, memory, then-and-now photo, plus-one, or dietary fields you enable, who can open form entries and banquet bookings, which inboxes receive copies, and how long records, emails, and backups are kept after the reunion weekend ends. Notification emails can also copy those fields off-site. One table can list every classmate who typed what became of them. Ask your web vendor not to keep life-update text next to contact details in one open submissions list longer than operations need, and to purge intake rows when the weekend is over. A privacy-policy page does not by itself limit who can open a submissions list. A stored RSVP is not proof of attendance. A life-update answer is self-reported, not a record of what became of anyone.

Page tags handled by a vendor

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

Class-reunion RSVP, booking, 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 reunion 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 banquet seat, campus tour, or photo-booth slot is a booking you create; a service name such as class-of-2004 dinner is a label you configure. Neither is a documented default. Life-update, memory, plus-one, or dietary questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof of attendance — and a CSV export of banquet seats next to life-update answers is still a name-keyed list of what classmates typed for the cohort to read. 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.

Class-reunion banquet and walk-through 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. Life-update, memory, plus-one, or then-and-now photo questions are fields you add; they are not documented defaults. Completing the form can store a life summary whose implied readers are the graduating cohort. A submitted RSVP is not proof of attendance. A life-update answer is self-reported, not a record of what became of anyone — and a then-and-now photo next to a plus-one name can sit in the same row as the classmate's contact details. A staff login can open the memory text next to the life-update answer. 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.

RSVP and life-update entries stored in WordPress; optional then-and-now 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 life-update, memory, or plus-one field was sent. A page request from this script is not proof anyone RSVP'd. The page URL can say class reunion even when no form is submitted. Consent timing has not been tested. Review which tags you enable on RSVP and banquet 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. Life-update, memory, then-and-now photo, or plus-one fields often depend on the fields you configure. An RSVP is not proof anyone attended. A life-update answer is self-reported, not a record of what became of anyone. An attendee list's omissions are the organizer's publication habit, not a statement about the missing. A marketing-tag page request is not proof anyone RSVP'd. The page URL can say class reunion even when no form is submitted. The audience is the exposure — that is a storage path next to a name, not a feature these plugins claim. This page is about that cohort-broadcast intake, not a race-registration results page, a matchmaking profile, a genealogy research request, or a summer-camp registration. Ask your web vendor who can open entries, whether a marketing tag loads on the RSVP page, and how long records and backups are kept. A "private classmates-only" 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 alumni-association policy, school records or FERPA, or reunion-attendance claims. Review stored records, bookings, connected services, exports, notification emails, marketing tags on RSVP 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-class-reunion-plugin-privacy