Privacy policy
Last updated
The short version
This policy covers the people who run events on WhoComing (organizers and their teams), people who pay us, and visitors to whocoming.com. For that data, OMOWorlds LLC decides what is collected and why.
If you RSVPed to an event, the organization running it decides what it collects about you. We hold your RSVP on its behalf. See Guests.
We do not sell personal data or share it for advertising. There are no ad pixels or analytics trackers on our website, dashboard, event pages or widget. We never send guests marketing email.
1. Who we are
WhoComing is run by OMOWorlds LLC, a Michigan limited liability company, at [OMOWorlds LLC postal address]. For anything in this policy, email [privacy contact email, for example privacy@whocoming.com].
This policy takes effect on [effective date].
2. Guests: data we handle for organizers
When you RSVP through a WhoComing widget, event page or an organizer's own app, the organizer is in charge of your details: your name, email, how many people you are bringing, and any answers to its questions. We process them only to run the RSVP for that organizer, under our data processing agreement with it.
That means:
- We send you only messages about your RSVP: the confirmation, waitlist news, reminders if the organizer has them on, and notice if the event changes or is cancelled. Replies go to the organizer.
- We never add you to a WhoComing mailing list or send you marketing email.
- We never sell your details or use them for advertising, and we do not combine them across organizers.
- Each confirmation email has a link to change or cancel your RSVP. You never need an account.
To see, correct or delete your details, ask the organizer. They can do it for you in the dashboard or with our API. If you contact us instead, we will pass your request to the organizer. If you cannot reach them, email [privacy contact email, for example privacy@whocoming.com] and we will help.
What the widget stores in your browser is explained on Privacy and cookies for the WhoComing embed.
3. What we collect about organizers and why
| What | Why | Legal basis (UK and EU) |
|---|---|---|
| Account details: your name, email address, and the organizations and roles you belong to. If you sign in with Google, the name, email and profile picture Google shares with us. | To create your account, sign you in, and let your team work together. | Contract |
| Sign-in records: one-time sign-in links (stored only as a hash and valid for 15 minutes), and session records with your browser type and a keyed hash of your IP address (never the address itself). | To keep you signed in and to spot sign-ins that are not you. | Contract and legitimate interests (security) |
| Billing details: plan, billing name, address, tax ID if you give one, and payment history. Stripe holds your card details; we never see the full number. | To charge for paid plans and keep tax and accounting records. | Contract and legal obligation |
| Usage: how many RSVPs your organization took this month, when each API key was last used, webhook delivery results. | To apply your plan's limits, bill overage, warn you at 80% and 100% of your limit, and help you debug. | Contract |
| Messages you send us, such as support emails. | To answer you. | Legitimate interests |
| Technical data: IP address, browser type and the pages or endpoints requested, in our hosting provider's logs and in error reports. | To keep the service running, fix bugs and stop abuse. IP addresses used for rate limiting are kept as a keyed hash for at most 30 days. | Legitimate interests (security and reliability) |
We do not ask for or collect more than this, and we do not buy data about you from anyone.
4. This website, cookies and similar storage
whocoming.com has no analytics, no advertising pixels and no third-party trackers. What it does store:
- A session cookie when you sign in, so you stay signed in. It is removed when you sign out or it expires.
- Your light or dark mode choice, in your browser's local storage under
wc-theme, if you change it.
Both are needed for things you asked for, so we do not show a cookie banner. Live demos of the RSVP widget on this site follow the embed privacy rules.
5. Email we send to organizers
We send account email you need: sign-in links, usage warnings, billing receipts, failed webhook notices, and notice of changes to these terms. You cannot turn these off while you have an account.
If we send product news or tips, each one will have a one-click unsubscribe link, and unsubscribing will not affect your account email.
7. How long we keep data
- Account details: while your account is open. After you cancel or close it, you have 30 days to export your data. We then delete or anonymize it within [deletion period after the export window], except what we must keep by law.
- Billing records: as long as tax and accounting law requires, which in the United States is usually up to seven years.
- Hashed IP addresses used for rate limiting: at most 30 days.
- Sign-in sessions and sign-in links: until they expire or you sign out. Expired ones are deleted every day.
- Guest RSVPs: as the organizer decides. By default, guest names, emails and answers are anonymized 365 days after the event ends; organizers can shorten or lengthen this.
- Backups: deleted data can remain in our database provider's backups until they expire, for [backup retention period, to be confirmed when the database provider is chosen].
8. Your rights
Wherever you live, you can ask us to:
- tell you what personal data we hold about you and send you a copy;
- correct it;
- delete it;
- send it to you, or another service, in a common format;
- stop or limit using it for a purpose, or object to a use based on our legitimate interests;
- withdraw consent where we relied on it.
Most of this you can do yourself in the dashboard. Otherwise email [privacy contact email, for example privacy@whocoming.com]. We may need to confirm it is really you. We will reply within one month, and will not charge you or treat you differently for asking. You may let someone else ask for you, with your written permission.
If you are in the UK or the EU, you can also complain to your data protection authority. If you are in a US state with a privacy law and we turn down your request, you can appeal by replying to our answer; if we still say no, you can contact your state attorney general.
9. Where data is stored
WhoComing is run from the United States and stores data there [hosting and database region to be confirmed]. If you are outside the US, your data is transferred to the US.
For data from the UK, the EU and Switzerland, we rely on the European Commission's standard contractual clauses and the UK addendum to them, in our agreements with organizers and with our sub-processors.
10. How we protect data
Data travels encrypted (HTTPS). API keys and RSVP manage links are stored only as hashes and shown once; webhook signing secrets are encrypted. Each organization's data is kept apart in the database itself, not just in our code. No security is perfect; if a breach affects your data, we will tell you without undue delay.
To report a security problem, email [security contact email, for example security@whocoming.com].
11. Children
WhoComing is a general-audience service, not made for children. Organizer accounts are for adults.
Families often RSVP for events such as game nights. Our terms require that an RSVP for a child under 13 is made by a parent or guardian, who gives their own name and email. RSVP forms never ask for a date of birth. The form editor in the dashboard has a ready-made checkbox organizers can add in one click: "I am 13 or older, or I am a parent or guardian RSVPing for a child".
If you think a child under 13 has given us personal data without a parent, email [privacy contact email, for example privacy@whocoming.com] and we will delete it.
12. Changes to this policy
If we make a change that matters, we will email account owners and show it here at least 30 days before it takes effect. The date at the top shows the last change.
13. Contact
OMOWorlds LLC, [OMOWorlds LLC postal address]. Email [privacy contact email, for example privacy@whocoming.com].