Guest responses and attendee lists
Who can see your guest list?
RSVP plugins collect guest names, emails, meal preferences, and plus-one details. Some can show who is attending on the page or accept open registration links. Others gate access with an invite or party code. Calendars and ticketing embeds have a separate page. Compare the documented setups below.
Based on plugin documentation, not tests of your site. Attendee-list settings, invite codes, and retention decide what outsiders can see. This is not legal advice or a compliance rating.
Scan your site for third-party requestsThis scan checks requests made by a visitor's browser on an RSVP page, including CAPTCHA, maps, or embeds when they load. It does not inspect submitted guest details or database records, test invitation access, show server-side email or SMS transfers, or assess how long responses remain after the event.
Open guest lists vs gated RSVPs
Responses stored on your WordPress site
Check whether a public attendee list is enabled and which names or notes it shows. Review who can open each invitation link or use each code; a code alone does not establish that the guest list is private. Check which fields and browser details you collect and how long records remain after the event.
Hosted RSVP dashboards and outside connectors
Some embeds send guest responses to a vendor dashboard instead of keeping them only in WordPress. Payment or email connectors can also move guest details off your site when enabled. Server-side transfers do not appear in a browser page scan. Review each hosted form and connector before you publish the RSVP page.
RSVP setups
No paid placement. Site-hosted RSVP tools appear first, followed by any vendor-connector group, then unreviewed rows. Site-hosted tools may still use outside CAPTCHA, payment, email, or SMS services when enabled. Review attendee-name display separately. Names are alphabetical within each group.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| ARIWEB Event Invitations & RSVP Documented self-hosted invitations with per-invitation guest limits and access links. Invitations can use short links or secure links with an additional access token. Assigned guest names can be shown or hidden on the public RSVP form. PDF invitations can include a clickable RSVP link and may be stored as media on the site. When reCAPTCHA v3 is configured, the public form loads Google's script from www.google.com. The server verifies the token with Google and includes the visitor's IP address. The listing also says local RSVP records can include IP addresses and browser information. Review these paths separately from guest-name visibility. Review invitation link settings, what appears on the public form, and PDF storage. Other browser hosts were not verified for this snapshot. | Guest responses stored on your WordPress site | www.google.com | Not assessed | Not tested |
| |
| RSVP and Event Management Documented self-hosted RSVP forms via the [rsvp] shortcode. Open Registrations can let people register themselves. Prefill URLs can include first name, last name, and a passcode when passcodes are enabled or required. Pro documents a front-end attendees list, waiting lists, reminder emails, and QR codes. Review whether the attendees list is enabled, how passcodes are used, and how long guest records remain after the event. Browser hosts were not verified for this snapshot. | Guest responses stored on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| RSVPMaker Documented self-hosted event RSVPs that can collect guest names and other form fields. Vendor docs list a Display attendee names / RSVP note field option among RSVP settings. Optional PayPal or Stripe payments and Mailchimp or Postmark email paths are documented separately. Review attendee-name display settings, which fields you collect, and any payment or email connectors you enable. Browser hosts were not verified for this snapshot. | Guest responses stored on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| Wedding Party RSVP Documented self-hosted wedding guest list. Guests RSVP with a Party ID (invite code) rather than a WordPress account. The listing says core RSVP storage does not call third-party APIs, and guest records live in the WordPress database. Optional paths include a Wedding RSVP App Network registration that stores directory metadata only (no guest list), Google Maps venue links, and reCAPTCHA on a guestbook when configured. Optional reminder and follow-up emails use your WordPress email configuration. The listing also names Twilio for optional SMS reminders and follow-ups when the Pro add-on is configured. Review email and SMS delivery separately from local RSVP storage. Review Party ID distribution, which meal and dietary fields you collect, and any optional connectors. Browser hosts were not verified for this snapshot. | Guest responses stored on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| ouRSVP Event RSVP Forms Documented WordPress embed for ouRSVP.app forms. You create the event on ouRSVP, then place a block or shortcode with the event ID. The listing says guest management happens in the ouRSVP dashboard rather than locking responses only inside WordPress, including dietary tracking and guest-list export. The listing documents a widget script and form/guest API endpoints on www.oursvp.app. Review which guest fields the hosted form collects and where responses are stored after the event. Other browser hosts were not verified for this snapshot. | Guest responses can sync to a vendor service | www.oursvp.app | Not assessed | Not tested |
|
What this table does and does not prove
This table describes documented RSVP workflows, not tests of your site. Consent timing, live attendee-list exposure, invite-code strength, and post-event retention lengths have not been assessed. Check attendee-list settings, access gating, guest fields, and any hosted RSVP or payment connectors. Event calendars and ticketing embeds are covered on the events page.
Documentation snapshot: Oct 8, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress events plugin privacy
- WordPress forms privacy
- WordPress QR code plugin privacy
- All privacy guides
/wp-rsvp-plugin-privacy