Meetupcall uses certain subprocessors and subcontractors to assist it in providing the Meetupcall Services.

What is a Subprocessor:

A subprocessor is a third party data processor engaged by Meetupcall, who has or potentially will have access to or process Service Data (which may contain Personal Data). Meetupcall engages different types of subprocessors to perform various functions as explained in the tables below. Meetupcall refers to third parties that do not have access to or process Service Data but who are otherwise used to provide the Services as “subcontractors” and not subprocessors.

Due Diligence:

Meetupcall undertakes to use a commercially reasonable selection process by which it evaluates the security, privacy and confidentiality practices of proposed subprocessors that will or may have access to or process Service Data.

  • process Personal Data in accordance with data controller’s (i.e. Subscriber’s) documented instructions (as communicated in writing to the relevant subprocessor by Meetupcall);
  • in connection with their subprocessing activities, use only personnel who are reliable and subject to a contractually binding obligation to observe data privacy and security, to the extent applicable, pursuant to applicable data protection laws;
  • Provide regular training in security and data protection to personnel to whom they grant access to Personal Data;
  • promptly inform Meetupcall about any actual or potential security breach; and
  • cooperate with Meetupcall in order to deal with requests from data controllers, data subjects or data protection authorities, as applicable.

This policy does not give Subscribers any additional rights or remedies and should not be construed as a binding agreement. The information herein is only provided to illustrate Meetupcall’s engagement process for subprocessors as well as to provide the actual list of third party subprocessors and subcontractors used by Meetupcall as of the date of this policy (which Meetupcall may use in the delivery and support of its Services).

Infrastructure Subprocessors – Service Data Storage

Meetupcall owns or controls access to the infrastructure that Meetupcall uses to host Service Data submitted to the Services, other than as set forth below. Currently, the Meetupcall production systems for the Services are located in co-location facilities in the UK and Ireland. The Subscriber’s Service Data subsequently remains in that region unless agreed between Subscriber and Meetupcall, but may be shifted among data centers within a region to ensure performance and availability of the Services. The following table describes the legal entities engaged in the storage of Service Data by Meetupcall.

Amazon Data Services Ireland Ltd Cloud Service Provider Ireland DPA ISO 27001


Meetupcall works with certain third parties to provide specific functionality within the Services. These providers are the Subprocessors set forth below. In order to provide the relevant functionality these Subprocessors access Service Data. Their use is limited to the indicated Services.

Wildbit, LLC (“Wildbit”) AKA Postmark Email delivery service. We use Postmark to help ensure high email delivery rates to customers’ inboxes. We share email addresses with Postmark in order for them to deliver emails from Meetupcall such as “Conference Invites” and “Conference Reminders”.

SendGrid, Inc. (“SendGrid”) Email delivery service. Like Postmark above Sendgrid offers the same service. Sendgrid is utilised should Postmark suffer a system outage, this ensures good service uptime for our customers.

Google Inc. Email Service and Calendar Provider. Google provide our email service and event scheduling services. Any email or event invite shared with Meetupcall will be processed by Google Inc.

Intercom R&D Unlimited Company.  We use intercom to process support tickets and live chat from our users.

Mailchimp / Intuit Inc. We use Mailchimp to send product update emails to our users.

Rollbar, Inc. Real-time error monitoring, alerting, and analytics. We utilise Rollbar to help our developer and operations teams quickly identify and fix coding issues. In the course of application usage some errors sent to Rollbar may include user data. Meetupcall is, again, the only consumer of this data.

Slack Technologies, Inc. Team collaboration tool. Our team use Slack  to collaborate on work related tasks, and to alert teams to business events that are occurring in real-time. As such some user data is shared with Slack.

Chargify, LLC.  We use Chargify to handle the recurring billing and generation of invoices.

Stripe Payments Europe, Ltd. Payment Processing Service. We utilise Stripe for all of our payment processing. Stripe are an industry leader in payment processing and Meetupcall use them to process credit card payments. To do this we need to share names and addresses with Stripe. Sensitive data such as the credit card data is sent directly to Stripe and Meetupcall have no knowledge of these data.

FreeAgent Holdings plc SaaS Accounting software. FreeAgent provide our accounting software, we also use them to produce and track invoices. As such we need to share names, addresses and email addresses with FreeAgent. Meetupcall are the only consumers of the data stored within FreeAgent.

Elastic, Inc. AKA Meetupcall uses to track sales and leads. We do not share any Service Data with only Account data.