Sub-processors
Last updated 14 October 2026
A sub-processor is a company we use to help provide the service that handles customer data: the information inside a customer’s tenant, including details of its attendees. This page lists each one, what it does, what data it handles and where. It forms part of the data processing agreement between EventDrake Limited and each customer.
We give 30 days’ notice by email before we add or replace a sub-processor, and from that notice you have 14 days to object. Clause 3 explains how.
1. Sub-processors
1.1 We use these sub-processors. The last column shows which data regions each one applies to.
| Sub-processor | Purpose | Data | Location | Regions |
|---|---|---|---|---|
| Amazon Web Services | Hosting, database, storage, login, email, backups | All customer data | The tenant’s data region and its backup location; global services from Northern Virginia; edge locations around the world | All |
| New Relic, Inc. | Error and performance monitoring | Technical data: URLs, timings, errors, IP address, internal IDs | United States. The European Union region will use New Relic’s European Union data centre | All |
| Intuition Machines, Inc. (hCaptcha) | Bot protection on checkout and contact forms | IP address, browser signals | United States | Australia and United States. The European Union region will use a replacement hosted in the European Union, or none |
| Google LLC (Google Fonts) | Web fonts on attendee sites | IP address, browser details | Global | All, until we host fonts ourselves |
| Cloudflare, Inc. (cdnjs) | Icon font | IP address, browser details | Global | All, until we host icons ourselves |
| Anthropic PBC | Analysis, debugging and software development | Diagnostics, logs and code, and limited samples of customer data when needed to investigate a problem. This data is never used for model training | United States, directly or through Amazon Bedrock | Australia and United States. The European Union region only through Amazon Bedrock in a European Union region, once available |
| Google LLC (Google Workspace) | Support email | Whatever a customer sends us | Global | All |
1.2 Each sub-processor is bound by a written contract that protects customer data to the same standard as our data processing agreement. We stay responsible for their work, as clause 5 of that agreement sets out.
1.3 Where a sub-processor handles customer data from the European Union region outside the European Union, the Standard Contractual Clauses apply, as clause 10 of the data processing agreement sets out.
2. Data regions
2.1 Each tenant is created in one data region, and Amazon Web Services stores its data there. Backups are kept in a second location in the same region.
| Region | Data stored in | Backups in | Status |
|---|---|---|---|
| Australia | Sydney | Melbourne | Live |
| European Union | Ireland | Frankfurt | Live |
| United States | Oregon | Ohio | Planned |
2.2 Some Amazon Web Services features are global and run from Northern Virginia. Limited operational data, such as domains, certificates and edge request logs, may be processed there for every region.
2.3 The other cases where data is accessed or processed outside a tenant’s region are set out in the privacy policy.
3. How we tell you about changes
3.1 We will give you 30 days’ notice before we add or replace a sub-processor. The notice goes by email to your tenant’s account owner through the hub, and we update this page at the same time.
3.2 From our notice, you have 14 days to object on reasonable data protection grounds by emailing hello@eventdrake.net. We will work with you in good faith to resolve it.
3.3 If we can’t resolve your objection, you can terminate your account before the change takes effect, and we will refund any fees you have prepaid for the period after termination.
3.4 The full terms are in clause 5 of the data processing agreement.
4. Services that are not our sub-processors
4.1 Your Stripe account. Attendee payments go through your own Stripe account, under your agreement with Stripe. Stripe provides that account to you, so Stripe isn’t our sub-processor. The same applies to a Stripe Terminal reader you buy through your Stripe account.
4.2 SmartPay. We are phasing out SmartPay payment terminals. SmartPay isn’t our sub-processor.
4.3 Our own business tools. We use our own Stripe account for billing, accounting software for our records, and a cookieless analytics service for eventdrake.net once we turn it on. These handle information about our own customers and website visitors, not customer data. The privacy policy covers them.
Version history
- : First published.