Eventonomy

Privacy & GDPR (Data Export & Erase)

Eventonomy stores attendee and buyer data - RSVPs and orders - in its own custom tables (evnm_rsvps, evnm_orders), not in WordPress posts or comments. Core's built-in privacy tools never see those tables on their own, so Eventonomy hooks itself into Tools → Export Personal Data and Tools → Erase Personal Data. That means a standard data-subject request covers a person's Eventonomy records alongside their core WordPress data, with no extra plugin or manual export.

This is what lets you answer a GDPR/CCPA "give me my data" or "delete my data" request for someone who registered for or bought a ticket to one of your events.

What You Will Learn

  • How Eventonomy plugs into WordPress's personal-data tools
  • Exactly what a data export contains
  • What an erase request removes, anonymizes, and deliberately keeps

How It Works

Eventonomy registers one exporter and one eraser, both named "Eventonomy (events, RSVPs & orders)", under the standard WordPress screens:

  • Tools → Export Personal Data
  • Tools → Erase Personal Data

You run a request the normal WordPress way: enter the person's email address, send/confirm the request, and Eventonomy's data is included automatically in the same report or erasure that covers WordPress core.

A person is matched two ways, so both members and guests are covered:

  • Registered members - matched by their user account (resolved from the request email).
  • Guests - matched by the email address recorded on their guest RSVP or order, even if they never created a WordPress account.

What an Export Contains

An export returns two groups:

Event RSVPs - one entry per RSVP:

Field Meaning
Event ID The event the person registered for
Status going / maybe / no / waitlist
Name Name given on the RSVP
Email Email given on the RSVP
Phone Phone given on the RSVP (if any)
Guests Number of additional guests
Registered When the RSVP was created

Event Orders - one entry per order:

Field Meaning
Order Number The human-readable order reference
Event ID The event the order is for
Name Buyer name
Email Buyer email
Total Order total with currency
Status pending / paid / refunded / cancelled
Placed When the order was placed

Large histories are paginated automatically (50 records per page), so an export completes even for a member with hundreds of RSVPs or orders.

What an Erase Removes - and What It Keeps

Erasing is deliberately not a blind delete, because two different legal obligations apply to two different kinds of record:

  • RSVPs are anonymized. Name, email, phone, and response details are cleared and the record is detached from the member's account. The RSVP row itself is kept so your event capacity and attendance counts stay correct - an anonymized RSVP still occupies its seat, it just no longer identifies a person.
  • Orders keep their financial record. Personal identifiers on the order are stripped, but the financial fields (order number, totals, gateway, transaction reference) are retained under the tax and accounting legal-basis exemption that lets you keep sales records. When this happens, WordPress reports back to the admin running the request that some records were retained for compliance.

This mirrors how most commerce plugins treat orders: you cannot legally erase the financial trail of a completed sale, but you can and should strip the personal identity attached to it.

Note: Eventonomy Pro adds a separate exporter/eraser for a member's followed events and organizers. See Privacy & GDPR (Pro).

Related