TallyUp.
Log inGet started

Sub-processors

Last updated 27 August 2026 · BespokeWorks, London, United Kingdom

Running TallyUp means relying on other companies. These are the ones that can touch personal data, what each does, and where it holds it. Each is bound by terms no weaker than our own data processing agreement, and we give notice before adding one.

Google Cloud
Runs the application and the database, and stores files a studio uploads such as logos and class photos.
European Union (europe-west1 and europe-west2)
Data stays in the EEA
Stripe
Takes card payments and holds the card details. Also handles a studio's own subscription to us.
Ireland and United States
Standard contractual clauses; UK extension to the Data Privacy Framework
Resend
Sends transactional email: confirmations, reminders, receipts and the messages a studio writes. Sees the recipient's name and address.
United States (delivering via Amazon SES)
Standard contractual clauses
Twilio
Sends text messages, when a studio turns them on. Sees the phone number and the message.
United States
Standard contractual clauses
OpenRouter
Routes requests to the AI models behind the concierge and copilot, when a studio uses them. Sees the text of that request.
United States
Standard contractual clauses
Google (Calendar, Places, Business Profile)
Free/busy times for a connected calendar, address lookup, and review replies. Only what a studio connects.
European Union and United States
UK extension to the Data Privacy Framework

What is not on this list

Card numbers. They never reach TallyUp. Stripe takes the payment and holds the card under its own PCI certification; we see the amount, the outcome and a reference.

Your client list. It is never shared with any of these companies for their own purposes, never used to train anything, and never sold. The AI features send only the specific text needed to answer the question in front of them, and only when a studio turns those features on.

Optional ones

Some entries only apply if a studio switches that feature on. Twilio sees a phone number only if a studio enables text messages. Google sees calendar free/busy only if somebody connects a calendar, and we ask for free/busy alone, never event contents. OpenRouter sees a prompt only when an AI feature is used.

Changes

We give notice before adding a sub-processor. If you object on reasonable data protection grounds, tell us at privacy@bespokeworks.ai and we will work it out with you or let you leave without penalty.