Subprocessors
These are the only third parties that process customer data on our behalf. The list is short because the service is built to keep it short: there is no analytics provider, no advertising network, no customer data platform, no chat widget and no AI vendor in this list, because none of them is used.
Current subprocessors
Hetzner Online GmbH
- Purpose
- Hosts the application, the database, uploaded files and their backups.
- What it can see
- Everything stored by the service, as the infrastructure it runs on.
- Incorporated in
- Germany
- Where the data is
- Germany (application, database, files, primary backups) and Finland (offsite backup copy)
- Transfers outside the EEA
- Within the European Union. No transfer outside the EEA arises.
Cloudflare, Inc.
- Purpose
- Carries traffic between the browser and the server, and protects the service from attack.
- What it can see
- Requests in transit and the visitor's network address. It is not a store of tickets or files.
- Incorporated in
- United States
- Where the data is
- Global edge network. Traffic to this service is carried through a tunnel to the European Union.
- Transfers outside the EEA
- Covered by the EU standard contractual clauses in the Cloudflare data processing addendum, version 6.4 of 3 April 2026.
Resend, Inc.
- Purpose
- Delivers the service's email: sign-in codes, invitations and ticket notifications.
- What it can see
- Recipient addresses and the content of those messages.
- Incorporated in
- United States
- Where the data is
- Ireland (eu-west-1), the region the sending domain is configured to use.
- Transfers outside the EEA
- Processed in the Resend Ireland region, so messages stay inside the EU. Where a transfer to the United States arises, the EU standard contractual clauses in the Resend data processing addendum apply.
Services you connect yourself
These are not our subprocessors, and the difference matters. A subprocessor is someone we engage to handle your data on our behalf, and we are answerable for them. The services below are tools you already have and connect yourself, under your own arrangement with them. Nothing here is switched on unless you switch it on, and you can switch it off at any time.
- Microsoft. Confirms a person's identity when an organisation chooses Microsoft sign-in. We receive the email address and name in the token. Nothing about tickets is sent to it.
- Google. Confirms a person's identity when an organisation chooses Google sign-in. We receive the email address and name in the token. Nothing about tickets is sent to it.
- Slack. If an organisation connects a Slack channel, we post a short message there when a ticket is raised, replied to or moved on: the reference, the subject line, who raised it and a link. The description and the replies are never sent. The channel, and who can read it, are that organisation's decision, and it can disconnect at any time.
The company that takes the payment
Dodo Payments Inc. is our merchant of record, which makes it a third thing again. On a card sale it is the legal seller: its name is on your statement, it issues your receipt, and it collects and files the VAT. It is not handling anything on our instructions, so it is not a subprocessor and we are not answerable for it the way we are for the three above. It is not something you connected either, because we chose it. It is here because a page that lists everywhere your data goes, and leaves out the one that takes your card, is not a disclosure.
Dodo Payments Inc.
- Role
- Merchant of record, and an independent controller for the payment itself.
- Purpose
- Takes the card payment for a subscription, issues the receipt, and collects and files the VAT on it.
- What we send them
- The subscribing organisation's name, the administrator's email address, and a country code, so the checkout knows who it is for.
- What they collect themselves
- The billing address and the card details, entered on their own checkout page. SIVO Hub never sees a card number and never stores one.
- Incorporated in
- United States, a Delaware corporation, with a UK group entity, Dodope Payments Limited.
- Where the data is
- Amazon Web Services in Mumbai, the ap-south-1 region.
- Transfers outside the EEA
- Their agreement applies the EU standard contractual clauses to transfers out of the EEA, and the UK addendum to UK transfers.
The last three of those are taken from the Dodo Payments Inc. data processing agreement of 11 March 2026, which is published at https://dodopayments.com/legal/data-processing-agreement. Paying by bank transfer instead means there is no checkout and nothing reaches them at all.
Our own storage
One backup copy is held on storage the operator controls directly, in SIVO Hub’s home country, rather than with a provider. It is not a third party and so is not listed above, but it is mentioned here because a subprocessor list that quietly omits a place your data sits is not much of a disclosure.
Changes to this list
Before adding or replacing a subprocessor we give every customer at least 30 days’ notice by email, and a customer who reasonably objects on data protection grounds has the rights set out in section 6 of the Data Processing Agreement. To be told about changes, or to ask anything about this list, write to [email protected].