Skip to Content

Data rights

Export everything you hold about a guest, erase a guest by email, and how long guest details are kept.

When a guest asks what you hold about them, or asks you to delete it, you can answer with one call. Both calls work on the mode of the key you use, so use a live key for real guests.

Export a guest's data

curl "https://api.whocoming.com/v1/guests/export?email=ada@example.com" \
  -H "Authorization: Bearer wc_live_..."
{
  "email": "ada@example.com",
  "mode": "live",
  "exported_at": "2026-12-01T15:04:05Z",
  "rsvps": [
    {
      "id": "rsvp_9a2c4e6g8i0k2m4o6q8s",
      "event_id": "evt_demo0000000000000001",
      "name": "Ada Lovelace",
      "email": "ada@example.com",
      "status": "going",
      "guests": 1,
      "answers": { "deck": "Mono red aggro" },
      "...": "...",
      "event": {
        "id": "evt_demo0000000000000001",
        "title": "Friday Night Magic",
        "starts_at": "2027-01-08T18:30:00-05:00",
        "timezone": "America/Detroit"
      }
    }
  ]
}

Every RSVP for that email in your organization, each with its event. Needs the rsvps:read scope.

Erase a guest

curl -X POST https://api.whocoming.com/v1/guests/erase \
  -H "Authorization: Bearer wc_live_..." \
  -H "Content-Type: application/json" \
  -d '{"email":"ada@example.com"}'
{ "email": "ada@example.com", "mode": "live", "rsvps_erased": 3 }

Deletes every RSVP with that address across your organization, in the key's mode: a live key erases live RSVPs, a test key test ones. (In the dashboard, erasing covers both modes.) This cannot be undone. rsvps_erased is how many RSVPs were deleted. Needs the rsvps:write scope.

What else happens:

  • Counts go down. The deleted RSVPs no longer hold seats, so the event's going and spots_left change.
  • The waitlist can move up. If the guest was going to a full event, the next person on the waitlist who fits is promoted and emailed, exactly as when someone cancels.
  • Webhooks. Each deleted RSVP that was not already cancelled sends rsvp.cancelled with identifiers only and "deleted": true, never the erased details. The guest's name, email and answers are also removed from deliveries already stored in the delivery log.
  • Usage is not refunded. RSVPs already counted this month stay counted.

To remove one RSVP rather than a person, use DELETE /v1/rsvps/{id}.

Retention

Guest details do not stay forever. By default, 365 days after an event ends, the name, email and answers on its RSVPs are replaced with null. The RSVP itself (status, plus-ones, check-in time) stays, so your attendance numbers stay right.

Your code should therefore treat name, email and answers as nullable on any RSVP.

What we keep about visitors

  • IP addresses are never stored as is. They are hashed to apply rate limits, and the hashes are kept for at most 30 days.
  • The widget sets no cookies and stores nothing on the guest's device unless they ask to be remembered. See embed privacy.

On this page