Data processing agreement
Last updated
The short version
When your guests RSVP, you decide what is collected and why; we store and process it for you. This agreement sets out the rules we follow while doing that, as GDPR Article 28 and US state privacy laws require.
It is part of our terms of service and applies automatically when you accept them. You do not need to sign anything. If your organization needs a countersigned copy, email [privacy contact email, for example privacy@whocoming.com].
1. Parties and scope
This data processing agreement ("DPA") is between the organization that accepted the WhoComing terms ("Customer", the controller) and OMOWorlds LLC, a Michigan limited liability company ("WhoComing", the processor). It applies to all Customer Personal Data that WhoComing processes in providing the service.
Customer Personal Data means personal data about Customer's guests that WhoComing processes on Customer's behalf: everything submitted through Customer's widgets, event pages, API calls and dashboard. It does not include data about Customer's own account users, which WhoComing handles as controller under its privacy policy.
Data Protection Laws means the laws that apply to the processing, which may include the EU General Data Protection Regulation (GDPR), the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, and US state privacy laws such as the California Consumer Privacy Act as amended (CCPA). Terms such as "controller", "processor", "personal data breach" and "data subject" have the meanings those laws give them.
2. Details of the processing
| Item | Details |
|---|---|
| Subject matter | Providing WhoComing: collecting and managing RSVPs for Customer's events. |
| Duration | For as long as Customer uses WhoComing, plus the export and deletion period in section 10. |
| Nature and purpose | Receiving RSVPs through the widget, hosted pages and API; storing them; showing them to Customer in the dashboard, exports and API; enforcing capacity and running waitlists; sending guests transactional email about their RSVP (confirmation, waitlist, reminders, changes); checking guests in; delivering webhooks to endpoints Customer sets up; preventing abuse and bots. |
| Types of personal data | Guest name and email address; number of additional guests; answers to questions Customer adds to the RSVP form; RSVP status, check-in time and history; a hash of the guest's private manage link; IP address, used only in keyed-hash form for rate limiting and kept at most 30 days; browser signals processed by the bot check. |
| Special categories | None are needed. Customer must not configure questions that collect special category data or data about criminal convictions unless Data Protection Laws allow it. |
| Data subjects | People who RSVP to Customer's events, including parents or guardians RSVPing for children. |
| Frequency | Continuous, while Customer uses the service. |
3. Customer's instructions
WhoComing processes Customer Personal Data only on Customer's documented instructions. Those instructions are: the terms of service, this DPA, and Customer's use and configuration of the service, including the dashboard, settings and API calls. Customer may give further reasonable written instructions consistent with these.
WhoComing will tell Customer if it believes an instruction breaks Data Protection Laws, unless the law forbids telling. WhoComing may process data otherwise only if the law requires it, and will tell Customer first unless the law forbids that too.
Customer is responsible for having a lawful basis and any required consent for the data it collects, for its notices to guests, and for the lawfulness of its instructions.
4. WhoComing's obligations
WhoComing will:
- make sure everyone it authorizes to process Customer Personal Data is bound by confidentiality;
- apply the security measures in section 7;
- use sub-processors only as section 5 allows;
- help Customer respond to data subject requests (section 9), and with security, breach notification, data protection impact assessments and consultations with authorities, taking into account the nature of the processing and the information available to WhoComing;
- delete or return Customer Personal Data at the end of the service (section 10);
- make available the information needed to show it meets this DPA, and allow audits (section 11);
- never sell Customer Personal Data, use it for advertising, add guests to WhoComing's own mailing lists, or combine it with data from other customers.
5. Sub-processors
Customer gives WhoComing general authorization to use sub-processors. The current list, with each one's purpose and location, is at whocoming.com/legal/subprocessors.
WhoComing will bind each sub-processor by written contract to data protection terms that protect Customer Personal Data at least as well as this DPA, and remains responsible to Customer for its sub-processors' performance.
WhoComing will email Customer's account owner at least 30 days before a new sub-processor begins processing Customer Personal Data. Customer may object on reasonable data protection grounds within that time. The parties will then discuss it in good faith. If they cannot resolve it, Customer may end the affected part of the service and receive a refund of fees prepaid for the period after it ends.
6. International transfers
WhoComing processes and stores Customer Personal Data in the United States [hosting and database region to be confirmed]. Some sub-processors operate globally, as their entries on the sub-processor list say.
- EU: for transfers from the European Economic Area, the standard contractual clauses approved by Commission Implementing Decision (EU) 2021/914 ("SCCs") apply and are incorporated into this DPA: Module 2 (controller to processor), with Clause 7 (docking) included, the optional wording in Clause 11 left out, option 2 (general authorization) in Clause 9 with the notice period in section 5, Irish law in Clause 17 and the courts of Ireland in Clause 18. Annex I is completed by section 2 of this DPA, Annex II by section 7, and Annex III by the sub-processor list.
- UK: for transfers from the UK, the International Data Transfer Addendum issued by the UK Information Commissioner applies, with the SCCs as completed above. Either party may end it as its Section 19 allows.
- Switzerland: for transfers from Switzerland, the SCCs apply with references to the GDPR read as references to the Swiss Federal Act on Data Protection, and the Swiss Federal Data Protection and Information Commissioner as the competent authority.
WhoComing uses the same kind of safeguards in its contracts with sub-processors that receive Customer Personal Data outside the countries it came from.
Whether WhoComing should also certify to the EU-US Data Privacy Framework, and the SCC module choices above, are questions for the legal review. WhoComing is not currently certified under the Data Privacy Framework.
7. Security measures
WhoComing keeps technical and organizational measures appropriate to the risk, including:
- In transit: all traffic to the service is encrypted with HTTPS.
- At rest: data is stored with hosting and database providers that encrypt it at rest.
- Keeping customers apart: every database table that holds customer data is protected by Postgres row-level security, so the database itself refuses to return one organization's rows to another, in addition to the checks in our code.
- Limiting access to guest details: the application reads guests' names, emails and answers only through a restricted view, which hides the details of RSVPs that are locked on the Free plan.
- Secrets: API keys and guests' manage links are stored only as SHA-256 hashes and shown once. Webhook signing secrets are encrypted at rest. Secrets are never put in web pages or logs.
- IP addresses: turned into a keyed hash before use, used only for rate limiting and abuse prevention, and deleted within 30 days.
- Bot and abuse protection: rate limits per key and per IP address, Cloudflare Turnstile and a hidden form field on public RSVP forms.
- Test mode: test data is kept apart from live data; a test key can never read or change live data.
- Retention: guest names, emails and answers are anonymized a set number of days after each event ends (365 by default, set by Customer).
- People: access to production systems is limited to the people who need it to run the service, and the accounts used to run it are protected with two-factor sign-in [to be confirmed by the owner before publishing].
WhoComing may update these measures as long as the overall level of protection does not go down.
Not stated yet: backup schedule and retention (they depend on the database provider, still to be chosen), and any certification. WhoComing does not hold SOC 2 or ISO 27001 certification.
8. Personal data breaches
WhoComing will notify Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data, and aims to do so within 72 hours. The notice will go to Customer's account owner by email and will describe, as far as WhoComing then knows: what happened, the categories and approximate number of guests and records affected, the likely consequences, and what WhoComing has done or proposes to do. WhoComing will add information as it learns more.
WhoComing will take reasonable steps to contain the breach and limit harm, and will help Customer meet its own duties to notify authorities and guests. Notice of a breach is not an admission of fault.
9. Requests from guests
Customer can answer guests' requests to see, correct, export or delete their data itself, without asking WhoComing:
| Request | How |
|---|---|
| Delete one RSVP | DELETE /v1/rsvps/{id}, or delete it in the dashboard |
| Erase a guest across all of Customer's events | POST /v1/guests/erase with the guest's email address |
| Export everything held about a guest | GET /v1/guests/export?email= |
| Correct details | PATCH /v1/rsvps/{id}, or edit the RSVP in the dashboard |
| Export all RSVPs | CSV export in the dashboard, or list them through the API |
Guests can also change or cancel their own RSVP through the private link in their confirmation email.
If a guest contacts WhoComing directly about Customer Personal Data, WhoComing will pass the request to Customer and will not answer it itself, except to tell the guest to contact Customer. Where the tools above are not enough, WhoComing will help Customer respond.
10. Deletion and return
While Customer uses the service, Customer can export and delete Customer Personal Data at any time with the tools in section 9.
When Customer's account ends, Customer has 30 days to export its data. After that, WhoComing will delete Customer Personal Data within [deletion period], unless the law requires WhoComing to keep it. Copies in backups are deleted when those backups expire, after [backup retention period, to be confirmed].
On request, WhoComing will confirm the deletion in writing.
11. Information and audits
WhoComing will make available to Customer the information reasonably needed to show that it meets this DPA, including answers to reasonable security questionnaires and, where sub-processors make them available, their own audit reports.
If that is not enough, or a regulator requires it, Customer may audit WhoComing's compliance, by itself or through an independent auditor bound by confidentiality, at Customer's cost, no more than once a year (unless after a personal data breach), with at least 30 days' written notice, during business hours, and without access to other customers' data.
12. US state privacy laws
For Customer Personal Data covered by the CCPA or other US state privacy laws, WhoComing is Customer's service provider or processor, and Customer discloses that data to WhoComing only for the limited and specified business purposes in section 2. WhoComing will not:
- sell or share the data, as those laws define selling and sharing (sharing includes use for cross-context behavioural advertising);
- keep, use or disclose it for any purpose other than those business purposes, or outside the direct business relationship with Customer;
- combine it with personal data WhoComing receives from or on behalf of anyone else, or collects itself, except as those laws allow.
WhoComing will comply with those laws and give the same level of privacy protection they require, will tell Customer if it decides it can no longer meet its obligations under them, and allows Customer to take reasonable and appropriate steps to stop and fix any unauthorized use. WhoComing understands and will comply with these restrictions.
13. Liability and order of precedence
Each party's liability under this DPA is subject to the limits in the terms of service, except where Data Protection Laws or the SCCs do not allow it.
If this DPA conflicts with the terms of service, this DPA wins for anything about personal data. If the SCCs conflict with this DPA, the SCCs win.
This DPA lasts as long as WhoComing processes Customer Personal Data. Questions: [privacy contact email, for example privacy@whocoming.com].