Sub-processors
Last updated
The short version
These are the companies that help us run WhoComing and may process personal data that organizers collect through it. Each is bound by a written agreement with data protection terms at least as strict as our data processing agreement.
We use no analytics or advertising services on the website, the dashboard or the widget, so none appear here.
1. Current sub-processors
| Company | What it does for us | Data it handles | Location |
|---|---|---|---|
| Vercel Inc. | Hosting for the website, dashboard, API and the widget script | Everything sent to or from WhoComing passes through it, including guest RSVPs and request logs with IP addresses | United States [hosting region to be confirmed] |
| Managed Postgres provider (to be confirmed before launch) | Database | All stored data: organizer accounts, events, guest RSVPs and answers | United States [provider and region to be confirmed] |
| Resend (Plus Five Five, Inc.) | Sending email: RSVP confirmations, reminders and waitlist notices for guests; sign-in links and account notices for organizers | Recipient name and email address, event details, and the email's content | United States |
| Stripe, Inc. | Subscription payments and invoices for organizers | Organizer billing details only. No guest data | United States |
| Upstash, Inc. | Rate limiting | Short-lived request counters labelled with a keyed hash of the IP address, an API key ID or an event ID. No names or email addresses | [Upstash region to be confirmed] |
| Functional Software, Inc. (Sentry) | Error monitoring for the website, dashboard and API. The widget sends nothing to Sentry | Error reports, which can include request details and the IDs of the records involved | United States [Sentry data region to be confirmed] |
| Cloudflare, Inc. | Turnstile bot protection when a guest sends an RSVP | The guest's IP address and browser signals, used to tell people from bots. Not their name or email | Global network, company in the United States |
Our database provider is not chosen yet. We will name it here, with its region, before the public launch.
2. Services that are not sub-processors
If an organizer chooses to sign in with Google, Google provides that sign-in under its own terms. It receives no guest data from us.
Webhook endpoints, exports and API calls send data where the organizer tells us to. Those destinations are the organizer's choice, not our sub-processors.
3. Changes to this list
We will email the owner of every organization at least 30 days before a new sub-processor starts handling customer data, and update this page. If you object on reasonable data protection grounds, tell us at [privacy contact email, for example privacy@whocoming.com]. The data processing agreement explains what happens next.