Legal · Sub-processors

Our sub-processors

The third parties we rely on to provide the Service, what they do, and what data reaches them. Several only engage when you switch on the matching feature.

Last updated 14 July 2026

Sub-processorPurposeDataLocationEngaged
Faden (hosting & database)Runs the platform and stores your dataAll studio & client data (encrypted at rest)AustraliaAlways
StripePayment processing — Faden subscriptions and, where connected, your own customer paymentsName, email, payment metadataUSA / globalWhen paying us, or when you connect Stripe
TwilioSMS, WhatsApp and voice callsName, phone number, message/call contentUSA / globalWhen you use messaging or calling features
SendGrid (Twilio)Delivery of transactional and, where consented, marketing emailName, email address, email content in transitUSA / globalAlways (transactional email)
AnthropicPowers the optional AI copilot (draft & summarise)Customer first name + initial and order context — onlyUSA / globalOnly when a Studio enables the AI copilot
XeroOne-way posting of your invoices, payments and refunds to your own Xero organisationContact name & email, invoice, payment and refund dataGlobalOnly when you connect Xero
CloudflareDNS and network protection for our domainsNetwork and technical request dataGlobalAlways

Each Studio can also see, inside its own settings, exactly which of these sub-processors are active for its account — because several engage only when the corresponding feature is switched on.

Changes. We update this page before adding or replacing a sub-processor, and — where appropriate — notify Studios by email. Under our Data Processing Agreement, you may object to a new sub-processor on reasonable data-protection grounds.

Questions about a sub-processor? Email privacy@faden.tech. See also our Privacy Policy.