Events plugin data paths
Where WordPress event plugins keep or send attendee details
Event calendars and RSVP forms collect names, emails, and attendance details. Some WordPress plugins keep those records on your host. Ticketing and scheduling embeds load outside services on the page. This table summarizes the documented setups below. Your settings can change where data goes.
Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.
Scan your events pageHow we group event plugins and embeds
We compare the event and calendar setups named below. A plugin can keep event or attendee records on your server and still load an outside embed or payment tool. Embeds such as Eventbrite and Calendly are listed separately from WordPress plugins. We have not tested when requests start relative to cookie consent or assessed how long data is kept.
Event plugins and embeds
No paid placement. On your server first, then outside services, then plugins not yet reviewed. Names are alphabetical within each group.
| Plugin or embed | Documented behavior | Receiving domains | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Events Manager (local bookings) Events Manager privacy docs: booking and event submissions are collected and stored on your site for reservations and attendance records. Optional Pro payment gateways (PayPal, Stripe, and others), Google Maps, and location autocomplete are outside this local-bookings row. | On your server | Receiving domains not verified | Not assessed | Not tested |
| |
| The Events Calendar (local events) The Events Calendar GDPR notes: event, venue, and organizer details collected through the plugin are stored in your WordPress database. The vendor states it does not collect or store your visitors end-user data through standard plugin use. Optional Event Aggregator, ticketing, and map services are outside this local-events row. | On your server | Receiving domains not verified | Not assessed | Not tested |
| |
| Calendly embed Calendly embed options load Calendly-hosted scheduling UI on the page that embeds them. Invitee details are collected in Calendly, not as native WordPress bookings. This row covers embeds. Verified receiving domains are not listed here. | Outside service | Receiving domains not verified | Not assessed | Not tested |
| |
| Eventbrite embed Eventbrite embedded checkout docs: checkout loads as an Eventbrite-hosted embed on the page that includes it. Attendee and checkout data is handled on Eventbrite, not in your WordPress database. This row covers embeds, not a native WordPress event plugin. Verified receiving domains are not listed here. | Outside service | Receiving domains not verified | Not assessed | Not tested |
| |
| Amelia We have not reviewed this plugin's event data path yet. | Not reviewed | Documentation not reviewed yet. | Not assessed | Not tested |
| |
| Bookly We have not reviewed this plugin's event data path yet. | Not reviewed | Documentation not reviewed yet. | Not assessed | Not tested |
|
What this table does and does not prove
This table describes the named event setups and embeds. It does not show what loads on your site. Local storage and outside embeds can both apply. We have not tested consent timing, and we have not assessed how long data is kept. This scan does not read attendee records inside your database.
Documentation snapshot: Sep 28, 2026. Sources are linked in each reviewed row.
Scan your events page/wp-events-plugin-privacy