What we record when you visit an event page or RSVP, who can see it, and the cookies we use.
This policy explains what RSVP Host/we records when you visit a public event page hosted on RSVP Host or reply using its RSVP form. Events are run by their organizers, who use RSVP Host to publish the page and collect replies.
Each visit records the following, along with the event, the date and time, and any share button you click:
Your IP address is not stored in the visit record. Visits we recognise as automated, and visits from people signed in to RSVP Host, are not recorded. Organisers see visits as totals and breakdowns on their Analytics page, not as a list of individual visits.
To work out your approximate location, we send your IP address to ipgeolocation.io, a third-party service, which returns the location for that address. This happens for visits and for every RSVP. For a visit, we skip the lookup if we looked up the same address recently or have reached our daily limit, so some visits have no location. We keep a visit's lookup result for up to 30 days to reuse it, filed under a one-way hash of the IP address rather than the address itself.
We store what you enter on the form and give it to the event organiser. That is your reply, company, name, phone number and email address, plus any guest names, answers and comments you add. If you enter a guest's name, please let them know. We also check whether your email address is already registered for the event, and we use it to email you your event pass, which includes a QR code containing your email address.
We also store the following with your registration:
Your IP address and these details are shown to the event organiser, next to your name, on the event's Analytics page.
Event pages set a session cookie, plus a security cookie that protects the form. Neither is used for advertising.
| What it does | How long it lasts |
|---|---|
| Links your browser to your visit. It keeps your language choice and form security token, and remembers where you arrived from, so that an RSVP can be credited to that source. Protects the RSVP form against forged submissions. |
120 minutes after your last request |
While a session is active, our server keeps a session record that includes your IP address and your browser's identifying details. You can block or delete cookies in your browser settings, but the RSVP form cannot be submitted without the session cookie.
Depending on how the organiser set up the page, your browser may connect to these services, which then receive your IP address. Their own privacy policies apply.
Event pass emails are sent through an email delivery provider, which may be one chosen by the organizer.
The event organiser and the team members they give access to can see the details described above, and the organiser decides how to use guest details for their event. The service providers named here receive only what they need to do their job. We may also disclose information when the law requires it.
Depending on where you live, you may have the right to ask for access to, correction of, or deletion of your information. To make a request, contact us at info@rsvphost.com. For questions about how an organizer uses your details for their event, you can also contact the organizer directly.
If we change this policy, we will update it here and change the "Last updated" date above.