SUB-PROCESSORS
Who else touches it.
PLAIN-ENGLISH SUMMARY · FULL LEGAL TEXT PUBLISHES WITH LAUNCH
Why this page exists
If we process your data, you are entitled to know who we rely on to do it. Naming them is a GDPR expectation and, frankly, the sort of thing worth checking before trusting any product with your books.
Hosting and infrastructure
Cloud hosting and content delivery for the application and this website, located in the UK and EU.
Banking data
Regulated Open Banking providers supply your bank feed. They are authorised and supervised, and the connection is one you grant and can revoke yourself.
Telephony and messaging
Carriers and messaging providers that deliver calls, texts and chat for the front desk, including transcription of the calls you route through Bizzle.
AI model providers
Models that read documents and draft replies. Content sent for processing is not retained by the provider for training.
Payments
Payment processing for your subscription, and for the payment links you send to your own customers.
Email delivery
Transactional email — invoices, chasers, notifications and account messages.
Product analytics
Cookieless traffic measurement on this website. No profile is built and no identifier is stored in your browser.
Changes and objections
We give notice before adding a sub-processor, and you can object. The named list, with each provider, its role and its location, publishes with launch and is available on request in the meantime.