Events.com Data Processing Addendum (Organizers)
Effective Date: November 5, 2026.
This Data Processing Addendum (“DPA”) forms part of the Events.com Terms of Service (“Terms”) between the Organizer and Events.com, Inc., or the Schedule 1 entity for the relevant service or region (“Events.com”). It applies whenever Events.com processes Organizer Personal Data on the Organizer’s behalf. The Organizer accepts this DPA by accepting the Terms, including by checking the acceptance box and clicking to publish an event, and Events.com will provide a countersigned copy on request. Capitalized terms not defined here have the meanings in the Terms.
1. Definitions
- Data Protection Laws: all laws that apply to the processing of Organizer Personal Data under this DPA. These include the EU GDPR, the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, the California Consumer Privacy Act (“CCPA”) and other U.S. state privacy laws, the Washington My Health My Data Act and Nevada’s consumer health data law, Canada’s PIPEDA and provincial laws (including Québec’s Act respecting the protection of personal information in the private sector), the UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data, Brazil’s Lei Geral de Proteção de Dados, and the data protection laws of the other countries where the Services are available. “Controller,” “processor,” “data subject,” “processing,” “business,” “service provider,” and “sell” or “share” have the meanings given in the applicable Data Protection Laws.
- Organizer Personal Data: personal data that Events.com processes on the Organizer’s behalf to provide the Services, as described in Annex I.
- Subprocessor: a third party, including a Company Group member, that Events.com engages to process Organizer Personal Data.
- Personal Data Breach: a breach of security leading to the accidental or unlawful destruction, loss, alteration, or unauthorized disclosure of, or access to, Organizer Personal Data, including a confidentiality incident under Québec law.
- SCCs: the standard contractual clauses approved by European Commission Implementing Decision (EU) 2021/914.
- UK Addendum: the International Data Transfer Addendum issued by the UK Information Commissioner.
2. Scope and roles
The Organizer is the controller (or “business”) of Organizer Personal Data, and Events.com is its processor (or “service provider”). This DPA covers processing to provide the Services the Organizer uses, including hosting event registration pages; collecting registration and custom-question responses; issuing tickets; sending attendee messages the Organizer initiates; check-in; reporting to the Organizer; for Sponsorship Tools customers, including HelpGetSponsors, storing sponsor and prospect contact records, proposals, contracts, fulfillment records, and sponsor leads the customer uploads or collects; for Operabase customers, Pro Tools features that process personal data the customer uploads or manages, namely the customer’s own projects, shortlists, notes, and saved searches in the Casting Tool, Talent Search, and organizer, producer, presenter, and venue search, and agency roster management; for Remo customers, hosting virtual and hybrid events, including registration, attendee profiles, chat, AI matchmaking, recordings and livestreams the customer starts, captions and transcripts, documents attendees upload at the customer’s request, and lead capture; and, for BibNumbers customers, printing participant names and numbers on event identification products. Audience Reach, which promotes a customer’s events and profiles on Operabase, is provided by Arts Consolidated ApS as an independent controller and is not covered by this DPA.
For Operabase, Remo, and BibNumbers, “Organizer” includes any customer for which Arts Consolidated ApS, Remo USA, Inc., or JM EventsOnline.ca Inc. (operating as BibNumbers.com) processes personal data as processor, and “Events.com” includes that entity. For the Sponsorship Tools, “Organizer” includes any Property or Sponsor that uses them. Events.com is an independent controller, not a processor, when it processes personal data for its own purposes described in its Privacy Policy. These purposes are: account administration; payment processing and fraud and bot prevention; security; legal, tax, and regulatory compliance; analytics and product improvement, with consent where the Privacy Policy says so; its relationship with its own users, including personalizing Discover from users’ activity on the Services; and operating the Discover and Operabase directories and Data Products from public sources and partner data, which never draw on Organizer Personal Data. Events.com is not a joint controller with the Organizer. This DPA does not govern that processing. Events.com will not use answers to the Organizer’s custom registration questions, or other Organizer Personal Data processed under this DPA, to recommend or market other organizers’ events, to build or enrich directory profiles, to include in Data Products, or for any purpose not permitted by this DPA.
3. Organizer responsibilities
The Organizer will:
- have a lawful basis for the processing, and provide all notices and obtain all consents Data Protection Laws require, including explicit consent for health or accessibility data, parental consent where required for minors (under 14 in Québec), and attendee opt-in before sharing contact details with sponsors or exhibitors;
- flag registration fields that collect health, medical, disability, or accessibility information, or information about minors, collect such data only where necessary for its event, and use the separate consent screen Events.com provides for health questions;
- assign accurate event categories under Section B.3A of the Terms, so the regional rules and the sensitive-data safeguards in Annex II apply to its events;
- set a refund policy and declare every mandatory fee before publishing a paid event, as Sections B.2 and B.3 of the Terms require, and fund the cancellation refunds in Section C.3 of the Terms;
- not use the Services to collect protected health information under HIPAA, payment card data outside the payment flow, or government identification numbers unless the feature is designed for it;
- give instructions that comply with Data Protection Laws; and
- handle requests from its attendees as controller, using the tools Events.com provides.
3A. Organizer content showing individuals
Rights in the event descriptions, images, video, and other content the Organizer adds to the Services are governed by Sections A.5 and B.3B of the Terms. Where that content includes the image, voice, or name of an identifiable individual, the Organizer is the controller of that personal data and confirms that it has a lawful basis, and any consent or release the law requires, to publish it through the Services and to grant the license in the Terms. The Organizer will tell Events.com promptly if an individual withdraws consent or objects, so that the content can be removed.
4. Events.com obligations as processor
Events.com will:
- Instructions. Process Organizer Personal Data only on the Organizer’s documented instructions, which are the Terms, this DPA, and the Organizer’s use and configuration of the Services, unless the law requires otherwise; in that case Events.com will inform the Organizer first unless the law prohibits it. Events.com will tell the Organizer if it believes an instruction infringes Data Protection Laws.
- Confidentiality. Ensure personnel authorized to process Organizer Personal Data are bound by confidentiality and trained appropriately.
- Security. Implement the technical and organizational measures in Annex II, which may be updated provided protection is not materially reduced.
- Subprocessors. Engage Subprocessors only under Section 6.
- Data subject requests. Taking into account the nature of the processing, assist the Organizer by appropriate measures, including self-service export and deletion tools, in responding to data subject requests. Events.com will forward any request it receives about Organizer Personal Data to the Organizer within two business days and will not respond itself unless instructed or required by law. When an attendee who holds an Events.com account asks Events.com to delete that account, Events.com may anonymize their personal data in the Organizer’s records while keeping the transaction amounts needed for accounting.
- Other assistance. Provide reasonable assistance with the Organizer’s security obligations, breach notifications, data protection impact assessments, and prior consultations with regulators, taking into account the information available to Events.com.
- Deletion and return. Delete or return Organizer Personal Data under Section 11.
- Information and audits. Make available the information necessary to demonstrate compliance with this DPA and allow audits under Section 10.
- Protective defaults. Configure the attendee-facing settings it controls, such as attendee directory visibility and sharing with sponsors, to the most protective option by default, so that the Organizer or attendee must choose to change them.
5. Aggregated and de-identified data
The Organizer authorizes Events.com to create aggregated or de-identified data from Organizer Personal Data, so it does not identify and cannot reasonably be linked to the Organizer, any attendee, or any individual or household. Events.com may use that data only to operate, secure, improve, and develop the Services, including benchmarking and analytics features offered to organizers and sponsorship customers, and to train and improve Events.com’s own machine-learning models. Events.com will commit to maintaining the data in de-identified form, take reasonable technical measures to prevent re-identification, not attempt to re-identify it, and contractually prohibit any recipient from re-identifying it. Events.com will not use the content of Remo audio, video, recordings, chat, or uploaded documents, or fields flagged as sensitive, to train machine-learning models. Events.com will not sell or share Organizer Personal Data. This Section does not limit the Organizer’s right to access and export its data under the Terms.
6. Subprocessors
The Organizer gives general authorization for Events.com to engage Subprocessors, including Company Group members. The current list is in Annex III and at events.com/legal/subprocessors. Events.com will give at least 30 days’ notice of a new Subprocessor through the list page, where the Organizer may subscribe to email notice of changes. The Organizer may object on reasonable data protection grounds within that period. The parties will discuss the objection in good faith; if it is not resolved, the Organizer may terminate the affected Services and receive a refund of prepaid fees for them. Events.com will impose data protection obligations on each Subprocessor, by written contract, that are no less protective than this DPA, and remains liable for its Subprocessors’ performance.
7. Personal Data Breaches
Events.com will notify the Organizer without undue delay, and in any event within 72 hours, after becoming aware of a Personal Data Breach affecting Organizer Personal Data. The notice will describe, as far as known, the nature of the breach, the categories and approximate numbers of data subjects and records affected, the likely consequences, and the measures taken or proposed. Events.com will update the Organizer as more information becomes available, take reasonable steps to contain and remediate the breach, record it in its incident register, and assist the Organizer with notifications it must make. Notice is not an admission of fault.
8. International transfers
- Locations. Events.com may process Organizer Personal Data in the United States and in other countries where it or its Subprocessors operate, subject to this Section. Organizer Personal Data is hosted on Amazon Web Services in the United States (us-west-2, Oregon); Operabase customer data is hosted on Amazon Web Services in Germany (eu-central-1, Frankfurt); BibNumbers order and participant data is stored in Canada. Personnel and contractors of Events.com and its Company Group who may access Organizer Personal Data are located in the United States, Brazil, Denmark, India, Italy, Pakistan, and Slovakia; access from countries without an adequacy decision is protected by the SCCs and the measures in Annex II.
- EU transfers. For transfers of Organizer Personal Data subject to the EU GDPR to a country without an adequacy decision, the parties incorporate Module 2 (controller to processor) of the SCCs, with Events.com as data importer. For the SCCs: Clause 7 (docking) applies; Clause 9 uses Option 2 (general authorization), with the notice period in Section 6; the optional redress language in Clause 11 does not apply; under Clause 13, the competent supervisory authority is the Organizer’s lead authority or, if the Organizer is not established in the EU, the authority of the Member State where its EU representative is located; Clauses 17 and 18 select the law and courts of Ireland. Annexes I, II, and III of this DPA complete the SCC annexes. Events.com does not rely on the EU-U.S. Data Privacy Framework for these transfers.
- UK transfers. For transfers subject to the UK GDPR, the UK Addendum applies to the SCCs. Table 1 is completed by Annex I, Tables 2 and 3 by this Section and the Annexes, and in Table 4 either party may end the Addendum as it permits.
- Swiss transfers. For transfers subject to Swiss law, the SCCs apply with these changes: references to the GDPR include the Swiss Federal Act on Data Protection, the competent authority is the Federal Data Protection and Information Commissioner, and “Member State” includes Switzerland for data subjects there.
- Transfers in both directions. The Organizer authorizes Events.com and its Subprocessors to transfer Organizer Personal Data from the country where it is collected to the locations in Section 8.1, and to receive Organizer Personal Data that the Organizer, its attendees, or the Organizer’s other service providers send from any country. Where Arts Consolidated ApS, as a processor established in the EU, makes Organizer Personal Data available to an Organizer outside the EEA (for example, in Pro Tools), the parties incorporate Module 4 (processor to controller) of the SCCs. Where a Company Group member acting as processor transfers Organizer Personal Data to another Company Group member acting as its Subprocessor outside the EEA or the UK, Module 3 (processor to processor) applies under the Company Group’s intra-group data transfer agreement.
- Restricted transfers. Events.com will not transfer Organizer Personal Data, or allow access to it, in a way prohibited by the U.S. Department of Justice rule at 28 C.F.R. Part 202 on access to bulk U.S. sensitive personal data by countries of concern, and will comply with that rule’s conditions for any restricted transaction.
- Onward transfers. Events.com will transfer Organizer Personal Data to Subprocessors outside the protected jurisdiction only under a transfer mechanism recognized by Data Protection Laws.
- Conflict. If the SCCs or UK Addendum conflict with this DPA, they prevail.
9. U.S. state privacy laws
Where the CCPA or another U.S. state privacy law applies, Events.com acts as the Organizer’s service provider or processor and will:
- process Organizer Personal Data only for the limited and specified business purposes in Section 2 and Annex I;
- not sell or share Organizer Personal Data;
- not retain, use, or disclose it outside the direct business relationship with the Organizer or for any purpose other than those purposes, except as the law permits;
- not combine it with personal data Events.com receives from or on behalf of others, or collects from its own interactions with consumers, except as the law permits a service provider to do;
- comply with applicable obligations under those laws and provide the same level of privacy protection they require;
- notify the Organizer if it determines it can no longer meet its obligations;
- allow the Organizer, on notice, to take reasonable and appropriate steps to stop and remediate unauthorized use of Organizer Personal Data; and
- impose these obligations on its Subprocessors by written contract.
The Organizer may take reasonable steps to confirm that Events.com uses Organizer Personal Data consistently with these obligations, including through the audit rights in Section 10.
9A. Consumer health data
Where an Organizer collects consumer health data through the Services, as the Washington My Health My Data Act or Nevada’s consumer health data law defines it, Events.com processes it only on the Organizer’s instructions and to provide the Services, collects it only after the separate consent screen in Section 3, item 2, does not share it with any affiliate or third party except its Subprocessors, helps the Organizer honor consumers’ requests to access, delete, or withdraw consent, and deletes it under Section 11. The Organizer publishes its own consumer health data privacy policy where those laws require one.
10. Audits
On written request, no more than once a year, Events.com will answer a reasonable security questionnaire and provide a summary of its security program. Events.com, Inc. does not currently hold a SOC 2 report or ISO 27001 certification; if it obtains one, it will provide the most recent report or certificate on request. Remo USA, Inc. maintains a SOC 2 report and ISO/IEC 27001 certification for Remo, which Remo customers may request under confidentiality. If those materials are not enough to demonstrate compliance, or a regulator requires it, or after a Personal Data Breach, the Organizer may conduct an audit, itself or through an independent auditor bound by confidentiality. The audit takes place on at least 30 days’ notice, during business hours, in a way that minimizes disruption, and at the Organizer’s cost, unless the audit reveals a material breach by Events.com.
11. Deletion and return
The Organizer can export Organizer Personal Data during its account term and for 30 days after termination; for business customers in the EU, the switching and retrieval periods in Section E.11 of the Terms apply where they are longer. After that period, Events.com will delete Organizer Personal Data within 60 days, unless the law requires it to keep some. Copies in backups are deleted on the normal backup cycle (no more than 90 days) and remain protected until then. On request, Events.com will confirm deletion in writing.
12. Québec and other jurisdictions
- Québec mandate terms. Where Events.com processes personal information about residents of Québec under this DPA, this DPA is the written mandate or service contract that section 18.3 of the Québec Act respecting the protection of personal information in the private sector requires. Events.com will: protect the information with the measures in Annex II; use it only to carry out the mandate; not keep it after the mandate ends, and return or destroy it under Section 11; notify the Organizer’s person in charge of the protection of personal information without delay of any confidentiality incident or any breach of these obligations; and allow the Organizer to verify its compliance, including under Section 10.
- Communication outside Québec. Before Organizer Personal Data about residents of Québec is communicated outside Québec, Events.com will help the Organizer complete the privacy impact assessment that section 17 of that Act requires, and this DPA, with the protections that assessment identifies, is the written agreement that section 17 requires.
- Québec incidents. Events.com will notify the Organizer of any confidentiality incident under Section 7, so that the Organizer can meet its obligations to the Commission d’accès à l’information and keep its incident register.
- Canada and the UAE. Where Canadian or UAE law applies, Events.com will apply the protections in this DPA and any additional measures those laws require.
- Brazil. Where Brazilian law applies to a transfer of Organizer Personal Data, the parties incorporate the standard contractual clauses approved by the Autoridade Nacional de Proteção de Dados in Resolution CD/ANPD No. 19/2024.
- Other instruments. Where the law of another exporting country requires a specific transfer instrument, such as the standard contract under China’s Personal Information Protection Law or the ASEAN Model Contractual Clauses, the parties will execute or incorporate it on request. If a Data Protection Law requires additional contract terms, the parties will agree on them in good faith.
13. Liability, precedence, and term
Each party’s liability under this DPA is subject to the limits in the Terms, except where Data Protection Laws or the SCCs prohibit limiting liability toward data subjects. Order of precedence for data processing: the SCCs and UK Addendum, where they apply; then this DPA; then the Terms. This DPA lasts as long as Events.com processes Organizer Personal Data on the Organizer’s behalf. Sections 7, 10, and 11 survive until that processing ends. Events.com may update this DPA to reflect changes in law, Subprocessors, or the Services, with notice under the Terms. Updates will not materially reduce the protection given to Organizer Personal Data.
Annex I: Parties and description of processing
- Parties
- Data exporter (controller): the Organizer, as identified in its account. Contact: the account owner’s details. Role: controller.
- Data importer (processor): Events.com, Inc., 811 Prospect Street, La Jolla, CA 92037, USA, including for the Sponsorship Tools, or, for Operabase customers, Arts Consolidated ApS, Business Centre Nord, Lyngbyvej 20, 2100 Copenhagen Ø, Denmark. For Remo customers, the data importer is Remo USA, Inc., 2093 Philadelphia Pike #8552, Claymont, DE 19703, USA, and for BibNumbers customers, JM EventsOnline.ca Inc. (operating as BibNumbers.com), 17-155 Colonnade Road, Ottawa, Ontario K2E 7K1, Canada. Contact for every importer: Privacy Officer, privacy@events.com. EU representative for Events.com, Inc. and Remo USA, Inc.: Arts Consolidated ApS, at the address above. Role: processor.
Both parties sign by accepting the Terms, which incorporate this DPA.
- Description of processing
Item | Description |
|---|
Data subjects | Event registrants and ticket buyers; attendees named by a purchaser; donors; parents or guardians, and minors they register; the Organizer’s personnel who use the Services; for the Sponsorship Tools, contacts at sponsors, prospects, agencies, and partners, and attendees who opt in to sponsor lead sharing; for Remo, event participants, speakers, exhibitors, and employers; for BibNumbers, event participants whose names or numbers are printed |
Personal data | Name and contact details; registration and custom-question responses; ticket, order, and check-in records; payment metadata (not full card numbers); messages the Organizer sends through the Services; device and security-check data needed to deliver tickets and messages and to protect checkout; for the Sponsorship Tools, business contact details, job titles, organization, communications, proposal and contract records, and lead information; for Remo, audio and video streams, recordings and transcripts the Organizer starts, chat, profile and matchmaking data, and documents participants upload; for BibNumbers, participant names and numbers |
Special categories and sensitive data | Only if the Organizer collects them: health, medical, disability, or accessibility information, including consumer health data. Safeguards: field flagging, separate consent screen, access limited to authorized personnel, no use outside this DPA. Data about minors: collected from parents or guardians only. Registration and attendance records for events whose nature reveals sensitive characteristics, such as LGBTQ+ events or political assemblies, are treated as sensitive data with the same safeguards. |
Frequency | Continuous for the duration of the Services |
Nature of processing | Collection, hosting, storage, organization, retrieval, transmission (email and SMS sent on the Organizer’s instructions), check-in scanning, security checks, reporting, export, and deletion |
Purpose | Providing the Services to the Organizer under the Terms |
Retention | During the account term, plus the export and deletion periods in Section 11, unless the law requires longer |
Transfers to Subprocessors | As listed in Annex III, for hosting, payments, communications, support, security, and error monitoring |
Competent supervisory authority | Under Section 8.2 |
Annex II: Technical and organizational measures
- Access control. Role-based access on a least-privilege basis; multi-factor authentication for production, administrative, and remote access; prompt removal of access when personnel leave or change roles; quarterly access reviews.
- Encryption. TLS 1.2 or higher in transit; AES-256 encryption at rest for databases, backups, and object storage; managed key storage with restricted access.
- Sensitive data. Health, accessibility, and minors’ data fields are flagged, collected only after the separate consent screen, visible only to the Organizer and authorized support personnel, and excluded from analytics, recommendations, and model training.
- Consent controls. Optional analytics and error-monitoring tools load on registration and checkout pages only after the attendee accepts them; form inputs are never captured by analytics; security checks load only at the protected action.
- Logging and monitoring. Centralized logging of administrative access and security events, retained for at least 12 months, with alerting for anomalous activity.
- Vulnerability management. Dependency and container scanning, timely patching of critical vulnerabilities, and an independent penetration test at least annually.
- Secure development. Code review before deployment; separation of development, test, and production environments, with test environments that cannot start production transactions; the pre-release privacy, consent, and link check (the “Release Gate”) in Section 9 of the Company Group’s Master Intercompany Agreement, which Events.com’s IT function runs before every release that affects personal data and which blocks any release that fails it; and no use of production personal data in testing without masking.
- Resilience. Encrypted backups, tested restoration, and infrastructure across multiple availability zones of Amazon Web Services.
- Incident response. A documented incident response plan with defined roles, escalation to Legal within 24 hours, an incident register, and the notification timelines in Section 7.
- Personnel and vendors. Confidentiality agreements and security and privacy training for personnel; security and privacy review of Subprocessors before engagement and periodically after.
- Data minimization and deletion. Collection limited to what the Services need, deletion under Section 11, and de-identification controls under Section 5.
- Separation from directory data. Organizer Personal Data is logically separated from Discover and Operabase directory data and Data Products, and is not used to build, enrich, or match directory profiles.
- Physical security. Data centers operated by Amazon Web Services under its physical and environmental controls; no personal data stored on removable media.
Annex III: Subprocessors
The current list is maintained at events.com/legal/subprocessors. This list covers only Subprocessors that process Organizer Personal Data. Vendors that process data Events.com controls for its own purposes are described in the Privacy Policy, and internal tools that process no customer personal data are not listed.
Subprocessor | Service | Location | Transfer mechanism |
|---|
Events.com, Inc. (Company Group) | Hosting for every Service except Operabase, which is hosted in Germany; engineering and support, including remote access for Operabase, Remo, and the Sponsorship Tools | United States | SCCs under the intra-group data transfer agreement |
Arts Consolidated ApS (Company Group) | Engineering and support | Denmark (EU) | Intra-group data transfer agreement; no transfer outside the EU for data hosted in Germany |
JM EventsOnline.ca Inc. (Company Group, BibNumbers.com) | Printing and shipping of event identification products | Canada | EU adequacy decision for Canada; intra-group data transfer agreement |
Amazon Web Services, Inc. | Infrastructure hosting and databases | United States (Oregon); Germany (Frankfurt) for Operabase | SCCs / DPF |
Stripe | Payment processing, at the payment step | United States; Ireland | SCCs / DPF |
Google LLC (reCAPTCHA Enterprise) | Bot and fraud protection at sign-in, registration, and checkout, as processor | United States | SCCs / DPF |
Functional Software, Inc. (Sentry) | Error monitoring: in the browser only after the attendee accepts Analytics; server-side error logs always | United States | SCCs |
Twilio Inc. (SendGrid) | Transactional and organizer-initiated email | United States | SCCs / DPF |
Twilio Inc. (Programmable Messaging) | Text messages the Organizer sends | United States | SCCs / DPF |
HubSpot, Inc. | Email, customer relationship management, and customer support (Service Hub) | United States | SCCs / DPF |
Postmark (ActiveCampaign, LLC) | Operabase transactional email | United States | SCCs / DPF |
Google LLC (Google Workspace) | Email, documents, and collaboration used in support | United States | SCCs / DPF |
Cloudflare, Inc. | Content delivery and security | United States | SCCs / DPF |
Google LLC (Firebase Cloud Messaging) | Push notifications about tickets and events, including messages the Organizer sends | United States | SCCs / DPF |
PostHog, Inc. | Product analytics and feature flags, with attendee consent; form inputs are never captured | United States | SCCs |
Usercentrics GmbH | Consent management: recording attendees’ cookie and SDK choices | Germany (EU) | No transfer outside the EU |
Mapbox, Inc. | Maps and location search | United States | SCCs |
Google LLC (Google Maps Platform) | Maps on event and registration pages, after the attendee accepts Functional cookies | United States | SCCs / DPF |
Capgo | Mobile app updates | [To be confirmed] | [To be confirmed] |
Oracle America, Inc. (NetSuite) | Finance and accounting records, including organizer payouts and refunds | United States | SCCs / DPF |
[AI model provider(s): to be confirmed before publication] | Remo AI matchmaking, captions, and transcripts, where the Host turns them on | [To be confirmed] | SCCs |
“DPF” in this table refers to the Subprocessor’s own certification under the EU-U.S. Data Privacy Framework, which supplements and does not replace the SCCs.