Sub-processors
The providers we use to run Clubo, what each one does with club and member data, and where each is based. Clubs can point their own members at this page.
Last updated 25 August 2026
Current sub-processors
| Provider | What it does | Data involved | Location |
|---|---|---|---|
| Supabase | Application database, file storage and authentication | All club and member records, profile photos, club badges | EU / UK |
| Cloudflare | Hosting, content delivery and application runtime | Requests to the app, including data in transit | Global edge network |
| Stripe | Card payments, subscriptions and payouts to clubs | Payer name, email, payment amounts and card details (held by Stripe, not by us) | EU / US |
| Google (Gmail API) | Sending invitations, payment requests and reminders by email | Recipient name and email address, message content | EU / US |
| Web push services (Apple, Google, Mozilla) | Delivering push notifications to members' devices | Device push endpoint and notification content | Global, per device platform |
| Lovable | Platform on which Clubo is built, hosted and maintained | Operational access to the application and its logs | EU / US |
How this list changes
We update this page before adding or replacing a sub-processor. Each one is bound by data protection obligations no less protective than those in our data processing agreement, and we remain responsible for their performance. If your club objects to a new sub-processor on reasonable data protection grounds, email hello@club-o.app.
What we do not do
We don't sell personal data and we don't use it for advertising. Where a provider processes data outside the UK, transfers rely on the safeguards that provider offers, such as the UK International Data Transfer Addendum or standard contractual clauses. See our privacy policy for the full picture.