List of Conferences i/o subprocessors

Subprocessors

Descriptions of each type of data

 

Subprocessors

 

The following subprocessors may process personal data on behalf of Conferences i/o. Please note that in most cases, the data used by subprocessors is limited to customer contact information. Conferences i/o greatly restricts subprocessing of end-user data (personal information submitted by attendees).

 

Subprocessor Purpose Type(s) of data Countries of processing
Amazon Web Services Infrastructure as a service Customer contact information, end-user data United States
Appcues Analytics, support End-user behavioral data United States
ClientSuccess Business operations; CRM Customer contact information United States
Freshworks Email, web chat, and phone support Customer contact information United States
Google, Inc. Emails and virtual office, analytics Customer contact information, payment information, end-user behavioral data United States
Google Cloud Platform Infrastructure as a service End-user data United States
Mailchimp Email Customer contact information United States
Liquid Web Infrastructure as a service Customer contact information United States
OpenAI LLM (opt-in features) End-user data (presentation content) United States
PandaDoc Legal Customer contact information, payment information United States
Pipedrive Business operations; CRM Customer contact information United States
Quickbooks Business operations; accounting, invoices, billing Customer contact information, payment information United States
SharpSpring Business operations; CRM Customer contact information United States
Slack Technologies Business operations; internal communication Customer contact information United States
Stripe Business operations; payments Customer contact information, payment information United States
Zoom Video Communication Business operations; internal communication Customer contact information United States

 

 

Descriptions of each type of data

  • Customer contact information: Contact information for organizations and groups that are directly customers of Conferences i/o. This will typically include names, phone numbers, and email addresses of points of contact for Conferences i/o customers.
     
  • Payment information: Billing information related to customer purchases.
     
  • End-user data: The actual data submitted by end-users, including attendees, moderators, and administrators. This includes but is not limited to personally identifying information (if it's been requested), poll responses, social Q&A submissions, and session evaluation responses.
     
  • End-user behavioral data: Behavioral data differs from regular end-user data in that behavioral data describes the actions taken by end users without including the content of the action. For example, if an end-user responds to a poll, we'd record the response itself as end-user data, and then the action of responding to a poll as behavioral data. Behavioral data helps us understand how Conferences i/o is used, and we use those understandings to improve the product.