Privacy
The widget sets no cookies, runs no analytics and stores nothing unless the guest asks it to remember them.
What the widget does on your visitors' browsers, in full:
- No cookies. Requests to the API are sent without credentials, so no cookie is sent or set, whatever the API does.
- No analytics, no tracking pixels, no fingerprinting.
- No storage by default. Nothing goes into
localStorage,sessionStorageor IndexedDB, unless the guest ticks Remember me on this device. Then their name and email are saved inlocalStorageunder the keywhocoming:guest, to fill the form next time. Sending an RSVP with the box unticked deletes it. - Requests go to three places only: our CDN for the widget's own script (
cdn.whocoming.com), our API (api.whocoming.com), and Cloudflare Turnstile (challenges.cloudflare.com), which is loaded only when a guest sends the form, to keep bots out. Turnstile usually runs invisibly and shows a challenge only when Cloudflare needs one. - No error reporting to third parties. Errors are fired as a
whocoming:errorevent on your page and go nowhere else.
What a guest's RSVP stores
Name, email, plus-ones, answers to your questions, and when they RSVPed. The IP address is hashed before it is used for rate limiting, and hashes are kept for at most 30 days. See data rights for export, erasure and retention.
Cookie banners
Because the widget sets no cookies and stores nothing without the guest's own action, it does not by itself need a cookie consent banner in most jurisdictions. Check with your own advisers for your situation.