Sub-processors

The companies Tadpole uses to run the service, which process club and member data on our behalf. This list forms part of our Data Processing Agreement (Section 7).

Last changed 20 October 2026

Joining this list

These join the list on the date shown. A club may object by writing to privacy@tadpole.club before then.

Clubs told 20 October 2026 · Objections until 4 November 2026 · On the list from 5 November 2026

Cloudflare

Every club

Encrypted nightly backups, DNS and routing of incoming email

Receives: Backups of all platform data, encrypted before upload with a key only Tadpole holds; incoming emails in transit
Where: EU for backups; global edge network for email in transit
Safeguard: Cloudflare Customer DPA with Standard Contractual Clauses
Company: Cloudflare Inc.

Clubs told 20 October 2026 · Objections until 4 November 2026 · On the list from 5 November 2026

Sentry

Every club

Reporting errors in the app so we can fix them

Receives: Error reports, and recordings of the error session with text and images masked, with names, email addresses, tokens and other identifying details removed before sending
Where: Germany (EU)
Safeguard: Sentry DPA; hosted in the EU, with Standard Contractual Clauses for support access from the US
Company: Functional Software Inc. (Sentry)

Clubs told 20 October 2026 · Objections until 4 November 2026 · On the list from 5 November 2026

Anthropic

Clubs with AI Help switched on

The AI help chat in the member app and admin panel

Receives: Questions typed into the help chat and the chat user's role or membership status, with names, contact details and identifiers replaced by placeholders where recognised. Not used to train models; deleted within 30 days
Where: United States
Safeguard: Anthropic Data Processing Addendum with EU Standard Contractual Clauses and the UK Addendum
Company: Anthropic PBC

Named in the updated Data Processing Agreement · Objections until 4 November 2026 · On the list from 5 November 2026

Twilio

Clubs with text messages switched on

Sending text messages to members

Receives: Mobile phone numbers and the text of each message
Where: United States, with EU processing
Safeguard: Twilio Data Protection Addendum with Standard Contractual Clauses
Company: Twilio Inc.

In use

Supabase

Every club

Database, sign-in and file storage, including member photographs

Receives: All club and member records held in the platform
Where: Ireland (EU)
Safeguard: Supabase DPA; data hosted in the EU, with Standard Contractual Clauses for support access from the US
Company: Supabase Inc.

Stripe

Clubs that take card payments

Card payments for memberships, permits and bookings, through your club's own Stripe account

Receives: Payer name, email address, payment details and transaction records
Where: EU and United States
Safeguard: Your club's own agreement with Stripe (Stripe DPA); EU-US Data Privacy Framework
Company: Stripe, under your club's own Stripe account

Vercel

Every club

Hosting and running the app and websites

Receives: Everything shown or entered in the app as it passes through, and request logs including IP addresses
Where: App servers in Dublin, Ireland (EU); global edge network for delivery
Safeguard: Vercel DPA with Standard Contractual Clauses
Company: Vercel Inc.

Brevo

Every club

Email delivery, through your club's own Brevo account

Receives: Names, email addresses and the content of emails sent
Where: France (EU)
Safeguard: Your club's own agreement with Brevo (Brevo DPA); EU-based
Company: Brevo (Sendinblue SAS), under your club's own Brevo account

Not on this list

When a member adds their membership card to Google Wallet or Apple Wallet, the card details go to Google or Apple at the member's request, and they handle them under their own terms. They are not processing data for us, so they are not sub-processors. Your club's privacy notice tells members about this.

When this list changes

We tell every club's administrators at least 14 days before a new sub-processor starts receiving their club's data, in the platform and by email. A club may object in that time; if it does, we discuss alternatives, which may include switching the feature concerned off for that club.

If an existing sub-processor has to be replaced urgently (a security incident, or it stops providing its service), we may make the change first and tell clubs within 72 hours, with the same right to object.