Privacy and cookies for the WhoComing embed
Last updated
The short version
This page is for organizations that put the WhoComing RSVP widget on their website. Hand it to whoever runs your cookie banner or reviews your privacy policy.
- The widget sets no cookies, and its calls to the WhoComing API are made with cookies left out.
- It stores nothing by default. It saves the guest's name and email in the browser only if the guest ticks "Remember me on this device".
- It talks to WhoComing and, when a guest sends an RSVP, to Cloudflare Turnstile. Nothing else: no analytics, no advertising, no error tracking, no fonts or images from anywhere.
- IP addresses are used only for rate limiting and stopping abuse, kept as a keyed hash, and deleted within 30 days.
1. What the widget stores on the device
One entry in the browser's local storage, and only after the guest asks for it.
| Item | Details |
|---|---|
| Type | Local storage (not a cookie). Never expires on its own. |
| Key | whocoming:guest |
| Contents | The guest's name and email address, for example {"name":"Ada","email":"ada@example.com"}. Nothing else. |
| When it is written | When the guest sends an RSVP with "Remember me on this device" ticked. The box is unticked by default. |
| What it is for | Filling in the name and email next time the guest RSVPs on the same site, in the same browser. |
| Where it lives | In your website's own storage area (your domain), because the widget runs inside your page. Other websites cannot read it. |
| Who it is sent to | No one, unless the guest sends another RSVP; then the name and email go to WhoComing as part of that RSVP, as typed in the form. |
How a guest removes it
- Send an RSVP with "Remember me on this device" unticked. The widget deletes the entry.
- Or clear this website's data in the browser settings ("Cookies and site data" in most browsers).
- Developers can run
localStorage.removeItem("whocoming:guest")in the browser console on your site.
If the browser blocks storage (some private modes do), the box simply does nothing and the RSVP still works.
Our reading is that this entry needs no cookie banner consent, because the guest asks for it directly by ticking the box. That is for you and your adviser to confirm for your own site.
2. What requests the widget makes
Every request below is made by the visitor's browser. The two calls to api.whocoming.com are made with cookies left out, so no cookie is sent or set by them, whatever the browser holds.
| When | To | What is sent |
|---|---|---|
| The page loads | cdn.whocoming.com | Downloads the widget script (embed.js) and its main file. A normal file download. |
| The widget appears | api.whocoming.com | Asks for the event's public details: title, time, place, spots left and the RSVP form. Sends only the event ID. |
| The guest presses Send | challenges.cloudflare.com | Loads Cloudflare Turnstile and runs a bot check, usually invisibly. See Cloudflare Turnstile. |
| The guest presses Send | api.whocoming.com | The RSVP: name, email, number of extra guests, answers to the organizer's questions, the Turnstile result, and a hidden field that should be empty (it catches bots). |
Like any web request, each of these also carries the visitor's IP address, browser type and the address of your page. That is how the web works; we explain below what WhoComing does with the IP address.
After an RSVP, the widget shows links the guest may choose to open: add to Google Calendar, download a calendar file, change or cancel the RSVP, and on some plans "RSVP by WhoComing". These are ordinary links. Nothing is requested unless the guest clicks one.
The widget sends nothing to error tracking or analytics services, including ours. If it hits a problem it tells your page through a whocoming:error event, and that is all.
3. What the widget adds to your page
Besides the RSVP box itself, which lives inside its own element, the widget adds one thing: for a public event, a small block of event details for search engines (a <script type="application/ld+json"> tag in the page head). It holds the event's public details only, never anything about guests. It is removed when the widget is removed.
4. IP addresses
WhoComing uses a visitor's IP address only to limit how often one device can RSVP (for example, five tries a minute per event) and to stop abuse.
- Before our application uses or stores an IP address, it turns it into a keyed hash. The raw address is not saved in our database or used as a rate-limit key.
- Hashed addresses are deleted within 30 days.
- Our hosting provider keeps its own request logs, which include IP addresses, for [hosting provider log retention period, to be confirmed]. See the sub-processor list.
5. Cloudflare Turnstile
Turnstile is Cloudflare's bot check. It replaces the "click all the traffic lights" kind of test. The widget loads it only when a guest presses Send, and runs it in a mode that shows nothing unless Cloudflare needs the guest to click a box.
To tell people from bots, Cloudflare processes the visitor's IP address and signals from the browser. It does not receive the guest's name, email or answers. Cloudflare describes this in its Turnstile privacy addendum.
Not final yet: we are confirming in testing exactly what Turnstile itself stores in the browser (cookies or local storage) before we state it here as fact. Until then, treat Turnstile as something that may store data on the device, only for bot protection, and only after the guest presses Send. Our Turnstile setup does not use Cloudflare's pre-clearance feature, which sets a cookie [to be confirmed in the Cloudflare settings before launch].
6. The iframe version
Some site builders do not allow script tags, so WhoComing also offers the widget as an iframe from whocoming.com/embed/. It is built to the same rules: no cookies, no analytics, and the same "Remember me" behaviour, except that the saved entry would belong to whocoming.com rather than your site. Some browsers block storage inside iframes; then the box does nothing.
We check this section against the iframe page each time that page changes.
7. Who is responsible for what
The organization running the event decides what to collect and why, so it is the controller of its guests' data. OMOWorlds LLC processes that data on the organization's behalf, under our data processing agreement. We never sell it, never use it for advertising, and never send guests marketing email.
Guests with a question about their RSVP should ask the organizer. Organizers can reach us at [privacy contact email, for example privacy@whocoming.com].
8. For your consent tool
If your cookie banner asks you to list what each script does, this is what we suggest:
| Name | Type | Purpose | Suggested category |
|---|---|---|---|
| WhoComing widget | Script, no cookies | Shows the RSVP form and sends RSVPs | Necessary (it is the feature the visitor uses) |
whocoming:guest | Local storage | Remembers name and email, only if the guest ticks "Remember me" | Functional, set at the guest's request |
| Cloudflare Turnstile | Script | Bot check when an RSVP is sent | Necessary (security) [pending our storage test above] |
A sentence you could add to your own privacy policy: "We use WhoComing to take RSVPs for our events. When you RSVP, your name, email and answers go to WhoComing, which handles them for us. WhoComing does not set cookies and does not use your details for its own purposes."